gateway not working

[elder pond]

Runtime: stopped (state active)
RPC probe: failed
RPC target: ws://127.0.0.1:18789
gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: ws://127.0.0.1:18789
Source: cli --url
Config: /Users/gursh/.openclaw/openclaw.json

Service is loaded but not running (likely exited immediately).
File logs: /tmp/openclaw/openclaw-2026-02-18.log
Launchd stdout (if installed): /Users/gursh/.openclaw/logs/gateway.log
Launchd stderr (if installed): /Users/gursh/.openclaw/logs/gateway.err.log

[jade raft]

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

[blazing holly]

Runtime: stopped (state active) + gateway closed (1006 abnormal closure) basically means: launchd still thinks the service is “there”, but the gateway process is exiting immediately (so the WS probe drops with 1006).

To get to the root cause, the next step is always the logs + --deep status.

Can you paste the output of these (and redact tokens/keys if they show up)?

openclaw --version
openclaw gateway status --deep
openclaw doctor

And the last ~150 lines of the crash logs:

tail -n 150 /tmp/openclaw/openclaw-2026-02-18.log

tail -n 150 /Users/gursh/.openclaw/logs/gateway.err.log
# (and gateway.log too if err is empty)

While we wait, the most common “exits immediately” causes on macOS are:

• config drift / wrong mode:

openclaw config get gateway.mode
openclaw config get gateway.bind
openclaw config get gateway.auth.token

• port already taken:

lsof -nP -iTCP:18789 -sTCP:LISTEN