FIX for Unhandled promise rejection: TypeError: fetch failed
Issue: Gateway Crashes on /new Command - Telegram Fetch Failed
Error Message
Unhandled promise rejection: TypeError: fetch failed
at node:internal/deps/undici/undici:16416:13
at processTicksAndRejections (node:internal/process/task_queues:103:5)
Root Cause
The Telegram channel crashes when calling setMyCommands during initialization due to network connectivity issues with api.telegram.org. Common causes include:
IPv6 Resolution Issue: The server resolves api.telegram.org to IPv6 but doesn't have working IPv6 egress
DNS/HTTPS Blocking: Outbound HTTPS/DNS to api.telegram.org may be blocked
Node.js 22+ AbortSignal Issues: Node 22+ has stricter AbortSignal handling that can cause fetch failures
Solution: Fix IPv6 Routing (Most Common)
bash# Check if you have IPv6 connectivity
ping6 api.telegram.org
Alternative Solutions
If on Node.js 22+, downgrade to Node 20:
bash# Check your Node version
node --version
nvm use 20
Check firewall/network access:
bash# Test connectivity to Telegram API
curl -v https://api.telegram.org/
Error Message
Unhandled promise rejection: TypeError: fetch failed
at node:internal/deps/undici/undici:16416:13
at processTicksAndRejections (node:internal/process/task_queues:103:5)
Root Cause
The Telegram channel crashes when calling setMyCommands during initialization due to network connectivity issues with api.telegram.org. Common causes include:
IPv6 Resolution Issue: The server resolves api.telegram.org to IPv6 but doesn't have working IPv6 egress
DNS/HTTPS Blocking: Outbound HTTPS/DNS to api.telegram.org may be blocked
Node.js 22+ AbortSignal Issues: Node 22+ has stricter AbortSignal handling that can cause fetch failures
Solution: Fix IPv6 Routing (Most Common)
bash# Check if you have IPv6 connectivity
ping6 api.telegram.org
If it fails, get the IPv4 address
dig A api.telegram.orgAdd IPv4 resolution to /etc/hosts
echo "<IPv4_ADDRESS> api.telegram.org" | sudo tee -a /etc/hostsRestart the gateway
clawdbot gateway restartAlternative Solutions
If on Node.js 22+, downgrade to Node 20:
bash# Check your Node version
node --version
If Node 22+, downgrade to Node 20
nvm install 20nvm use 20
Reinstall moltbot
npm install -g moltbot@latestRestart the gateway
clawdbot gateway restartCheck firewall/network access:
bash# Test connectivity to Telegram API
curl -v https://api.telegram.org/
If it fails, allow HTTPS outbound (UFW example)
sudo ufw allow out 443/tcp
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?
