Independent Field Manual — Not affiliated with, endorsed by, or operated by OpenClaw
ClawReady.in
Setup Help

Type to search guides, troubleshooting, and recipes.

↑↓ Navigate Enter Open Esc Close Search by Pagefind
Navigation

Guide Hub

Start
What Is OpenClaw?
Install
Fresh Ubuntu VPS Setup for OpenClaw Install on Ubuntu VPS Install Without Docker Node 24 Setup for OpenClaw Hostinger VPS Setup for OpenClaw Run After SSH Logout (PM2)
Secure
Understanding Gateway Port 18789 Performing an Security Audit Tailscale Private Access Setup for OpenClaw VPS Security Checklist
Channels
Why You Need a Dedicated WhatsApp Number for OpenClaw Telegram Allowlist Guide Understanding Telegram Pairing in OpenClaw Telegram Channel Setup WhatsApp Setup

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
On this page
On this page
Symptom

You send a /start or normal text message to your Telegram bot. The message shows double checkmarks (delivered to Telegram), but the bot never replies — not even an error message.

Likely Causes
  1. Your Telegram User ID is not on the allowlist — the bot is ignoring you for security reasons (correct behavior)
  2. The bot token in claw.config.json is incorrect or expired
  3. Another script or server is polling the same bot token, stealing messages from OpenClaw (Telegram 409 conflict)
  4. OpenClaw Gateway is not running
Diagnostic Commands

Watch the live Gateway logs while sending a test message from your phone:

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

Or via PM2:

pm2 logs openclaw --lines 30

Good output (your allowlist policy is working):

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

This means the bot works perfectly — you just need to add your User ID to the allowlist.

Bad output (token conflict with another server):

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

Diagnose: Telegram Bot Silent

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

    YES Copy the UserID from the logs, add it to 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 stop it. Only one server can poll a Telegram token at a time.
    NO Continue checking bot connectivity.

  3. Are there zero log entries when you message the bot?

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

What NOT to do

Do not open firewall rules for Telegram. The default polling mode requires no incoming ports — Telegram reaches out to your server, not the other way around.

When to ask for help

If your token is correct, no other servers are running, and you still get zero logs, there may be a webhook/polling mismatch. 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.