solution channel high linux macos windows telegram

Telegram: network request failed (sendMessage/sendChatAction) due to IPv6/DNS

Fix Telegram API failures by addressing IPv6-first DNS on hosts without IPv6 egress, or by fixing outbound DNS/HTTPS reachability to api.telegram.org.

By CoClaw Team •

Symptoms

  • Gateway logs show errors like:
    • HttpError: Network request for 'sendMessage' failed
    • HttpError: Network request for 'sendChatAction' failed
  • setMyCommands may also fail on startup.

Cause

Most often:

  • api.telegram.org resolves to IPv6 first, but your host has no IPv6 egress, or
  • outbound DNS/HTTPS to api.telegram.org is blocked/restricted on the gateway host.

Fix

1) Probe Telegram from OpenClaw

On the gateway host:

openclaw channels status --probe

If Telegram probes fail, continue below.

2) If your host does not support IPv6, force IPv4 (common on VPS)

Options (pick one that matches your environment):

  • Enable IPv6 on the host/network, or
  • Configure the host to prefer IPv4 / disable IPv6 DNS resolution for this environment.

Then restart the gateway.

3) If you’re on a restricted network

Run the gateway on a host with reliable egress to Telegram (VPS), or use a network path that can reach api.telegram.org.

Verify

  • openclaw channels status --probe reports Telegram healthy.
  • A test Telegram message triggers a response.

Verification & references

  • Reviewed by:CoClaw Code Team
  • Last reviewed:March 14, 2026
  • Verified on: Linux · macOS · Windows

References

Official docs

  1. OpenClaw docs: /channels/telegram
  2. OpenClaw docs: /channels/troubleshooting
Want to explore more? Browse all solutions or ask in the Community Forum .
Report a problem

Related Resources

Telegram: 'setMyCommands failed' / Bot API requests fail
Fix
Fix Telegram Bot API failures caused by outbound HTTPS/DNS/IPv6 issues to api.telegram.org (common on restricted VPS or proxies).
Telegram: channel stops working because persisted session state JSON is bad
Fix
Recover a Telegram channel that looks mysteriously broken by identifying the bad persisted Telegram session-state JSON, backing it up, resetting only that file, and restarting the gateway.
Telegram: bot shows connected but receives no messages
Fix
Fix Telegram bots that start successfully but don't receive updates by checking privacy mode, webhook/polling conflicts, and network reachability.
Telegram: bot is in a group but never responds
Fix
Fix Telegram group response issues caused by allowlist/groups config, requireMention, or Telegram privacy mode/admin permissions.
Telegram + OpenClaw: Setup, Group Controls, and Common Pitfalls
Guide
Set up Telegram for OpenClaw with safe DM and group controls, privacy-mode awareness, and a verification path that proves the bot sees the right messages.
OpenClaw Not Responding: Fix 'no output', Incorrect API, Rate Limits, and Silent Failures
Guide
A high-signal checklist for when OpenClaw stops replying (TUI shows '(no output)', channels go quiet, or logs show 401/403/429). Covers config precedence, provider auth, model allowlists, relay API-mode mismatch, and rate-limit/billing traps.