Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: {"subsystem":"fetch-timeout"} [1 comments, 2 participants]

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…
GitHub stats
openclaw/openclaw#75783•Fetched 2026-05-02 05:30:16
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
2
Author
tankotantankotan
Participants
clawsweeper[bot]clawsweeper[bot]tankotantankotan
Timeline (top)
commented ×1labeled ×1

OpenClaw Version: 2026.4.29 (a448042) Node.js Version: 22.22.2 OS: Linux 5.15.0-303.171.5.2.1.el8uek.x86_64 (Oracle Cloud Infrastructure) Installation: npm (sudo npm install -g openclaw) Gateway Port: 18789

Runtime: running (pid 977842, state active, sub running) Connectivity probe: failed Probe target: ws://127.0.0.1:18789 timeout Gateway port 18789 is not listening (service appears running)

{"subsystem":"fetch-timeout"} "fetch timeout reached; aborting operation" "url":"https://api.telegram.org/bot826996…6oMs/getMe" "timeoutMs":2500,"elapsedMs":2500 {"subsystem":"fetch-timeout"} "fetch timeout reached; aborting operation" "timeoutMs":9998,"elapsedMs":18070

{"subsystem":"telegram/native-approvals"} "connect error: scope upgrade pending approval (requestId: ....................)"

{"subsystem":"gateway/channels/telegram"} "native approval handler disabled: ExecApprovalChannelRuntimeTerminalStartError: native approval gateway client paused reconnect after startup auth failure (PAIRING_REQUIRED): gateway closed (1008): pairing required: device is asking for more scopes than currently approved"

{"subsystem":"telegram/api"} "telegram sendChatAction failed: Network request for 'sendChatAction' failed!"

Node.js HTTP Client Issue:​ OpenClaw's internal fetch implementation có thể không tương thích với Node.js 22.22.2 hoặc có bug với HTTPS connections

IPv6/IPv4 Preference:​ Dù đã set --dns-result-order=ipv4first, vẫn có thể có vấn đề với network stack Timeout Configuration:​ Default timeout (2.5s - 10s) có thể quá ngắn cho server có latency cao (172ms đến Telegram) Scope Upgrade Deadlock:​ Cơ chế pairing/scope upgrade bị block khi network timeout xảy ra

Error Message

"connect error: scope upgrade pending approval (requestId: ....................)" Cải thiện error messages để phân biệt network timeout vs auth failure Cải thiện error messages để phân biệt network timeout vs auth failure

Root Cause

OpenClaw Version: 2026.4.29 (a448042) Node.js Version: 22.22.2 OS: Linux 5.15.0-303.171.5.2.1.el8uek.x86_64 (Oracle Cloud Infrastructure) Installation: npm (sudo npm install -g openclaw) Gateway Port: 18789

Runtime: running (pid 977842, state active, sub running) Connectivity probe: failed Probe target: ws://127.0.0.1:18789 timeout Gateway port 18789 is not listening (service appears running)

{"subsystem":"fetch-timeout"} "fetch timeout reached; aborting operation" "url":"https://api.telegram.org/bot826996…6oMs/getMe" "timeoutMs":2500,"elapsedMs":2500 {"subsystem":"fetch-timeout"} "fetch timeout reached; aborting operation" "timeoutMs":9998,"elapsedMs":18070

{"subsystem":"telegram/native-approvals"} "connect error: scope upgrade pending approval (requestId: ....................)"

{"subsystem":"gateway/channels/telegram"} "native approval handler disabled: ExecApprovalChannelRuntimeTerminalStartError: native approval gateway client paused reconnect after startup auth failure (PAIRING_REQUIRED): gateway closed (1008): pairing required: device is asking for more scopes than currently approved"

{"subsystem":"telegram/api"} "telegram sendChatAction failed: Network request for 'sendChatAction' failed!"

Node.js HTTP Client Issue:​ OpenClaw's internal fetch implementation có thể không tương thích với Node.js 22.22.2 hoặc có bug với HTTPS connections

IPv6/IPv4 Preference:​ Dù đã set --dns-result-order=ipv4first, vẫn có thể có vấn đề với network stack Timeout Configuration:​ Default timeout (2.5s - 10s) có thể quá ngắn cho server có latency cao (172ms đến Telegram) Scope Upgrade Deadlock:​ Cơ chế pairing/scope upgrade bị block khi network timeout xảy ra

Fix Action

Fix / Workaround

Severity:​ High Affected Feature:​ Telegram channel integration Workaround:​ Disable Telegram plugin (plugins.entries.telegram.enabled false) Users Affected:​ Anyone deploying OpenClaw on servers with moderate latency to Telegram API

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

OpenClaw Version: 2026.4.29 (a448042) Node.js Version: 22.22.2 OS: Linux 5.15.0-303.171.5.2.1.el8uek.x86_64 (Oracle Cloud Infrastructure) Installation: npm (sudo npm install -g openclaw) Gateway Port: 18789

Runtime: running (pid 977842, state active, sub running) Connectivity probe: failed Probe target: ws://127.0.0.1:18789 timeout Gateway port 18789 is not listening (service appears running)

