Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: [Bug]: Gateway WebSocket handshake/request regression in 2026.4.25+ — TUI cannot connect on low-core hosts [2 comments, 3 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#73524•Fetched 2026-04-29 06:18:49
View on GitHub
Comments
2
Participants
3
Timeline
9
Reactions
0
Author
harshcatsystems-collabharshcatsystems-collab
Participants
harshcatsystems-collabharshcatsystems-collabsteipetesteipeteVksh07Vksh07
Timeline (top)
commented ×2cross-referenced ×2labeled ×2closed ×1

Title: [Bug]: Gateway WebSocket handshake/request regression in 2026.4.25+ — TUI cannot connect on low-core hosts

Body:

Environment

  • OpenClaw: 2026.4.25 and 2026.4.26 (regression vs 2026.4.14)
  • OS: Debian bookworm (2 CPU, 3.8GB RAM)
  • Node: 22.22.2
  • Gateway: loopback, token auth, 9 plugins, Telegram + Slack channels

Description

After updating from 2026.4.14 to 2026.4.25, the TUI cannot connect to the gateway. WebSocket handshake completes but subsequent RPC requests (agents.list, chat.history) take 2-29 seconds, exceeding the 30s requestTimeoutMs.

On 2026.4.14 with identical config and hardware, TUI connects instantly.

Steps to Reproduce

  1. Working gateway on 2026.4.14, TUI connects instantly
  2. npm install -g [email protected] (or 2026.4.26)
  3. openclaw gateway restart
  4. openclaw tui — stuck at "connecting | idle", eventually "gateway request timeout for connect"

Gateway Logs

Gateway shows requests completing but extremely slowly:

  • agents.list: 1723ms
  • chat.history: 28844ms (nearly hits 30s requestTimeoutMs)

Channels (Telegram, Slack) and HTTP dashboard work fine. Only WebSocket RPC is slow.

Related Issues

  • #51987, #47265, #47931, #50380 — same handshake timeout pattern
  • Root cause appears to be event loop contention during channel/plugin initialization that now persists beyond startup in 2026.4.25+

Workaround

Downgrade to 2026.4.14: npm install -g [email protected]

Open https://github.com/openclaw/openclaw/issues/new and paste this in.

Sources:

Root Cause

Related Issues

  • #51987, #47265, #47931, #50380 — same handshake timeout pattern
  • Root cause appears to be event loop contention during channel/plugin initialization that now persists beyond startup in 2026.4.25+

Fix Action

Fix / Workaround

Workaround

Downgrade to 2026.4.14: npm install -g [email protected]

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Title: [Bug]: Gateway WebSocket handshake/request regression in 2026.4.25+ — TUI cannot connect on low-core hosts

Body:

Environment

  • OpenClaw: 2026.4.25 and 2026.4.26 (regression vs 2026.4.14)
  • OS: Debian bookworm (2 CPU, 3.8GB RAM)
  • Node: 22.22.2
  • Gateway: loopback, token auth, 9 plugins, Telegram + Slack channels

Description

After updating from 2026.4.14 to 2026.4.25, the TUI cannot connect to the gateway. WebSocket handshake completes but subsequent RPC requests (agents.list, chat.history) take 2-29 seconds, exceeding the 30s requestTimeoutMs.

On 2026.4.14 with identical config and hardware, TUI connects instantly.

Steps to Reproduce

  1. Working gateway on 2026.4.14, TUI connects instantly
  2. npm install -g [email protected] (or 2026.4.26)
  3. openclaw gateway restart
  4. openclaw tui — stuck at "connecting | idle", eventually "gateway request timeout for connect"

Gateway Logs

Gateway shows requests completing but extremely slowly:

  • agents.list: 1723ms
  • chat.history: 28844ms (nearly hits 30s requestTimeoutMs)

Channels (Telegram, Slack) and HTTP dashboard work fine. Only WebSocket RPC is slow.

Related Issues

  • #51987, #47265, #47931, #50380 — same handshake timeout pattern
  • Root cause appears to be event loop contention during channel/plugin initialization that now persists beyond startup in 2026.4.25+

Workaround

Downgrade to 2026.4.14: npm install -g [email protected]

Open https://github.com/openclaw/openclaw/issues/new and paste this in.

Sources:

Steps to reproduce

Steps to Reproduce

  1. Working gateway on 2026.4.14, TUI connects instantly
  2. npm install -g [email protected] (or 2026.4.26)
  3. openclaw gateway restart
  4. openclaw tui — stuck at "connecting | idle", eventually "gateway request timeout for connect"

Expected behavior

Steps:

  1. Working gateway on 2026.4.14, TUI connects instantly
  2. npm install -g [email protected]
  3. openclaw gateway restart
  4. openclaw tui — stuck at "connecting | idle", eventually "gateway request timeout for connect"

Actual behavior

Description/Steps to reproduce: After updating from 2026.4.14 to 2026.4.25, the TUI cannot connect to the gateway. WebSocket handshake completes but subsequent RPC requests (agents.list, chat.history) take 2-29 seconds, exceeding the 30s requestTimeoutMs. On 2026.4.14 with identical config and hardware, TUI connects instantly.

OpenClaw version

2026.4.25 and 2026.4.26 (regression vs 2026.4.14)

Operating system

Debian bookworm, 2 CPU, 3.8GB RAM, Node 22.22.2

Install method

No response

Model

claude-sonnet-4-6

Provider / routing chain

anthropic-messages (direct API key, no router)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

Downgrade to OpenClaw version 2026.4.14 to resolve the WebSocket handshake and request regression issue.

Guidance

  • The issue seems to be related to event loop contention during channel/plugin initialization, which persists beyond startup in versions 2026.4.25 and later.
  • To verify the issue, check the gateway logs for slow request completion times, such as agents.list and chat.history taking longer than expected.
  • As a temporary workaround, downgrading to version 2026.4.14 resolves the issue, as it does not exhibit the same event loop contention problem.
  • Reviewing related issues (#51987, #47265, #47931, #50380) may provide additional insight into the root cause and potential fixes.

Example

No code snippet is provided, as the issue is related to a specific version regression and not a code-based problem.

Notes

The exact cause of the event loop contention is not specified, but it appears to be related to changes introduced in version 2026.4.25. Downgrading to 2026.4.14 is a reliable workaround, but it may not be a long-term solution.

Recommendation

Apply the workaround by downgrading to OpenClaw version 2026.4.14, as it is a known stable version that does not exhibit the regression issue. This will allow for continued use of the TUI while a permanent fix is developed for the event loop contention problem.

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

Steps:

  1. Working gateway on 2026.4.14, TUI connects instantly
  2. npm install -g [email protected]
  3. openclaw gateway restart
  4. openclaw tui — stuck at "connecting | idle", eventually "gateway request timeout for connect"
#api#search optimization#API routing#API middleware#request timeout

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]: [Bug]: Gateway WebSocket handshake/request regression in 2026.4.25+ — TUI cannot connect on low-core hosts [2 comments, 3 participants]