Bug: Telegram long-polling receives no inbound messages
✅Solved
Bug: Telegram long-polling receives no inbound messages
OpenClaw version: 2026.2.14 (just updated),
openclaw doctor shows Telegram OK,
openclaw status --deep shows Telegram OK,
Outbound sendMessage works,
getUpdates via curl (with gateway stopped) returns messages correctly,
getUpdates via curl (with gateway running) returns 409 (confirming gateway IS polling),
But zero Telegram messages ever reach the agent,
No errors, no policy blocks, nothing in logs,
Discord and WhatsApp work perfectly on the same setup,
Tried 3 different bot tokens, same result
I was previously able to connect it to my telegram, but moved to my VPS server, could that be the issue?
OpenClaw version: 2026.2.14 (just updated),
openclaw doctor shows Telegram OK,
openclaw status --deep shows Telegram OK,
Outbound sendMessage works,
getUpdates via curl (with gateway stopped) returns messages correctly,
getUpdates via curl (with gateway running) returns 409 (confirming gateway IS polling),
But zero Telegram messages ever reach the agent,
No errors, no policy blocks, nothing in logs,
Discord and WhatsApp work perfectly on the same setup,
Tried 3 different bot tokens, same result
I was previously able to connect it to my telegram, but moved to my VPS server, could that be the issue?
Solution
Quick fix (safe; just makes a backup)
Stop gateway, move the offset file out of the way, restart:Then DM the bot again.
If you paste the
cat …/update-offset-default.json(Migration footgun reference, since you moved to a VPS: https://docs.openclaw.ai/install/migrating)
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
