Gateway sopts after update to latest version | Friends of the Crustacean 🦞🤝 | Page 1

covert kestrel Apr 27, 2026, 9:58 AM

#

my gateway stoped when i updared to latest version on WSL and win11

livid shoalBOT Apr 27, 2026, 9:58 AM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

arctic oxideBOT Apr 27, 2026, 9:58 AM

#

First thing: can you paste the exact version + status from the place where the Gateway is supposed to run?

Run these inside WSL if your Gateway runs in WSL:

openclaw --version
which openclaw
openclaw gateway status --deep
openclaw status --all
openclaw doctor

If you also installed OpenClaw on native Windows, run this in PowerShell too:

openclaw --version

#

where openclaw
openclaw gateway status --deep

After updates, the common failure is a split install / stale service: the CLI updated, but the Gateway service still points at an older OpenClaw binary. If gateway status --deep shows a version/path mismatch, try:

openclaw gateway install --force
openclaw gateway restart
openclaw gateway status

Please paste the output here, especially any error from gateway status --deep or doctor.

Docs for this exact path:
https://docs.openclaw.ai/gateway/troubleshooting

#

https://docs.openclaw.ai/install/updating

covert kestrel Apr 27, 2026, 10:04 AM

#

OpenClaw 2026.4.24 (cbcfdf6)
/home/luisadmin/.npm-global/bin/openclaw

🦞 OpenClaw 2026.4.24 (cbcfdf6) — Your .env is showing; don't worry, I'll pretend I didn't see it.

│
◇
Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-04-27.log
Command: /usr/bin/node /home/luisadmin/.npm-global/lib/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789

Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json

Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.

Runtime: running (pid 4073, state active, sub running, last exit 0, reason 0)
Warm-up: launch agents can take a few seconds. Try again shortly.
Connectivity probe: failed
Probe target: ws://127.0.0.1:18789
timeout
Capability: unknown

Port 18789 is already in use.

pid 4073 luisadmin: openclaw-gateway (127.0.0.1:18789)
Gateway already running locally. Stop it (openclaw gateway stop) or use a different port.
Listening: 127.0.0.1:18789
Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting

arctic oxideBOT Apr 27, 2026, 10:04 AM

#

Good, this means the Gateway is not stopped — systemd says it’s running — but the WebSocket health probe is timing out.

Also: the “Port 18789 is already in use” line is probably just the running OpenClaw gateway itself, not a separate port conflict.

Try this in WSL:

openclaw gateway restart
sleep 20
openclaw gateway status
openclaw health --verbose

If it still times out, please paste the last log chunk:

#

tail -n 200 "$(ls -t /tmp/openclaw/openclaw-*.log | head -1)"

And systemd’s view:

journalctl --user -u openclaw-gateway -n 120 --no-pager

Small caution: your status output says .env is showing, so skim the log before posting and remove any API keys/tokens/passwords.

Docs: https://docs.openclaw.ai/gateway/troubleshooting

covert kestrel Apr 27, 2026, 10:07 AM

#

luisadmin@AE7:~$ openclaw gateway restart
sleep 20
openclaw gateway status
openclaw health --verbose
Restarted systemd service: openclaw-gateway.service
Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-04-27.log
Command: /home/luisadmin/.nvm/versions/node/v22.22.2/bin/node /home/luisadmin/.npm-global/lib/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789
Service config looks out of date or non-standard.
Service config issue: Gateway service PATH includes version managers or package managers; recommend a minimal PATH. (/home/luisadmin/.nvm/versions/node/v22.22.2/bin)
Service config issue: Gateway service uses Node from a version manager; it can break after upgrades. (/home/luisadmin/.nvm/versions/node/v22.22.2/bin/node)
Recommendation: run "openclaw doctor" (or "openclaw doctor --repair").
Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json
Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.
Runtime: running (pid 4946, state active, sub running, last exit 0, reason 0)
Warm-up: launch agents can take a few seconds. Try again shortly.
Connectivity probe: failed
Probe target: ws://127.0.0.1:18789
read ECONNRESET
Capability: unknown
Port 18789 is already in use.

