Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] QQ token fetch to bots.qq.com times out across A/B uplinks (core healthy) [1 comments, 1 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#71583•Fetched 2026-04-26 05:11:08
View on GitHub
Comments
1
Participants
1
Timeline
1
Reactions
0
Author
Huxyu001Huxyu001
Participants
Huxyu001Huxyu001
Timeline (top)
commented ×1

QQ channel stays disconnected because token fetch to https://bots.qq.com/app/getAppAccessToken times out (http_code=000) even though OpenClaw core gateway/dashboard is healthy.

Root Cause

Summary

QQ channel stays disconnected because token fetch to https://bots.qq.com/app/getAppAccessToken times out (http_code=000) even though OpenClaw core gateway/dashboard is healthy.

Fix Action

Fix / Workaround

Question

Is there any known QQ token-fetch path issue (region/egress/policy) for bots.qq.com:443, or recommended OpenClaw-specific diagnostics/workarounds for this stage?

Code Example

openclaw channels status --probe --json
curl --noproxy '*' -4 -I -sS --connect-timeout 10 --max-time 20 \
  https://bots.qq.com/app/getAppAccessToken -o /dev/null \
  -w 'ipv4_http_code=%{http_code} connect=%{time_connect}s tls=%{time_appconnect}s total=%{time_total}s remote_ip=%{remote_ip}\n'
route -n get 157.255.84.115
RAW_BUFFERClick to expand / collapse

[Bug] QQ token fetch to bots.qq.com times out across A/B uplinks (core healthy)

Summary

QQ channel stays disconnected because token fetch to https://bots.qq.com/app/getAppAccessToken times out (http_code=000) even though OpenClaw core gateway/dashboard is healthy.

Environment

  • OpenClaw 2026.4.23 (stable, up to date)
  • macOS 15.6.1 arm64, Node 24.15.0
  • Gateway LaunchAgent loaded/running, dashboard 127.0.0.1:18789 healthy

Repro

openclaw channels status --probe --json
curl --noproxy '*' -4 -I -sS --connect-timeout 10 --max-time 20 \
  https://bots.qq.com/app/getAppAccessToken -o /dev/null \
  -w 'ipv4_http_code=%{http_code} connect=%{time_connect}s tls=%{time_appconnect}s total=%{time_total}s remote_ip=%{remote_ip}\n'
route -n get 157.255.84.115

Actual

  • QQ endpoint probe times out (http_code=000, connect timeout).
  • QQ channel remains disconnected for all configured QQ accounts.

Expected

  • QQ token endpoint reachable (non-timeout response), QQ channel able to connect.

What I already tried

  • Single-account relogin/revalidation: no change.
  • OpenClaw upgraded to latest stable (2026.4.23): no change.
  • A/B uplink test (different DNS/route/gateway): both fail with same timeout signature.

Evidence

  • A network: state/qq-ab-test/network-A-20260425-202612.txt
  • B network: state/qq-ab-test/network-B-20260425-203715.txt
  • Core health PASS during tests: state/healthcheck-20260425-202612.txt, state/healthcheck-20260425-203715.txt

Question

Is there any known QQ token-fetch path issue (region/egress/policy) for bots.qq.com:443, or recommended OpenClaw-specific diagnostics/workarounds for this stage?

extent analysis

TL;DR

Investigate DNS resolution and routing issues for bots.qq.com as the likely cause of the timeout.

Guidance

  • Verify DNS resolution for bots.qq.com using tools like dig or nslookup to ensure it resolves to the correct IP address.
  • Check the routing table using route -n get 157.255.84.115 to confirm the traffic is taking the expected path.
  • Test the connection to bots.qq.com using a different network or DNS server to isolate the issue.
  • Review the network configuration and firewall rules to ensure they are not blocking the traffic to bots.qq.com.

Example

dig +short bots.qq.com

This command can help verify the DNS resolution for bots.qq.com.

Notes

The issue seems to be related to network connectivity rather than OpenClaw configuration, as the core gateway and dashboard are healthy. The fact that both A/B uplinks fail with the same timeout signature suggests a common issue with the DNS resolution or routing.

Recommendation

Apply workaround by testing the connection to bots.qq.com using a different network or DNS server to isolate the issue, as the root cause is likely related to network configuration rather than OpenClaw itself.

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…
#optimization#mixed precision#training loop#device allocation#model download

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] QQ token fetch to bots.qq.com times out across A/B uplinks (core healthy) [1 comments, 1 participants]