Bug: Gateway crash loop when Telegram API is unreachable
Hey! Found an issue where the gateway crashes and won't recover if it can't reach Telegram's API during startup.
What happened:
• My ISP had some packet loss/latency issues
• Gateway tried to start, couldn't reach api.telegram.org
• The setMyCommands call failed and threw an unhandled promise rejection
• Gateway crashed, systemd restarted it, same thing, crash loop
• Restart counter hit 73 before I rebooted the VM
Error from logs:
[telegram] setMyCommands failed: HttpError: Network request for 'setMyCommands' failed!
[clawdbot] Unhandled promise rejection: TypeError: fetch failed
Version: 2026.1.23-1
Suggestion: Could the setMyCommands call be wrapped in a try/catch so it doesn't crash the whole gateway? It's not critical for the bot to work.
Workaround: Added RestartSec=30 to systemd to slow down the restart loop.
What happened:
• My ISP had some packet loss/latency issues
• Gateway tried to start, couldn't reach api.telegram.org
• The setMyCommands call failed and threw an unhandled promise rejection
• Gateway crashed, systemd restarted it, same thing, crash loop
• Restart counter hit 73 before I rebooted the VM
Error from logs:
[telegram] setMyCommands failed: HttpError: Network request for 'setMyCommands' failed!
[clawdbot] Unhandled promise rejection: TypeError: fetch failed
Version: 2026.1.23-1
Suggestion: Could the setMyCommands call be wrapped in a try/catch so it doesn't crash the whole gateway? It's not critical for the bot to work.
Workaround: Added RestartSec=30 to systemd to slow down the restart loop.
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?