pid 4946 luisadmin: openclaw-gateway (127.0.0.1:18789)
Gateway already running locally. Stop it (openclaw gateway stop) or use a different port.
Listening: 127.0.0.1:18789
Troubles: run openclaw status

#

[openclaw] Failed to start CLI: Error: gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: /home/luisadmin/.openclaw/openclaw.json
Bind: loopback
Possible causes:

Gateway not yet ready to accept connections (retry after a moment)
TLS mismatch (connecting with ws:// to a wss:// gateway, or vice versa)
Gateway crashed or was terminated unexpectedly
Run openclaw doctor for diagnostics.
at Object.onClose (file:///home/luisadmin/.npm-global/lib/node_modules/openclaw/dist/call-Gv9tybWD.js:257:10)
at WebSocket.<anonymous> (file:///home/luisadmin/.npm-global/lib/node_modules/openclaw/dist/client-kQ1-TM3I.js:2281:23)
at WebSocket.emit (node:events:519:28)
at WebSocket.emitClose (/home/luisadmin/.npm-global/lib/node_modules/openclaw/node_modules/ws/lib/websocket.js:263:12)
at emitErrorAndClose (/home/luisadmin/.npm-global/lib/node_modules/openclaw/node_modules/ws/lib/websocket.js:1047:13)
at ClientRequest.<anonymous> (/home/luisadmin/.npm-global/lib/node_modules/openclaw/node_modules/ws/lib/websocket.js:886:5)
at ClientRequest.emit (node:events:519:28)
at emitErrorEvent (node:_http_client:108:11)
at Socket.socketErrorListener (node:_http_client:575:5)
at Socket.emit (node:events:519:28)

arctic oxideBOT Apr 27, 2026, 10:08 AM

#

This points to the service wrapper being stale/non-standard:

Gateway service uses Node from nvm; it can break after upgrades.

Run the repair path first:

openclaw doctor --repair
openclaw gateway restart
sleep 20
openclaw gateway status --deep
openclaw health --verbose

If it still shows ECONNRESET, we need the crash/startup error from logs:

#

tail -n 200 /tmp/openclaw/openclaw-2026-04-27.log
journalctl --user -u openclaw-gateway -n 120 --no-pager

Please redact tokens/API keys before posting.

If doctor --repair does not rewrite the service, the stronger service refresh is:

openclaw gateway install --force
openclaw gateway restart

Docs: https://docs.openclaw.ai/gateway/doctor and https://docs.openclaw.ai/gateway/troubleshooting

#

Yep, that 1006 abnormal closure means the CLI can reach the port, but the Gateway is closing the WebSocket immediately. We need the Gateway log, not the CLI stack trace.

Please run:

grep -Ei "error|fatal|exception|unhandled|failed|crash|ECONNRESET" /tmp/openclaw/openclaw-2026-04-27.log | tail -n 120

If that doesn’t show much:

tail -n 250 /tmp/openclaw/openclaw-2026-04-27.log
journalctl --user -u openclaw-gateway -n 150 --no-pager

Also, your service is using Node from nvm, and OpenClaw is warning that this can break after upgrades. If you haven’t already, run this exact repair sequence:

#

openclaw doctor --repair
openclaw gateway install --force
openclaw gateway restart
sleep 20
openclaw gateway status --deep

Please redact any tokens/API keys before posting logs. The log lines around error / failed should tell us what’s actually killing the Gateway.

covert kestrel Apr 27, 2026, 10:10 AM

#

luisadmin@AE7:~$ grep -Ei "error|fatal|exception|unhandled|failed|crash|ECONNRESET" /tmp/openclaw/openclaw-2026-04-27.log | tail -n 120
{"0":"[openclaw] Unhandled promise rejection: CIAO ANNOUNCEMENT CANCELLED","meta":{"runtime":"node","runtimeVersion":"22.22.2","hostname":"unknown","name":"openclaw","date":"2026-04-27T09:18:21.957Z","logLevelId":5,"logLevelName":"ERROR","path":{"fullFilePath":"file:///home/luisadmin/.npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy.js:161:68","fileName":"subsystem-CWI_MDy_.js","fileNameWithLine":"subsystem-CWI_MDy_.js:161","fileColumn":"68","fileLine":"161","filePath":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js","filePathWithLine":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js:161","method":"console.error"}},"time":"2026-04-27T11:18:21.957+02:00"}
{"0":"[openclaw] wrote stability bundle: /home/luisadmin/.openclaw/logs/stability/openclaw-stability-2026-04-27T09-18-21-958Z-402-unhandled_rejection.json","meta":{"runtime":"node","runtimeVersion":"22.22.2","hostname":"unknown","name":"openclaw","date":"2026-04-27T09:18:21.960Z","logLevelId":5,"logLevelName":"ERROR","path":{"fullFilePath":"file:///home/luisadmin/.npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy.js:161:68","fileName":"subsystem-CWI_MDy_.js","fileNameWithLine":"subsystem-CWI_MDy_.js:161","fileColumn":"68","fileLine":"161","filePath":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js","filePathWithLine":".npm-global/lib/node_modules/openclaw/dist/subsystem-CWI_MDy_.js:161","method":"console.error"}},"time":"2026-04-27T11:18:21.961+02:00"}
{"0":"[openclaw] Unhandled promise rejection: CIAO ANNOUNCEMENT CANCELLED","_meta":

#

the chunk is way longer

arctic oxideBOT Apr 27, 2026, 10:12 AM

#

That log is the smoking gun: CIAO ANNOUNCEMENT CANCELLED = Bonjour/mDNS advertiser crash path. WSL is exactly the kind of environment where mDNS can be flaky. The changelog has fixes after 2026.4.24 for Bonjour/ciao crashes and loops. (raw.githubusercontent.com)

Do this:

npm view openclaw version
npm i -g openclaw@latest
openclaw doctor --repair
openclaw gateway install --force
openclaw gateway restart

If it still crashes, disable Bonjour/mDNS discovery; it’s only LAN auto-discovery, not the Gateway itself. Docs list OPENCLAW_DISABLE_BONJOUR=1 for disabling advertising. (docs.openclaw.ai)

Try the config-side disable first:

#

openclaw plugins disable bonjour
openclaw gateway restart
sleep 20
openclaw gateway status

If the Gateway comes up after that, you’ve confirmed it was the Bonjour issue. Then you can stay with Bonjour disabled on WSL.

#

No need to paste the whole huge chunk — the CIAO ANNOUNCEMENT CANCELLED line is already enough to suspect Bonjour/mDNS on WSL.

If you want to share more, send only the focused part:

grep -Ei "CIAO|bonjour|mdns|stability|unhandled|fatal|error|listening|ready" /tmp/openclaw/openclaw-2026-04-27.log | tail -n 200

But I’d try the fix first:

npm i -g openclaw@latest
openclaw plugins disable bonjour
openclaw doctor --repair
openclaw gateway install --force
openclaw gateway restart

#

sleep 20
openclaw gateway status

On WSL, disabling Bonjour is fine — it only disables LAN auto-discovery, not the actual gateway.

covert kestrel Apr 27, 2026, 10:14 AM

#

i usually use openclaw update for udpates not that npm thing is that ok?

arctic oxideBOT Apr 27, 2026, 10:14 AM

#

Yes — openclaw update is the preferred path. My npm i -g suggestion was just the manual recovery path if the updater itself is wedged.

Use this instead:

openclaw update
openclaw plugins disable bonjour
openclaw doctor --repair
openclaw gateway install --force
openclaw gateway restart

Then check:

openclaw gateway status

#

openclaw health --verbose

If openclaw update fails or hangs, then use the npm recovery from the docs:

npm i -g openclaw@latest

For your WSL case, the key workaround is still disabling Bonjour.

covert kestrel Apr 27, 2026, 10:25 AM

#

ha funcionado

arctic oxideBOT Apr 27, 2026, 10:25 AM

#

¡Perfecto! 🎉

Entonces era casi seguro el problema de Bonjour/mDNS en WSL. Puedes dejar bonjour desactivado ahí sin problema; solo pierdes auto-discovery LAN, no el Gateway.

Si esto lo solucionó, porfa marca la respuesta útil como solución: right-click en el mensaje → Apps → ✅ Mark Solution. Así queda indexado para futuros usuarios. 🦐

#Gateway sopts after update to latest version