#help me debugi

1 messages · Page 1 of 1 (latest)

devout oriole
#

it says telegram configued but i can't talk to my bot

crude girderBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

normal foxBOT
# devout oriole it says telegram configued but i can't talk to my bot

If Telegram shows “configured” but the bot won’t respond, it’s usually one of these:

  1. Gateway isn’t actually running / reachable
  2. DM access control blocked you (very common: Telegram DMs default to pairing)
  3. Bot token/network issue (can’t reach api.telegram.org)

Quick checks (please paste outputs)

Run these on the machine that runs the Gateway:

openclaw --version
openclaw status --all
openclaw status --deep
openclaw channels status --probe

status --all is the best thing to share here (it redacts secrets).

#

Also: DM vs group?

  • If you’re DM’ing the bot: send /start to the bot in Telegram.

    • With default config (dmPolicy: "pairing"), you should get a pairing code.
    • Then approve it:
      openclaw pairing list telegram
openclaw pairing approve telegram <CODE>

  • If this is in a group: by default it often requires a mention, and Telegram privacy mode can block non-mention messages. Tell me if it’s a group and whether you’re mentioning the bot.

If you get no pairing code at all

Tail logs while you message the bot:

openclaw logs --follow