telegram setMyCommands failed: HttpError: Network request for 'setMyCommands' fa
hey @Krill ๐ฆ im seeing "telegram setMyCommands failed: HttpError: Network request for 'setMyCommands' failed!" in my gateway logs, and when i send messages on telegram nothing happens.
Solution
hey just to let everyone know:
Summary: Telegram Connection Error
The Problem:
When running clawdbot gateway, the Telegram provider failed with:
[telegram] telegram setMyCommands failed: HttpError: Network request for 'setMyCommands' failed!
The bot wasn't receiving messages because the Node.js process couldn't establish a connection to Telegram's API.
Root Cause:
- Tailscale was active with DNS server 100.100.100.100
- This DNS resolver was handling api.telegram.org queries differently than expected
- Node.js (clawdbot) couldn't establish a proper connection through this DNS path
- Regular curl worked because it handles DNS/connections differently than Node.js's https module
The Solution:
Added a static entry to /etc/hosts:
149.154.166.110 api.telegram.org
This bypassed Tailscale's DNS entirely and forced Telegram's API to resolve to a direct IP that Node.js could connect to reliably.
Result:
Node.js can now reach Telegram successfully, and clawdbot should receive messages properly.
Summary: Telegram Connection Error
The Problem:
When running clawdbot gateway, the Telegram provider failed with:
[telegram] telegram setMyCommands failed: HttpError: Network request for 'setMyCommands' failed!
The bot wasn't receiving messages because the Node.js process couldn't establish a connection to Telegram's API.
Root Cause:
- Tailscale was active with DNS server 100.100.100.100
- This DNS resolver was handling api.telegram.org queries differently than expected
- Node.js (clawdbot) couldn't establish a proper connection through this DNS path
- Regular curl worked because it handles DNS/connections differently than Node.js's https module
The Solution:
Added a static entry to /etc/hosts:
149.154.166.110 api.telegram.org
This bypassed Tailscale's DNS entirely and forced Telegram's API to resolve to a direct IP that Node.js could connect to reliably.
Result:
Node.js can now reach Telegram successfully, and clawdbot should receive messages properly.
