Installation Problems
"command not found: openclaw" after npm install
Cause: npm global bin directory not in PATH
Solutions:
- Restart your terminal
- Add npm to PATH:
export PATH="$PATH:$(npm bin -g)" - Use npx:
npx openclaw init - Check npm prefix:
npm config get prefix
"EACCES: permission denied" during installation
Cause: Permission issues with npm global directory
Solutions:
- Fix npm permissions:
mkdir ~/.npm-global && npm config set prefix '~/.npm-global' - Use nvm (Node Version Manager)
- Or run with sudo (not recommended)
Node.js version not supported
Cause: Old Node.js version
Solutions:
- Check version:
node --version - Update Node.js:
npm install -g n && n latest - Or use nvm to manage versions
- Minimum required: Node.js 18+
Docker container won't start
Causes & Solutions:
- Port conflict: Check port isn't in use
- Docker not running: Start Docker daemon
- Missing volumes: Create required directories
- Pull image manually:
docker pull openclaw/openclaw
Configuration Errors
"YAML parse error" or "Invalid YAML"
Common causes:
- Inconsistent indentation (use spaces, not tabs)
- Missing colons after keys
- Unquoted special characters
- Duplicate keys
Fix:
- Validate YAML:
npm install -g yaml-lint && yaml-lint gateway.yaml - Use an online YAML validator
- Check for hidden characters
"Invalid API key" or "Authentication failed"
Check these:
- API key is correct and not expired
- No extra spaces in config
- Key format matches provider (sk-..., anthropic-..., etc.)
- API key has sufficient credits
- Environment variable is set correctly
Test: echo $YOUR_API_KEY_VAR
"Model not found" or "Model not supported"
Solutions:
- Check model name format (provider/model-id)
- Verify model is available in your region
- Update to latest OpenClaw version
- Check provider's model list
Examples of correct format:
model: "openai/gpt-4o"
model: "anthropic/claude-3-5-sonnet-20241022"
model: "google/gemini-pro"
"Channel not supported" or "Invalid channel"
Check:
- Channel name is correct (lowercase)
- Channel is enabled in OpenClaw
- Credentials are properly formatted
Valid channels: discord, whatsapp, telegram, slack, signal, sms, msteams, matrix, googlechat, webchat
Runtime Problems
OpenClaw starts but immediately crashes
Debug steps:
- Run with verbose:
openclaw start --verbose - Check logs for error messages
- Verify config loads:
openclaw config validate - Try minimal config (just one channel)
"Port already in use"
Find and kill the process:
# Find process
lsof -i :3000
# Kill it
kill -9 [PID]
# Or use different port
openclaw start --port 3001
"Out of memory" or high RAM usage
Solutions:
- Reduce context window in config
- Clear memory database
- Restart the gateway
- Add swap space
- Use smaller models
- Limit concurrent requests
"Context length exceeded" error
What's happening: Conversation too long for model's context window
Solutions:
- Reduce max_tokens setting
- Clear session memory
- Shorter system prompt
- Use model with larger context
- Enable aggressive forgetting in memory config
"Rate limit exceeded" (Error 429)
Immediate fixes:
- Wait 60 seconds and retry
- Reduce message frequency
- Add delay between requests
Long-term solutions:
- Upgrade your API plan
- Use a provider with higher limits
- Implement request caching
- Consider local LLM for high-volume
"Connection timeout" or network errors
Troubleshooting:
- Check internet connection
- Verify API endpoint is reachable
- Check firewall/proxy settings
- Try different network
- Check provider status pages
For local LLM: Ensure Ollama is running and accessible
Channel-Specific Issues
Discord: Bot won't join server
Solutions:
- Generate new invite link with correct permissions
- Check bot is not already in server
- Verify you have admin rights to add bots
- Check Discord's bot requirements
Discord: "Missing permissions"
Required permissions:
- Read Messages
- Send Messages
- Embed Links
- Attach Files
- Use Slash Commands
- Manage Threads (for thread support)
Fix: Re-invite bot with all permissions
WhatsApp: Session expired or disconnected
Reconnect:
openclaw connect whatsapp --reset
Then scan QR code again.
Prevention: Don't log out from phone while session active
WhatsApp: Messages not sending
Check:
- Phone is connected to internet
- Session is still active
- Not in "last seen" restricted mode
- Recipient hasn't blocked you
Telegram: Bot not responding
Verify:
- Bot token is correct
- Bot is not blocked by user
- Started with /start command
- Bot is in the group (if group chat)
Check updates:
openclaw telegram getUpdates
Slack: App not installed to workspace
Steps:
- Go to Slack App configuration
- Click "Install to Workspace"
- Authorize with admin account
- Copy the OAuth token
- Add to gateway config
Signal: Registration failed
Requirements:
- Valid phone number
- Signal account already registered
- CAPTCHA may be required
Note: Signal has limited bot support. Consider alternative channels.
Memory & Knowledge Issues
Memory not working or not saving
Check config:
memory:
enabled: true
provider: "pinecone"
- Vector database credentials are correct
- Database/index exists
- Network connectivity to DB
"Vector DB connection failed"
Troubleshoot:
- Verify API key/credentials
- Check endpoint URL
- Ensure project/index exists
- Check network access
- Verify firewall rules
Knowledge base not loading
Check:
- File path is correct
- File format is supported
- Files are readable
- Size is reasonable (not too large)
Supported formats: PDF, TXT, MD, DOCX, CSV, JSON
Voice Problems
TTS not producing audio
Check:
- TTS provider API key is valid
- Voice ID exists for provider
- ffmpeg is installed
- Audio output device is configured
Test ffmpeg:
which ffmpeg
ffmpeg -version
STT not transcribing
Verify:
- Microphone permissions granted
- STT provider configured
- Audio format is correct
- API key has credits
Voice latency too high
Solutions:
- Use closer TTS/STT provider
- Reduce audio quality
- Check network latency
- Use local TTS/STT
- Enable push-to-talk mode
Skills & Extensions
Skill won't install
Try:
openclaw install @skill-name --verbose
- Check skill name is correct
- Verify internet connection
- Clear npm cache:
npm cache clean --force - Check skill compatibility with your OpenClaw version
Skill installed but not working
Debug:
- Skill is added to config
- Restart gateway after install
- Check skill has required dependencies
- Verify skill version compatibility
Deployment Issues
Docker container restarts constantly
Check logs:
docker logs [container_id]
Common causes:
- Config error (crashes on startup)
- Missing environment variables
- Out of memory
- Invalid volume paths
Can't access from internet
Check:
- Port is open in firewall
- Router port forwarding configured
- Using correct external IP/DDNS
- HTTPS certificate valid
For reverse proxy: Verify nginx/Caddy config
HTTPS not working
If using Caddy:
- Domain DNS points to server
- Port 80 is accessible
- Domain is valid
If using Certbot:
sudo certbot --nginx -d yourdomain.com
Performance & Speed
Responses are very slow
Causes & solutions:
- Large context: Clear memory or reduce history
- Slow API: Use faster model or provider
- Network: Check connection speed
- Too many skills: Disable unused skills
- Server load: Check CPU/memory
High CPU usage
Reduce by:
- Limiting concurrent requests
- Using lighter models
- Disabling unused features
- Checking for infinite loops in custom skills
Still Stuck?
Need more help?
Resources:
When asking for help, include:
- OpenClaw version
- Your config (without secrets)
- Error messages
- Steps to reproduce