hermes - 💡(How to fix) Fix QQ Bot WebSocket session timeout and failure to fetch gateway URL [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
NousResearch/hermes-agent#11493Fetched 2026-04-18 06:00:45
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Participants

Code Example

WebSocket closed: code=4009 reason=Session timed out
Reconnect failed: Failed to get QQ Bot gateway URL
RAW_BUFFERClick to expand / collapse

Bug Description

When connecting Hermes Agent via the QQ Bot platform, the WebSocket connection fails with the following errors:

WebSocket closed: code=4009 reason=Session timed out
Reconnect failed: Failed to get QQ Bot gateway URL

Environment

  • Hermes Agent version: [please fill in]
  • Operating system: [please fill in]
  • QQ Bot setup method: [please describe your configuration]

Steps to Reproduce

  1. [please fill in]
  2. [please fill in]

Expected Behavior

The QQ Bot should maintain a stable WebSocket connection and handle messages normally.

Actual Behavior

After the connection is established, it times out after a period of time, and automatic reconnection fails.

Relevant Logs

(please attach full logs if available)

extent analysis

TL;DR

The WebSocket connection issue between Hermes Agent and QQ Bot platform may be resolved by verifying the QQ Bot gateway URL and ensuring a stable network connection.

Guidance

  • Check the QQ Bot setup method and configuration to ensure it is correctly set up to provide a valid gateway URL.
  • Verify the network connection stability and check for any firewall or proxy settings that might be interfering with the WebSocket connection.
  • Review the Relevant Logs to identify any patterns or errors that could indicate the root cause of the session timeout.
  • Consider testing the connection with a different network or environment to isolate the issue.

Notes

The provided information lacks specific details about the environment, steps to reproduce, and relevant logs, making it challenging to provide a definitive solution. Further investigation and logging are necessary to determine the exact cause of the issue.

Recommendation

Apply workaround: Verify the QQ Bot gateway URL and network connection stability, as these are the most likely causes of the WebSocket connection failure, given the provided error messages.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING