Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Telegram provider intermittently stalls despite stable direct Bot API connectivity

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Telegram provider intermittently fails with sendMessage/getMe timeouts despite stable direct Bot API connectivity.

Root Cause

Telegram provider intermittently fails with sendMessage/getMe timeouts despite stable direct Bot API connectivity.

Code Example

fetch fallback: DNS-resolved IP unreachable
UND_ERR_CONNECT_TIMEOUT
fetch timeout reached
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Telegram provider intermittently fails with sendMessage/getMe timeouts despite stable direct Bot API connectivity.

Steps to reproduce

  1. Start OpenClaw with Telegram provider enabled.
  2. Configure SOCKS5 proxy.
  3. Use Telegram normally for some time.
  4. Eventually outbound Telegram messages fail while inbound messages still arrive.

Expected behavior

Telegram provider should remain stable under a stable SOCKS5 connection.

Actual behavior

Outbound Telegram requests intermittently fail with:

  • sendMessage failed
  • getMe timeout
  • UND_ERR_CONNECT_TIMEOUT

while direct curl requests to Telegram Bot API remain stable.

OpenClaw version

2026.05.22

Operating system

Ubuntu24

Install method

No response

Model

openai/gpt-5.4

Provider / routing chain

OpenClaw -> grammY/undici -> SOCKS5 proxy -> Telegram Bot API

Additional provider/model setup details

No response

Logs, screenshots, and evidence

fetch fallback: DNS-resolved IP unreachable
UND_ERR_CONNECT_TIMEOUT
fetch timeout reached

Impact and severity

No response

Additional information

Direct Telegram Bot API access via curl is stable (100/100 successful requests through the same proxy).

The issue appears to be inside OpenClaw Telegram transport/fallback handling rather than general network connectivity.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Telegram provider should remain stable under a stable SOCKS5 connection.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Telegram provider intermittently stalls despite stable direct Bot API connectivity