After installing OpenClaw, don't just look at whether the command is successfully returned, but make sure that the Gateway, Dashboard, model, and channel are all working. The shortest verification link is: openclaw gateway status check the running status, openclaw dashboard open the console, and then send a test message in the Control UI.
3 minutes to check the sequence
- Execute
node --version, confirming Node 24 or at least Node 22.14+. openclaw gateway statusexecution, you should normally see the Gateway listening, and the default local port is usually18789.openclaw dashboard, the browser opens the Control UI.- Send "Hello, reply with a message" on the console to confirm that the model key is available.
- Finally, run
openclaw doctorand let it check for configuration, services, and common permission issues.
What phenomena are not really running
- The installer runs out, but the gateway is not running.
- The Dashboard opens, but there is no model reply to the message.
- Telegram/Slack is connected, but the message is blocked by pairing or allowlist.
- This machine can be used, but the remote access fails, but the problem is misjudged as a model problem.
If you just want to check the base environment, don't rush to get skills and browser tools out of the way. After the basic message link is stable, open the channel, browser, exec and lobster one by one, so that if there is a problem, you can also locate which layer is broken.
Official open source address: https://github.com/openclaw/openclaw.
