Openclaw not responding on telegram but gateway and everything installed and working fine

[lost flax]

As the title says the openclaw isn't responding on telegram it's on a hetzner server was working previously Gateway: restarted and verified. we're on the latest version just updated did openclaw gateway probe etc maybe I had a big job running and it's not responding idk.

[pale remnant]

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

[clever escarp]

First thing: please paste the exact openclaw --version even if you just updated. Version skew after an update/restart is a common cause here.

For Telegram specifically, run this ladder on the Hetzner box and paste the relevant output, with tokens redacted:

openclaw status --all
openclaw gateway probe
openclaw gateway status
openclaw channels status --probe
openclaw pairing list telegram
openclaw logs --follow

What I’d look for:

• channels status --probe says whether Telegram transport is actually connected/probing cleanly.
• pairing list telegram catches the common “/start but not approved / DM policy changed” case.
• Logs should show whether Telegram polling is stalled, API calls are failing, or OpenClaw is receiving messages but dropping them due to policy/allowlist/mention rules.

[clever escarp]

• If it’s a group: check BotFather privacy mode / whether the bot is admin, and whether your group + sender allowlists still match after the update.
• If a big job wedged a session, the logs/status output should show stuck/active runs; don’t delete state blind until we see that.

Docs for the exact triage flow:
https://docs.openclaw.ai/help/troubleshooting
https://docs.openclaw.ai/channels/troubleshooting
https://docs.openclaw.ai/channels/telegram

[lost flax]

openclaw --version
OpenClaw 2026.5.27 (27ae826)

Targets
Local loopback ws://127.0.0.1:18789
Connect: ok (36ms) · Capability: connect-only · Read probe: limited - missing scope: operator.read

[clever escarp]

That output says the gateway WebSocket is reachable, but your local CLI only has connect-level access for the read probe. That operator.read line is degraded diagnostics, not proof that Telegram is broken.

Next useful bit is the channel probe/logs:

openclaw channels status --probe
openclaw pairing list telegram
openclaw logs --follow

For the logs, send the smallest chunk around a Telegram message you just sent to the bot. I’m looking for either polling/API errors, pairing/allowlist drops, or “message received but ignored” policy lines.

Docs reference: https://docs.openclaw.ai/help/troubleshooting and https://docs.openclaw.ai/channels/telegram