Fix gateway errors, unauthorized issues, connection problems fast. Step-by-step solutions with copy-paste commands. Get running in 5 minutes.
Click the card that matches your problem to see the fix.
Control UI shows "Unauthorized" or can't connect. Config file is empty.
Copy the token and paste into Control UI → Overview → Gateway Token field.
Terminal says "openclaw: command not found" after installation.
Docker Desktop won't launch or containers fail to start on Apple Silicon.
Error says port 18789 is already occupied by another process.
OpenClaw can't write to directories or access files.
Installation fails with errors about sharp or libvips during npm install.
The most common OpenClaw issue — solved in 3 steps.
First, let's see if you already have a token configured:
If no token exists, generate one:
✅ This creates a secure token and saves it to your config file.
Now retrieve it to copy:
Copy the token from Step 1 or 2, then:
💡 Quickest method: Run openclaw dashboard --no-open and open the printed URL — it includes the token and auto-connects!
Quick answers to frequent troubleshooting questions.
openclaw config get gateway.auth.token in terminal, then paste the token into the Control UI's Gateway Token field. Or use openclaw dashboard --no-open for automatic token injection.
export PATH="$(npm prefix -g)/bin:$PATH" to your ~/.zshrc (macOS) or ~/.bashrc (Linux), then run source ~/.zshrc to apply.
openclaw gateway stop, then clear the config: rm ~/.openclaw/openclaw.json, then restart: openclaw gateway. If issues persist, run openclaw doctor --generate-gateway-token to regenerate auth.
npm install -g openclaw and run openclaw gateway directly. Docker is only needed if you prefer containerized deployment.
More troubleshooting questions from searchers.
Run openclaw gateway status or check if port 18789 is listening with lsof -i :18789. You can also visit http://localhost:18789 in your browser.
Usually means the gateway isn't running or the auth token is wrong. Start the gateway with openclaw gateway and ensure your token is set correctly in the UI.
Yes! Start with a different port: openclaw gateway --port 3000. Or set it permanently in your config file.
Logs are in /tmp/openclaw/ by default. View with tail -f /tmp/openclaw/gateway.log for real-time monitoring.
Run npm update -g openclaw or pnpm update -g openclaw
Yes! Join the official OpenClaw Discord at discord.com/invite/clawd for community support and troubleshooting help.
Get help from the OpenClaw community or start fresh with managed hosting.