#Gateway unresponsive
1 messages · Page 1 of 1 (latest)
rm: ... No such file or directory just means ~/.openclaw/gateway.pid doesn’t exist on your machine (so there’s no stale PID file to delete). OpenClaw doesn’t rely on that file in many setups anymore, so deleting it usually won’t fix “gateway unresponsive”.
The fastest way to debug is to use the built-in status/log commands. On the machine running the Gateway, please run and paste the output of:
openclaw --version
openclaw gateway status
openclaw status --all
openclaw logs --follow
If you just want to try the “safe restart” first:
openclaw gateway restart
And if it still won’t come back:
openclaw doctor
openclaw channels status --probe
Docs for this exact ladder:
- https://docs.openclaw.ai/help/faq#first-60-seconds-if-somethings-broken
- https://docs.openclaw.ai/gateway/troubleshooting
Also tell me what “stopped working” means in your case (no replies in Discord? dashboard can’t connect? CLI says RPC probe failed?), because the next step depends on that.
When I run openclaw --version it prompts error: unknown option -version
That error message (unknown option -version) is what you get when the CLI receives a single-dash flag (-version), not the double-dash one.
Can you try these and paste the output?
openclaw --version
openclaw -V
openclaw status
If all of those fail / look weird, it usually means you’re not running the OpenClaw binary you think you are. Then please also paste:
which openclaw
openclaw --help | head -40