-
-
Notifications
You must be signed in to change notification settings - Fork 183
"Stop Gateway" button issue #102
Description
I have 2 issues:
- how can I open the storage access? it is showing warning in setting.
- I click the button "Stop Gateway" (on top), but it seems it doesn't stop the gateway and after "openclaw gateway status", it is showing below info:
Question:
- I only can stop the gateway by inputting "openclaw gateway stop" instead of that button?
- if I want to restart the gateway, only can input "openclaw gateway restart" instead of clicking the button twice?
root@localhost:~# openclaw gateway status
🦞 OpenClaw 2026.3.24 (cff6dc9) — I can't fix your code taste, but I can fix your build and your backlog.
│
◇
Service: systemd (disabled)
File logs: /tmp/openclaw/openclaw-2026-04-02.log
Service config looks out of date or non-standard.
Service config issue: Gateway service PATH is not set; the daemon should use a minimal PATH.
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 (env/config)
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: unknown (systemctl --user unavailable: Failed to connect to bus: No medium found)
RPC probe: ok
systemd user services unavailable.
systemd user services are unavailable; install/enable systemd or run the gateway under your supervisor.
On a headless server (SSH/no desktop session): run sudo loginctl enable-linger $(whoami) to persist your systemd user session across logins.
Also ensure XDG_RUNTIME_DIR is set: export XDG_RUNTIME_DIR=/run/user/$(id -u), then retry.
If you're in a container, run the gateway in the foreground instead of openclaw gateway