openclaw - 💡(How to fix) Fix [Bug]: Gateway fails to accept WebSocket connections after upgrade to 2026.4.24 — event loop blocked during channel initialization [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#72164Fetched 2026-04-27 05:33:58
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×2closed ×1commented ×1subscribed ×1

Title: Gateway fails to accept WebSocket connections after upgrade to 2026.4.24 — event loop blocked during channel initialization


Environment

  • OpenClaw version: 2026.4.24 (cbcfdf6)
  • Previous working version: 2026.4.23
  • OS: Ubuntu (Linux, ARM64)
  • Node: 24.14.1
  • Install method: sudo npm i -g openclaw@latest
  • Mode: local, bind: loopback, port: 18789

Description

After upgrading from 2026.4.23 to 2026.4.24, the gateway starts and binds to port 18789, but never accepts WebSocket connections. openclaw channels status consistently returns a timeout or abnormal closure, and all configured channels (Telegram, Discord) stop receiving messages.


Steps to reproduce

  1. Upgrade from 2026.4.23 to 2026.4.24 via sudo npm i -g openclaw@latest
  2. Run openclaw gateway run --bind loopback --port 18789
  3. Observe the gateway log — it reaches starting channels and sidecars... and stops producing output
  4. Run openclaw channels status — returns timeout or 1006 abnormal closure
  5. Attempt a raw TCP connection to 127.0.0.1:18789 — TCP handshake succeeds, but HTTP/WebSocket upgrade request receives no response

Observed behavior

  Gateway log progression:
  [gateway] loading configuration…
  [gateway] resolving authentication…
  [gateway] starting...
  [plugins] <per-plugin dep installs>
  [gateway] starting HTTP server...
  [gateway] ready (5 plugins: browser, discord, memory-core, memory-wiki, telegram; ~120s)
  [gateway] starting channels and sidecars...
  [hooks] loaded 4 internal hook handlers
  [tailscale] serve enabled: ...

After starting channels and sidecars..., no further channel connection logs appear (no Telegram polling started, no Discord connected). The WebSocket server accepts TCP connections but never responds to HTTP upgrade requests, suggesting the event loop is blocked during channel initialization. After 300 seconds, the health monitor fires:

 Health check failed: Error: gateway timeout after 10000ms
 killing 1 stale gateway process(es) before restart: <pid>

This triggers a restart loop.


Additional issue: bundled plugin deps reinstalled on every run After upgrading, every gateway start (and every openclaw status / openclaw channels status invocation) triggers a full reinstall of all bundled plugin runtime deps, including grammy, typebox, undici, ws, discord-api-types, etc. Running openclaw doctor --fix does not permanently resolve this — the next invocation treats the same packages as missing again.

Observed in the gateway log and in openclaw status output on every separate process invocation.

Additional issue: Discord plugin module resolution failure On some gateway starts, the Discord plugin fails at the register stage:

 [plugins] discord failed during register from .../dist/extensions/discord/index.js:
  Error: Cannot find module 'discord-api-types/v10'
  Require stack:
  - /home/ubuntu/.openclaw/plugin-runtime-deps/openclaw-unknown-c1d01dbe639a/dist/extensions/discord/components-AfY8KcWW.js

Note the openclaw-unknown-c1d01dbe639a path — the version component is unknown, which may be why installed deps are not found on subsequent runs.


Expected behavior Gateway completes channel initialization, WebSocket server responds to connections, and openclaw channels status reports connected channels.

Workaround Rolling back to 2026.4.23 restores normal operation.


Error Message

Health check failed: Error: gateway timeout after 10000ms killing 1 stale gateway process(es) before restart: <pid>

Root Cause

Title: Gateway fails to accept WebSocket connections after upgrade to 2026.4.24 — event loop blocked during channel initialization


Environment

  • OpenClaw version: 2026.4.24 (cbcfdf6)
  • Previous working version: 2026.4.23
  • OS: Ubuntu (Linux, ARM64)
  • Node: 24.14.1
  • Install method: sudo npm i -g openclaw@latest
  • Mode: local, bind: loopback, port: 18789

Description

After upgrading from 2026.4.23 to 2026.4.24, the gateway starts and binds to port 18789, but never accepts WebSocket connections. openclaw channels status consistently returns a timeout or abnormal closure, and all configured channels (Telegram, Discord) stop receiving messages.


Steps to reproduce

  1. Upgrade from 2026.4.23 to 2026.4.24 via sudo npm i -g openclaw@latest
  2. Run openclaw gateway run --bind loopback --port 18789
  3. Observe the gateway log — it reaches starting channels and sidecars... and stops producing output
  4. Run openclaw channels status — returns timeout or 1006 abnormal closure
  5. Attempt a raw TCP connection to 127.0.0.1:18789 — TCP handshake succeeds, but HTTP/WebSocket upgrade request receives no response

Observed behavior

  Gateway log progression:
  [gateway] loading configuration…
  [gateway] resolving authentication…
  [gateway] starting...
  [plugins] <per-plugin dep installs>
  [gateway] starting HTTP server...
  [gateway] ready (5 plugins: browser, discord, memory-core, memory-wiki, telegram; ~120s)
  [gateway] starting channels and sidecars...
  [hooks] loaded 4 internal hook handlers
  [tailscale] serve enabled: ...

After starting channels and sidecars..., no further channel connection logs appear (no Telegram polling started, no Discord connected). The WebSocket server accepts TCP connections but never responds to HTTP upgrade requests, suggesting the event loop is blocked during channel initialization. After 300 seconds, the health monitor fires:

 Health check failed: Error: gateway timeout after 10000ms
 killing 1 stale gateway process(es) before restart: <pid>

This triggers a restart loop.


Additional issue: bundled plugin deps reinstalled on every run After upgrading, every gateway start (and every openclaw status / openclaw channels status invocation) triggers a full reinstall of all bundled plugin runtime deps, including grammy, typebox, undici, ws, discord-api-types, etc. Running openclaw doctor --fix does not permanently resolve this — the next invocation treats the same packages as missing again.

Observed in the gateway log and in openclaw status output on every separate process invocation.

Additional issue: Discord plugin module resolution failure On some gateway starts, the Discord plugin fails at the register stage:

 [plugins] discord failed during register from .../dist/extensions/discord/index.js:
  Error: Cannot find module 'discord-api-types/v10'
  Require stack:
  - /home/ubuntu/.openclaw/plugin-runtime-deps/openclaw-unknown-c1d01dbe639a/dist/extensions/discord/components-AfY8KcWW.js

Note the openclaw-unknown-c1d01dbe639a path — the version component is unknown, which may be why installed deps are not found on subsequent runs.


Expected behavior Gateway completes channel initialization, WebSocket server responds to connections, and openclaw channels status reports connected channels.

Workaround Rolling back to 2026.4.23 restores normal operation.


Fix Action

Fix / Workaround

Title: Gateway fails to accept WebSocket connections after upgrade to 2026.4.24 — event loop blocked during channel initialization


Expected behavior Gateway completes channel initialization, WebSocket server responds to connections, and openclaw channels status reports connected channels.

Workaround Rolling back to 2026.4.23 restores normal operation.

Code Example

Gateway log progression:
  [gateway] loading configuration…
  [gateway] resolving authentication…
  [gateway] starting...
  [plugins] <per-plugin dep installs>
  [gateway] starting HTTP server...
  [gateway] ready (5 plugins: browser, discord, memory-core, memory-wiki, telegram; ~120s)
  [gateway] starting channels and sidecars...
  [hooks] loaded 4 internal hook handlers
  [tailscale] serve enabled: ...

---

Health check failed: Error: gateway timeout after 10000ms
 killing 1 stale gateway process(es) before restart: <pid>

---

[plugins] discord failed during register from .../dist/extensions/discord/index.js:
  Error: Cannot find module 'discord-api-types/v10'
  Require stack:
  - /home/ubuntu/.openclaw/plugin-runtime-deps/openclaw-unknown-c1d01dbe639a/dist/extensions/discord/components-AfY8KcWW.js

---

Gateway log progression:
  [gateway] loading configuration…
  [gateway] resolving authentication…
  [gateway] starting...
  [plugins] <per-plugin dep installs>
  [gateway] starting HTTP server...
  [gateway] ready (5 plugins: browser, discord, memory-core, memory-wiki, telegram; ~120s)
  [gateway] starting channels and sidecars...
  [hooks] loaded 4 internal hook handlers
  [tailscale] serve enabled: ...

---

Health check failed: Error: gateway timeout after 10000ms
 killing 1 stale gateway process(es) before restart: <pid>

---
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Title: Gateway fails to accept WebSocket connections after upgrade to 2026.4.24 — event loop blocked during channel initialization


Environment

  • OpenClaw version: 2026.4.24 (cbcfdf6)
  • Previous working version: 2026.4.23
  • OS: Ubuntu (Linux, ARM64)
  • Node: 24.14.1
  • Install method: sudo npm i -g openclaw@latest
  • Mode: local, bind: loopback, port: 18789

Description

After upgrading from 2026.4.23 to 2026.4.24, the gateway starts and binds to port 18789, but never accepts WebSocket connections. openclaw channels status consistently returns a timeout or abnormal closure, and all configured channels (Telegram, Discord) stop receiving messages.


Steps to reproduce

  1. Upgrade from 2026.4.23 to 2026.4.24 via sudo npm i -g openclaw@latest
  2. Run openclaw gateway run --bind loopback --port 18789
  3. Observe the gateway log — it reaches starting channels and sidecars... and stops producing output
  4. Run openclaw channels status — returns timeout or 1006 abnormal closure
  5. Attempt a raw TCP connection to 127.0.0.1:18789 — TCP handshake succeeds, but HTTP/WebSocket upgrade request receives no response

Observed behavior

  Gateway log progression:
  [gateway] loading configuration…
  [gateway] resolving authentication…
  [gateway] starting...
  [plugins] <per-plugin dep installs>
  [gateway] starting HTTP server...
  [gateway] ready (5 plugins: browser, discord, memory-core, memory-wiki, telegram; ~120s)
  [gateway] starting channels and sidecars...
  [hooks] loaded 4 internal hook handlers
  [tailscale] serve enabled: ...

After starting channels and sidecars..., no further channel connection logs appear (no Telegram polling started, no Discord connected). The WebSocket server accepts TCP connections but never responds to HTTP upgrade requests, suggesting the event loop is blocked during channel initialization. After 300 seconds, the health monitor fires:

 Health check failed: Error: gateway timeout after 10000ms
 killing 1 stale gateway process(es) before restart: <pid>

This triggers a restart loop.


Additional issue: bundled plugin deps reinstalled on every run After upgrading, every gateway start (and every openclaw status / openclaw channels status invocation) triggers a full reinstall of all bundled plugin runtime deps, including grammy, typebox, undici, ws, discord-api-types, etc. Running openclaw doctor --fix does not permanently resolve this — the next invocation treats the same packages as missing again.

Observed in the gateway log and in openclaw status output on every separate process invocation.

Additional issue: Discord plugin module resolution failure On some gateway starts, the Discord plugin fails at the register stage:

 [plugins] discord failed during register from .../dist/extensions/discord/index.js:
  Error: Cannot find module 'discord-api-types/v10'
  Require stack:
  - /home/ubuntu/.openclaw/plugin-runtime-deps/openclaw-unknown-c1d01dbe639a/dist/extensions/discord/components-AfY8KcWW.js

Note the openclaw-unknown-c1d01dbe639a path — the version component is unknown, which may be why installed deps are not found on subsequent runs.


Expected behavior Gateway completes channel initialization, WebSocket server responds to connections, and openclaw channels status reports connected channels.

Workaround Rolling back to 2026.4.23 restores normal operation.


Steps to reproduce

Steps to reproduce

  1. Upgrade from 2026.4.23 to 2026.4.24 via sudo npm i -g openclaw@latest
  2. Run openclaw gateway run --bind loopback --port 18789
  3. Observe the gateway log — it reaches starting channels and sidecars... and stops producing output
  4. Run openclaw channels status — returns timeout or 1006 abnormal closure
  5. Attempt a raw TCP connection to 127.0.0.1:18789 — TCP handshake succeeds, but HTTP/WebSocket upgrade request receives no response

Expected behavior

The project must goes well.

Actual behavior

Observed behavior

  Gateway log progression:
  [gateway] loading configuration…
  [gateway] resolving authentication…
  [gateway] starting...
  [plugins] <per-plugin dep installs>
  [gateway] starting HTTP server...
  [gateway] ready (5 plugins: browser, discord, memory-core, memory-wiki, telegram; ~120s)
  [gateway] starting channels and sidecars...
  [hooks] loaded 4 internal hook handlers
  [tailscale] serve enabled: ...

After starting channels and sidecars..., no further channel connection logs appear (no Telegram polling started, no Discord connected). The WebSocket server accepts TCP connections but never responds to HTTP upgrade requests, suggesting the event loop is blocked during channel initialization. After 300 seconds, the health monitor fires:

 Health check failed: Error: gateway timeout after 10000ms
 killing 1 stale gateway process(es) before restart: <pid>

This triggers a restart loop.


OpenClaw version

2026.4.24

Operating system

Ubuntu 24.04

Install method

by npm global.

Model

Claude-cli, Openai-codex/gpt5.5

Provider / routing chain

Claude Cli,Codex

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The most likely fix is to roll back to OpenClaw version 2026.4.23, as it is reported to restore normal operation.

Guidance

  • Verify that the issue is indeed caused by the upgrade to 2026.4.24 by checking the gateway log for any errors or warnings during channel initialization.
  • Check the plugin dependencies, especially the Discord plugin, for any version conflicts or missing modules, as indicated by the error message "Cannot find module 'discord-api-types/v10'".
  • Investigate the event loop blocking issue during channel initialization, which may be related to the bundled plugin dependencies being reinstalled on every run.
  • Consider running openclaw doctor --fix to resolve any potential issues with the plugin dependencies, although it may not permanently resolve the issue.

Example

No code snippet is provided as the issue is more related to configuration and dependency management.

Notes

The issue seems to be specific to the 2026.4.24 version of OpenClaw, and rolling back to the previous version may be the most straightforward solution. However, it is essential to investigate the root cause of the issue to prevent similar problems in the future.

Recommendation

Apply the workaround by rolling back to OpenClaw version 2026.4.23, as it is reported to restore normal operation. This will allow for further investigation and debugging of the issue without disrupting the service.

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

The project must goes well.

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]: Gateway fails to accept WebSocket connections after upgrade to 2026.4.24 — event loop blocked during channel initialization [1 comments, 2 participants]