Tutorial
Running into issues with OpenClaw? This guide covers the most common problems, their causes, and step-by-step solutions.
Installation Issues
Error: "command not found: openclaw"
Symptom: Running openclaw gives "command not found"
Solutions:
- Check installation:
npm list -g | grep openclaw - Verify npm bin directory is in PATH:
echo $PATH - Try full path:
$(npm config get prefix)/bin/openclaw - Reinstall with sudo if needed:
sudo npm install -g openclaw@latest
Error: EACCES permission denied
Symptom: Cannot install globally due to permissions
Solutions:
- Fix npm permissions:
mkdir -p ~/.npm-global && npm config set prefix '~/.npm-global' - Add to PATH in
~/.bashrcor~/.zshrc:export PATH="~/.npm-global/bin:$PATH" - Or use sudo:
sudo npm install -g openclaw@latest
API Key Issues
Error: "Invalid API key"
Symptom: API calls fail with authentication error
Solutions:
- Verify API key in config:
openclaw config get anthropicApiKey - Set API key:
openclaw config set anthropicApiKey YOUR_KEY - Or use environment variable:
export ANTHROPIC_API_KEY=YOUR_KEY - Check API key hasn't expired or been revoked
Daemon Issues
Daemon won't start
Symptom: openclaw daemon start fails silently
Solutions:
- Check for existing daemon:
openclaw daemon status - Check logs:
openclaw daemon logs --follow - Check port conflicts:
lsof -i :3000(or your configured port) - Try restart:
openclaw daemon restart
Daemon stops unexpectedly
Symptom: Daemon crashes after some time
Solutions:
- Check memory usage:
toporhtop - Review logs for crash details
- Reduce conversation context size if memory is low
- Consider using systemd for auto-restart
Integration Issues
Discord bot not responding
Symptom: Bot is online but doesn't respond to messages
Solutions:
- Verify MESSAGE CONTENT INTENT is enabled in Discord Developer Portal
- Check bot has "Read Messages" and "Send Messages" permissions
- Verify daemon is running:
openclaw daemon status - Check logs:
openclaw daemon logs
Telegram webhook fails
Symptom: Cannot set up Telegram webhook
Solutions:
- Use polling mode for local development: set
mode: "polling"in config - For webhook, verify URL is publicly accessible
- Use ngrok for testing:
ngrok http 3000 - Check Telegram bot token is correct
Performance Issues
Slow response times
Symptom: AI takes long time to respond
Solutions:
- Check internet connection
- Try faster model (claude-3-5-haiku instead of sonnet)
- Reduce max_tokens setting
- Use local models via Ollama for privacy
Getting More Help
If you're still stuck:
- Join the GitHub Discussions
- Check official documentation
- Search existing issues on GitHub
- Run with
--verboseflag and share logs when asking for help
Tip: Always include your OpenClaw version when reporting bugs:
openclaw --version
References
- OpenClaw Official Documentation - https://docs.openclaw.ai/ - Accessed February 2026
- OpenClaw GitHub Issues - Known Issues & Reports - Accessed February 2026
- OpenClaw Troubleshooting Guide - Common Fixes - Accessed February 2026
- Kaspersky Security Report - OpenClaw Vulnerabilities Analysis - February 2026
Reference Trail
External sources surfaced from the underlying article content
- GitHub Discussionsgithub.com
- official documentationdocs.openclaw.ai
- GitHubgithub.com
- https://docs.openclaw.ai/docs.openclaw.ai
- Common Fixesdocs.openclaw.ai