CR ClawReady.in Independent guide
Setup Help
Open menu
Guide Menu expand_more

troubleshooting

Fix Telegram Bot Not Replying in OpenClaw

Check bot token, pairing, allowlist, dmPolicy, Gateway status, and logs without weakening access controls unnecessarily.

Symptom
Telegram messages reach the bot chat, but OpenClaw does not respond.
Severity
medium
Affected Area
telegram
Proceed with caution A silent bot is often an indication that security policies are working correctly and rejecting unknown users.

Symptom

You send a /start or a normal text message to your Telegram Bot. The message gets double checkmarks (delivered), but the bot never replies.

Likely Causes

  1. Your Telegram User ID is not on the allowlist, so the bot is ignoring you for security reasons.
  2. The bot token in claw.config.json is incorrect.
  3. Another process (like a Python script) is running and already polling this Telegram token, stealing the messages from OpenClaw.
  4. OpenClaw Gateway is not running.

Diagnostic Commands

Check the live logs of your OpenClaw Gateway:

bash
tail -f ~/openclaw-workspace/logs/gateway.log

Send a message to the bot on your phone while watching the logs.

Good Output vs Bad Output

Good Output (Security working):

[WARN] Rejected incoming Telegram message from UserID 12345678: Not in allowlist.

(This means the bot works perfectly, but you forgot to add yourself to the allowlist.)

Bad Output (Conflict):

[ERROR] Telegram API Error 409: Conflict: terminated by other getUpdates request

(This means you have another server running a bot with the same token.)

Fix Steps

Diagnose: Telegram Bot Silent

  1. Do the logs show 'Rejected incoming message from UserID... Not in allowlist'?

    YES Copy the UserID printed in the logs, paste it into the `allowlist` array in `claw.config.json`, and restart OpenClaw.
    NO Continue checking for conflicts.

  2. Do the logs show 'Error 409 Conflict'?

    YES Find the other server or script using this bot token and kill it. Telegram tokens can only be polled by one server at a time.
    NO Continue checking bot connectivity.

  3. Are there absolutely zero logs when you message the bot?

    YES Your bot token is likely wrong, or OpenClaw is not actually connected. Run `openclaw channel status` to verify.
    NO Check your rate limits and API quotas.

What NOT to do

Do not disable UFW rules. If the Telegram bot is using polling (the default), you do not need any incoming open ports. Telegram reaches out to your server; your server fetches the updates.

When to ask for help

If your bot token is correct, no other servers are running, and you are still getting zero logs, there might be a webhook/polling architecture mismatch. For complex group deployments or webhook proxy setups, request a Telegram Architecture Session.

Sources

ClawReady.in is an independent educational resource and setup service. It is not affiliated with, endorsed by, or operated by OpenClaw.