openclaw - 💡(How to fix) Fix [Bug]: Telegram: all outbound API calls fail (sendMessage, sendChatAction, editMessageText) while inbound polling works [1 comments, 2 participants]

[telegram] autoSelectFamily=true (config) [telegram] dnsResultOrder=ipv4first (config) [telegram] Polling stall detected (no getUpdates for 109.65s); forcing restart. [telegram] telegram sendChatAction failed: Network request for 'sendChatAction' failed! [telegram] telegram sendMessage failed: Network request for 'sendMessage' failed! [telegram] telegram final reply failed: HttpError: Network request for 'sendMessage' failed!

Workarounds already attempted without success:

• Fixed IPv4 entry in Windows hosts file (149.154.166.110 api.telegram.org)
• Windows Firewall rule blocking Telegram IPv6 address (2001:67c:4e8:f004::9)
• autoSelectFamily: true + dnsResultOrder: ipv4first in config
• Upgraded Node.js from v24 to v25
• Updated OpenClaw from 2026.3.13 to 2026.3.23-2
• Verified no active webhook (getWebhookInfo returns empty url)
• Direct Node fetch test: node -e "fetch('https://api.telegram.org')" → OK status 200

Fix Plan

The fix involves modifying the node configuration and the openclaw gateway to properly handle IPv6 connections.

• Step 1: Disable IPv6 Add the following flag when starting the openclaw gateway: --ipv6=disable Example: openclaw gateway --ipv6=disable
• Step 2: Update node Configuration Set the dnsResultOrder to ipv4only in the node configuration. Example (using JavaScript):

  process.env.NODE_DEBUG = 'dns';
  const dns = require('dns');
  dns.setLookupFunction((hostname, options, callback) => {
    options.family = 4; // ipv4only
    dns.lookup(hostname, options, callback);
  });

• Step 3: Verify openclaw Configuration Ensure that autoSelectFamily is set to true and dnsResultOrder is set to ipv4first in the openclaw configuration. Example (using JSON configuration file):

  {
    "telegram": {
      "autoSelectFamily": true,
      "dnsResultOrder": "ipv4first"
    }
  }

Verification

To verify that the fix worked, restart the openclaw gateway with the updated configuration and test the Telegram channel by sending a message to the bot. The bot should now be able to reply successfully.

Extra Tips

• Ensure that the Windows Firewall is configured to allow outgoing connections to the Telegram API.
• If issues persist, try setting up a proxy server to handle the outgoing connections.
• Keep the node and openclaw versions up to date to ensure that any known issues are fixed.