{"subsystem":"fetch-timeout"} "fetch timeout reached; aborting operation" "url":"https://api.telegram.org/bot826996…6oMs/getMe" "timeoutMs":2500,"elapsedMs":2500 {"subsystem":"fetch-timeout"} "fetch timeout reached; aborting operation" "timeoutMs":9998,"elapsedMs":18070

{"subsystem":"telegram/native-approvals"} "connect error: scope upgrade pending approval (requestId: ....................)"

{"subsystem":"gateway/channels/telegram"} "native approval handler disabled: ExecApprovalChannelRuntimeTerminalStartError: native approval gateway client paused reconnect after startup auth failure (PAIRING_REQUIRED): gateway closed (1008): pairing required: device is asking for more scopes than currently approved"

{"subsystem":"telegram/api"} "telegram sendChatAction failed: Network request for 'sendChatAction' failed!"

Node.js HTTP Client Issue:​ OpenClaw's internal fetch implementation có thể không tương thích với Node.js 22.22.2 hoặc có bug với HTTPS connections

IPv6/IPv4 Preference:​ Dù đã set --dns-result-order=ipv4first, vẫn có thể có vấn đề với network stack Timeout Configuration:​ Default timeout (2.5s - 10s) có thể quá ngắn cho server có latency cao (172ms đến Telegram) Scope Upgrade Deadlock:​ Cơ chế pairing/scope upgrade bị block khi network timeout xảy ra

Steps to reproduce

Giả Thuyết Nguyên Nhân

Node.js HTTP Client Issue:​ OpenClaw's internal fetch implementation có thể không tương thích với Node.js 22.22.2 hoặc có bug với HTTPS connections

IPv6/IPv4 Preference:​ Dù đã set --dns-result-order=ipv4first, vẫn có thể có vấn đề với network stack

Timeout Configuration:​ Default timeout (2.5s - 10s) có thể quá ngắn cho server có latency cao (172ms đến Telegram)

Scope Upgrade Deadlock:​ Cơ chế pairing/scope upgrade bị block khi network timeout xảy ra

​📊 Impact

Severity:​ High Affected Feature:​ Telegram channel integration Workaround:​ Disable Telegram plugin (plugins.entries.telegram.enabled false) Users Affected:​ Anyone deploying OpenClaw on servers with moderate latency to Telegram API

Expected behavior

Gợi Ý Fix Cho Dev Team

Tăng default timeout cho Telegram API calls (hiện tại 2.5s - 10s, nên tăng lên 30s+)

Thêm config option để tùy chỉnh timeout: jsonCopy"channels.telegram.requestTimeout": 30000

Fix scope upgrade deadlock — cho phép bypass pairing khi dmPolicy="allowlist"

Thêm retry logic với exponential backoff cho Telegram API calls

Cải thiện error messages để phân biệt network timeout vs auth failure

Actual behavior

Gợi Ý Fix Cho Dev Team

Tăng default timeout cho Telegram API calls (hiện tại 2.5s - 10s, nên tăng lên 30s+)

Thêm config option để tùy chỉnh timeout: jsonCopy"channels.telegram.requestTimeout": 30000

Fix scope upgrade deadlock — cho phép bypass pairing khi dmPolicy="allowlist"

Thêm retry logic với exponential backoff cho Telegram API calls

Cải thiện error messages để phân biệt network timeout vs auth failure

OpenClaw version

OpenClaw Version: 2026.4.29 (a448042)

Operating system

Linux 5.15.0-303.171.5.2.1.el8uek.x86_64 (Oracle Cloud Infrastructure)

Install method

No response

Model

deepseek

Provider / routing chain

openclaw

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

Increase the default timeout for Telegram API calls to 30s+ and add a config option to customize the timeout.

Guidance

  • Increase the default timeout for Telegram API calls from 2.5s-10s to 30s+ to account for servers with moderate latency to the Telegram API.
  • Add a config option, such as "channels.telegram.requestTimeout": 30000, to allow customization of the timeout.
  • Consider implementing retry logic with exponential backoff for Telegram API calls to handle network timeouts and auth failures.
  • Improve error messages to distinguish between network timeouts and auth failures.

Example

{
  "channels": {
    "telegram": {
      "requestTimeout": 30000
    }
  }
}

Notes

The issue seems to be related to the default timeout being too short for servers with moderate latency to the Telegram API. Increasing the timeout and adding a config option should help resolve the issue. However, further testing and verification are needed to ensure the fix works as expected.

Recommendation

Apply the workaround by increasing the default timeout and adding a config option, as it is a more targeted solution to the problem. This should help resolve the issue without introducing unnecessary changes.

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

Gợi Ý Fix Cho Dev Team

Tăng default timeout cho Telegram API calls (hiện tại 2.5s - 10s, nên tăng lên 30s+)

Thêm config option để tùy chỉnh timeout: jsonCopy"channels.telegram.requestTimeout": 30000

Fix scope upgrade deadlock — cho phép bypass pairing khi dmPolicy="allowlist"

Thêm retry logic với exponential backoff cho Telegram API calls

Cải thiện error messages để phân biệt network timeout vs auth failure

#api#installation#LLM response#prompt template#agent execution

Still need to ship something?

×6

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

Back to top recommendations

TRENDING