openclaw - 💡(How to fix) Fix [Bug]: updated to 4.24, Gateway not reachable. Is it running and accessible? [5 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#72665Fetched 2026-04-28 06:33:36
View on GitHub
Comments
5
Participants
3
Timeline
8
Reactions
1
Timeline (top)
commented ×5labeled ×2closed ×1

After update from 4.22 to 4.24, Completion cache update failed: Error: spawnSync /home/burkro/.npm-global/lib/node_modules/node/bin/node ETIMEDOUT. web error: disconnected (1006): no reason, openclaw logs error: Gateway not reachable. Is it running and accessible?

Error Message

After update from 4.22 to 4.24, Completion cache update failed: Error: spawnSync /home/burkro/.npm-global/lib/node_modules/node/bin/node ETIMEDOUT. web error: disconnected (1006): no reason, openclaw logs error: Gateway not reachable. Is it running and accessible? 1、update error log: Completion cache update failed: Error: spawnSync /home/burkro/.npm-global/lib/node_modules/node/bin/node ETIMEDOUT 2、web error: disconnected (1006): no reason 3、openclaw logs error: Gateway not reachable. Is it running and accessible? Completion cache update failed: Error: spawnSync /home/burkro/.npm-global/lib/node_modules/node/bin/node ETIMEDOUT

Root Cause

After update from 4.22 to 4.24, Completion cache update failed: Error: spawnSync /home/burkro/.npm-global/lib/node_modules/node/bin/node ETIMEDOUT. web error: disconnected (1006): no reason, openclaw logs error: Gateway not reachable. Is it running and accessible?

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After update from 4.22 to 4.24, Completion cache update failed: Error: spawnSync /home/burkro/.npm-global/lib/node_modules/node/bin/node ETIMEDOUT. web error: disconnected (1006): no reason, openclaw logs error: Gateway not reachable. Is it running and accessible?

Steps to reproduce

1、update error log: Completion cache update failed: Error: spawnSync /home/burkro/.npm-global/lib/node_modules/node/bin/node ETIMEDOUT 2、web error: disconnected (1006): no reason 3、openclaw logs error: Gateway not reachable. Is it running and accessible?

Expected behavior

all same config, same workflow

Actual behavior

Completion cache update failed: Error: spawnSync /home/burkro/.npm-global/lib/node_modules/node/bin/node ETIMEDOUT

OpenClaw version

2026.4.24

Operating system

ubuntu 24.04

Install method

No response

Model

local

Provider / routing chain

local

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 issue is likely due to a timeout error when trying to spawn a Node.js process, and a potential workaround is to adjust the timeout settings or check the accessibility of the Node.js executable.

Guidance

  • Check the permissions and accessibility of the Node.js executable at /home/burkro/.npm-global/lib/node_modules/node/bin/node to ensure it can be executed by the current user.
  • Verify that the Node.js process is not being blocked by any firewall or security software, which could be causing the timeout error.
  • Consider increasing the timeout value for the spawnSync function to allow more time for the Node.js process to start.
  • Investigate the OpenClaw logs to determine if there are any other error messages that could indicate the root cause of the issue.

Example

No code example is provided as the issue does not contain sufficient information to create a specific code snippet.

Notes

The issue may be related to changes in the Node.js version or the OpenClaw configuration between versions 4.22 and 4.24. Further investigation is needed to determine the root cause of the issue.

Recommendation

Apply workaround: Adjust the timeout settings or check the accessibility of the Node.js executable, as this is a more immediate and non-invasive solution compared to upgrading or downgrading versions.

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

all same config, same workflow

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]: updated to 4.24, Gateway not reachable. Is it running and accessible? [5 comments, 3 participants]