Fix: Telegram "Network request failed" After v2026.2.26 Upgrade
[Telegram] Network request failed: setMyCommands
[Telegram] Network request failed: sendMessage
After upgrading OpenClaw from v2026.2.23 to v2026.2.26, the Telegram plugin starts logging "Network request failed" for all outbound Telegram API calls — but curl to the same endpoints succeeds. This indicates a Node.js HTTP dispatcher change introduced in the upgrade is breaking the plugin's internal fetch calls, not a network or firewall issue.
Next Step
Fix now, then reduce repeat incidents
If this issue keeps coming back, validate your setup in Doctor first, then harden your config.
Jump to Fix
Step 1: Confirm the Issue Is Node.js, Not the Network
# Test with curl (should succeed)
curl -s https://api.telegram.org | head -5
# Test with Node.js (may fail after upgrade)
node -e "fetch('https://api.telegram.org').then(r=>console.log('node_http='+r.status)).catch(e=>console.error(e.cause?.code,e.message))"
# Also check undici version (used internally by OpenClaw)
node -e "const u=require('undici'); console.log(u.version || 'unknown')"If curl succeeds but node -e "fetch(...)" fails, the dispatcher regression is confirmed.
Step 2: Update to the Latest Patch
A patch was released to revert the dispatcher change. Update to pick it up:
npm install -g openclaw@latest # Restart gateway openclaw gateway restart
Step 3: Check for HTTP_PROXY / HTTPS_PROXY Environment Variables
The setGlobalDispatcher change interacts badly with proxy environment variables. If you have a proxy configured, unset it or add Telegram's API hostname to the no-proxy list:
# Check proxy settings echo $HTTP_PROXY echo $HTTPS_PROXY echo $NO_PROXY # Add Telegram API to no-proxy export NO_PROXY="api.telegram.org,$NO_PROXY" # Or unset proxy entirely for testing unset HTTP_PROXY HTTPS_PROXY
This regression was also tracked in the HTTP proxy setGlobalDispatcher regression guide. See that guide for more dispatcher-related fixes.
Fallback: Downgrade to v2026.2.23
If the patch has not yet been released for your distribution channel, pin to the last known-good version:
npm install -g [email protected] # Verify openclaw --version
After applying the fix, restart the gateway and send a test message to your Telegram bot. The "Network request failed" errors should stop appearing in the logs.
Related network issues
Fix It Faster With Our Tools
Did this guide solve your problem?