Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: 2026.4.25: Gateway hangs/timeouts after update; plugin-runtime-deps missing packages [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#72992•Fetched 2026-04-28 06:29:02
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
1
Author
Schnup03Schnup03
Participants
Schnup03Schnup03steipetesteipete
Timeline (top)
cross-referenced ×3labeled ×2closed ×1commented ×1

I am not very experienced with Linux/WSL, but several Discord users appear to be hitting the same issue, so I am collecting the symptoms here. Multiple Discord users are reporting serious Gateway failures after updating to OpenClaw 2026.4.25.

Common symptoms:

  • openclaw status / WS health timeout
  • service reports running, but Gateway is unreachable
  • /healthz sometimes times out or port is not listening
  • Gateway did not become healthy after restart
  • Completion cache update failed: spawnSync node ETIMEDOUT
  • bundled runtime deps missing:
    • Cannot find package 'chokidar'
    • Cannot find module '@hapi/hoek'
    • Cannot find module 'discord-api-types/v10.js'
    • Cannot find module 'typebox/build/index.mjs'
  • npm ENOTEMPTY rename ... node_modules/...
  • browser runtime deps fail to stage: @modelcontextprotocol/sdk, playwright-core Affected reports include:
  • Gateway not responding after update 2026.4.23 -> 2026.4.25
  • Gateway Broken after Update
  • Gateway entrypoint problem
  • OpenClaw slow after updating to 2026.4.25
  • Gateway not starting after updating to 2026.4.25
  • qmd memory unavailable / active memory timeouts

One WSL2 case:

  • OpenClaw 2026.4.25 aa36ee6
  • WSL2 Linux 6.6.87.2
  • Node initially 22.22.2, later 24.15.0 via nvm
  • systemd user gateway
  • bind lan / port 18789
  • plugin-runtime-deps root became partially installed
  • manual npm install inside plugin-runtime-deps pruned 739 packages
  • moving runtime deps aside + doctor did not fully recover consistently
  • OPENCLAW_SKIP_CHANNELS=1 OPENCLAW_SKIP_PROVIDERS=1 can start core after ~30s, but normal service still wedges around channels/runtime deps
  • downgrade to 2026.4.23 may not help unless runtime-deps cache/service state are cleaned too

Important warning: Users should not manually run npm install inside ~/.openclaw/plugin-runtime-deps; it is OpenClaw-managed and npm can prune packages.

Suspected area: 2026.4.25 bundled plugin runtime dependency staging / mirror rebuild / service restart recovery regression, possibly related to issue #72933.

Root Cause

I am not very experienced with Linux/WSL, but several Discord users appear to be hitting the same issue, so I am collecting the symptoms here. Multiple Discord users are reporting serious Gateway failures after updating to OpenClaw 2026.4.25.

Common symptoms:

  • openclaw status / WS health timeout
  • service reports running, but Gateway is unreachable
  • /healthz sometimes times out or port is not listening
  • Gateway did not become healthy after restart
  • Completion cache update failed: spawnSync node ETIMEDOUT
  • bundled runtime deps missing:
    • Cannot find package 'chokidar'
    • Cannot find module '@hapi/hoek'
    • Cannot find module 'discord-api-types/v10.js'
    • Cannot find module 'typebox/build/index.mjs'
  • npm ENOTEMPTY rename ... node_modules/...
  • browser runtime deps fail to stage: @modelcontextprotocol/sdk, playwright-core Affected reports include:
  • Gateway not responding after update 2026.4.23 -> 2026.4.25
  • Gateway Broken after Update
  • Gateway entrypoint problem
  • OpenClaw slow after updating to 2026.4.25
  • Gateway not starting after updating to 2026.4.25
  • qmd memory unavailable / active memory timeouts

One WSL2 case:

  • OpenClaw 2026.4.25 aa36ee6
  • WSL2 Linux 6.6.87.2
  • Node initially 22.22.2, later 24.15.0 via nvm
  • systemd user gateway
  • bind lan / port 18789
  • plugin-runtime-deps root became partially installed
  • manual npm install inside plugin-runtime-deps pruned 739 packages
  • moving runtime deps aside + doctor did not fully recover consistently
  • OPENCLAW_SKIP_CHANNELS=1 OPENCLAW_SKIP_PROVIDERS=1 can start core after ~30s, but normal service still wedges around channels/runtime deps
  • downgrade to 2026.4.23 may not help unless runtime-deps cache/service state are cleaned too

Important warning: Users should not manually run npm install inside ~/.openclaw/plugin-runtime-deps; it is OpenClaw-managed and npm can prune packages.

Suspected area: 2026.4.25 bundled plugin runtime dependency staging / mirror rebuild / service restart recovery regression, possibly related to issue #72933.

Fix Action

Fix / Workaround

One WSL2 case:

  • OpenClaw 2026.4.25 aa36ee6
  • WSL2 Linux 6.6.87.2
  • Node initially 22.22.2, later 24.15.0 via nvm
  • systemd user gateway
  • bind lan / port 18789
  • plugin-runtime-deps root became partially installed
  • manual npm install inside plugin-runtime-deps pruned 739 packages
  • moving runtime deps aside + doctor did not fully recover consistently
  • OPENCLAW_SKIP_CHANNELS=1 OPENCLAW_SKIP_PROVIDERS=1 can start core after ~30s, but normal service still wedges around channels/runtime deps
  • downgrade to 2026.4.23 may not help unless runtime-deps cache/service state are cleaned too
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

I am not very experienced with Linux/WSL, but several Discord users appear to be hitting the same issue, so I am collecting the symptoms here. Multiple Discord users are reporting serious Gateway failures after updating to OpenClaw 2026.4.25.

Common symptoms:

  • openclaw status / WS health timeout
  • service reports running, but Gateway is unreachable
  • /healthz sometimes times out or port is not listening
  • Gateway did not become healthy after restart
  • Completion cache update failed: spawnSync node ETIMEDOUT
  • bundled runtime deps missing:
    • Cannot find package 'chokidar'
    • Cannot find module '@hapi/hoek'
    • Cannot find module 'discord-api-types/v10.js'
    • Cannot find module 'typebox/build/index.mjs'
  • npm ENOTEMPTY rename ... node_modules/...
  • browser runtime deps fail to stage: @modelcontextprotocol/sdk, playwright-core Affected reports include:
  • Gateway not responding after update 2026.4.23 -> 2026.4.25
  • Gateway Broken after Update
  • Gateway entrypoint problem
  • OpenClaw slow after updating to 2026.4.25
  • Gateway not starting after updating to 2026.4.25
  • qmd memory unavailable / active memory timeouts

One WSL2 case:

  • OpenClaw 2026.4.25 aa36ee6
  • WSL2 Linux 6.6.87.2
  • Node initially 22.22.2, later 24.15.0 via nvm
  • systemd user gateway
  • bind lan / port 18789
  • plugin-runtime-deps root became partially installed
  • manual npm install inside plugin-runtime-deps pruned 739 packages
  • moving runtime deps aside + doctor did not fully recover consistently
  • OPENCLAW_SKIP_CHANNELS=1 OPENCLAW_SKIP_PROVIDERS=1 can start core after ~30s, but normal service still wedges around channels/runtime deps
  • downgrade to 2026.4.23 may not help unless runtime-deps cache/service state are cleaned too

Important warning: Users should not manually run npm install inside ~/.openclaw/plugin-runtime-deps; it is OpenClaw-managed and npm can prune packages.

Suspected area: 2026.4.25 bundled plugin runtime dependency staging / mirror rebuild / service restart recovery regression, possibly related to issue #72933.

Steps to reproduce

update from 2026.4.23 > 2026.4.25

Expected behavior

works fine after update

Actual behavior

Dead

OpenClaw version

2026.4.25

Operating system

Windows 11 / WSL2 Ubuntu24.04

Install method

npm

Model

nicht relevant

Provider / routing chain

nicht relevant

Additional provider/model setup details

nicht relevant

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

Downgrade to OpenClaw version 2026.4.23 and clean the runtime-deps cache and service state to potentially resolve the Gateway failures.

Guidance

  • The issue seems to be related to the bundled plugin runtime dependency staging in OpenClaw version 2026.4.25, so reverting to the previous version might help.
  • Before downgrading, clean the runtime-deps cache and service state to ensure a fresh start.
  • Avoid manually running npm install inside ~/.openclaw/plugin-runtime-deps as it can cause package pruning issues.
  • If the issue persists, try setting OPENCLAW_SKIP_CHANNELS=1 and OPENCLAW_SKIP_PROVIDERS=1 to start the core service, but note that this might not fully recover the normal service functionality.

Notes

The provided information suggests a regression in the 2026.4.25 update, but without more details on the specific changes or the environment, it's challenging to provide a definitive fix. The suggested downgrade and cache cleaning are based on the symptoms and the suspected area of the issue.

Recommendation

Apply workaround: Downgrade to OpenClaw version 2026.4.23 and clean the runtime-deps cache and service state. This is recommended because the issue seems to be specific to the 2026.4.25 update, and reverting to a previous version that worked might provide a temporary solution until the issue is fully resolved.

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

works fine after update

#api#pipeline error#runtime error#dependency conflict#environment setup

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]: 2026.4.25: Gateway hangs/timeouts after update; plugin-runtime-deps missing packages [1 comments, 2 participants]