Telegram bot receives messages, but OpenClaw gateway never responds or logs updates
Hi, I’m having trouble with the Telegram channel in OpenClaw and would love some help.
Environment: Ubuntu 24.04.3 LTS on AWS EC2, OpenClaw v2026.1.30.
Bot: @shreyas2917_bot, token 8414…22g is valid.
When the OpenClaw gateway is stopped, calling getUpdates on the Telegram API returns my test message (test123) from my account, so Telegram and the token are working.
When the gateway is running, the logs show normal startup, including agent model: google/gemini-2.0-flash-latest and [telegram] [default] starting provider (@shreyas2917_bot). There are no errors.
In this state, if I send messages like ping_from_openclaw_test to the bot, Telegram shows them as delivered (blue double ticks), but:
The OpenClaw logs show no new lines at all after startup (no inbound message/update logs, no agent run).
Manual getUpdates calls now return an empty result array, suggesting something is consuming the updates, but OpenClaw is not replying or logging anything.
Config I’ve set:
bash
openclaw config set channels.telegram.botToken "<valid token>"
openclaw config set channels.telegram.dmPolicy open
openclaw config set channels.telegram.groupPolicy open
Questions:
Is there any additional setting required to make the Telegram provider actually poll and log incoming updates in 2026.1.30?
Is this a known issue with this version’s Telegram integration, and is there a recommended workaround or version to use instead?
How can I enable more verbose logging for the Telegram channel or the gateway so I can see whether updates are being received and where they fail?
I can share full journalctl --user -u openclaw-gateway snippets around startup and test messages if needed.
Environment: Ubuntu 24.04.3 LTS on AWS EC2, OpenClaw v2026.1.30.
Bot: @shreyas2917_bot, token 8414…22g is valid.
When the OpenClaw gateway is stopped, calling getUpdates on the Telegram API returns my test message (test123) from my account, so Telegram and the token are working.
When the gateway is running, the logs show normal startup, including agent model: google/gemini-2.0-flash-latest and [telegram] [default] starting provider (@shreyas2917_bot). There are no errors.
In this state, if I send messages like ping_from_openclaw_test to the bot, Telegram shows them as delivered (blue double ticks), but:
The OpenClaw logs show no new lines at all after startup (no inbound message/update logs, no agent run).
Manual getUpdates calls now return an empty result array, suggesting something is consuming the updates, but OpenClaw is not replying or logging anything.
Config I’ve set:
bash
openclaw config set channels.telegram.botToken "<valid token>"
openclaw config set channels.telegram.dmPolicy open
openclaw config set channels.telegram.groupPolicy open
I previously tried channels.telegram.allowFrom "*" but reverted after validation error.
openclaw config set agents.defaults.model.primary "google/gemini-2.0-flash-latest"Questions:
Is there any additional setting required to make the Telegram provider actually poll and log incoming updates in 2026.1.30?
Is this a known issue with this version’s Telegram integration, and is there a recommended workaround or version to use instead?
How can I enable more verbose logging for the Telegram channel or the gateway so I can see whether updates are being received and where they fail?
I can share full journalctl --user -u openclaw-gateway snippets around startup and test messages if needed.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Similar Threads
Was this page helpful?
