Security Warning: OpenClaw grants AI full system access

Troubleshooting

Common errors and how to fix them.

moltbot: command not found
Root Cause:

CLI binary renamed, old path remains

Solution:

Run `npm uninstall -g moltbot && npm install -g openclaw` then restart terminal

clawdbot: command not found
Root Cause:

CLI binary renamed, old path remains

Solution:

Run `npm uninstall -g clawdbot && npm install -g openclaw` then restart terminal

WhatsApp status=515
Root Cause:

Baileys library version mismatch or session file corrupted

Solution:

Click 'Update' in Config to update dependencies, or delete session file and re-scan QR

Connection refused (127.0.0.1:18789)
Root Cause:

Gateway not running, or Docker port mapping not configured to host

Solution:

Check `docker ps` for container status; verify `ports` section in docker-compose.yml

No API key found for provider
Root Cause:

Agent config file missing auth info

Solution:

Run `openclaw models auth setup-token` to re-enter API key

Invalid --bind
Root Cause:

Bind address parameter error, common in PaaS environments

Solution:

Set environment variable `CLAWDBOT_GATEWAY_BIND=auto`

Bot stops responding after terminal close
Root Cause:

Daemon not installed, process dies with terminal

Solution:

Re-run `openclaw onboard --install-daemon` to install systemd/launchd service

💡 Pro Tip: Run Doctor

OpenClaw includes a built-in diagnostic tool: 

openclaw doctor

This checks for common misconfigurations and security issues.