Fix It When It Breaks
Diagnose and fix the most common OpenClaw problems.
Reference this page whenever something stops working. Start with logs.
Always start here
openclaw logs --tail 100Most issues are visible in the logs. Look for ERROR lines. The error message usually tells you exactly what's wrong.
Gateway issues
Gateway won't start
openclaw gateway statusCommon causes:
| Error | Fix |
|---|---|
EADDRINUSE: address already in use | Another process is on port 18789. Run lsof -i :18789 to find it. Change the port in config or kill the conflicting process. |
Cannot find module | Node.js version too old. Run node --version — need 22.14+ (Node 24 recommended). Update via nvm install 24. |
Invalid JSON in config | Your openclaw.json has a syntax error. Run `cat ~/.openclaw/openclaw.json |
API key invalid | Your AI provider key is wrong or expired. Check it at your provider's dashboard. |
Gateway keeps crashing
openclaw logs --filter error --tail 200If it's crashing on startup with a channel error, try disabling all channels temporarily and re-enabling them one at a time to find the bad config.
Port conflict
openclaw config set gateway.port 18790
openclaw gatewayChannel issues
Telegram not responding
- Check
openclaw gateway status— istelegram: connected? - Verify the bot token in config is correct (no extra spaces)
- Check if BotFather revoked the token — generate a new one if needed
- Make sure you sent
/startto the bot before messaging
WhatsApp disconnected
WhatsApp sessions expire if unused for too long.
openclaw channels login --channel whatsappRe-scan the QR code. The session will reconnect.
If you see Error: session store corrupted:
rm -rf ~/.openclaw/sessions/whatsapp
openclaw channels login --channel whatsappSlack "not_in_channel" error
Your bot isn't in the channel you're trying to post to. In Slack:
/invite @YourBotNameAlso check the bot's OAuth scopes — it needs chat:write at minimum.
iMessage not responding
iMessage requires macOS accessibility permissions. If they were revoked:
openclaw channels setup imessageRe-grant permissions when prompted.
Automation issues
Automations not firing
openclaw cron list
openclaw cron status [automation-id]Check:
- Is the schedule valid cron syntax? Test at crontab.guru
- Is the Gateway running at the scheduled time? (Laptop sleeping breaks this — see Run It 24/7)
- Is the timezone correct? Add
"timezone": "America/New_York"to the automation config if not specified
Test an automation manually
openclaw cron run [automation-id]This runs it immediately regardless of schedule.
Automation runs but sends nothing
If suppressEmpty is set, the agent may be deciding there's nothing worth sending. Test the prompt manually in WebChat to see what the agent produces:
openclaw dashboardAI response issues
Slow responses
- Check your AI provider's status page for outages
- Try a smaller model:
"model": "claude-haiku-4-5-20251001"for faster responses - Check your internet connection
Agent ignoring SOUL.md instructions
- SOUL.md over 200 lines? The agent may be ignoring sections. Trim it.
- Instructions too vague? "Be concise" is ignored. "Default to 2-3 sentences" works.
- Restart the Gateway after editing SOUL.md: stop and re-run
openclaw gateway
Tool not working
openclaw tools listCheck that the tool is enabled. If web_search isn't in the list, it's not in your config.
Config issues
Finding your config
cat ~/.openclaw/openclaw.jsonValidating your config
openclaw config validateThis checks JSON syntax and required fields.
Resetting to defaults
openclaw config resetThis resets openclaw.json to defaults but doesn't touch SOUL.md, USER.md, or workspace files.
Getting help
If you can't fix it:
- Official docs: docs.openclaw.ai/help/troubleshooting
- Discord: The OpenClaw Discord has a
#helpchannel with the community - GitHub issues: github.com/openclaw/openclaw/issues
When asking for help, include the output of openclaw logs --tail 50 and openclaw gateway status.