OpenClaw Not Responding: How to Fix

Quick Diagnosis

When OpenClaw stops responding, check these in order:

1. Is the process running? pm2 status
2. Are there errors? pm2 logs openclaw
3. Is the API working? Check Anthropic status
4. Is the platform connected? Check Discord/Telegram status

Common Causes & Solutions

1. Process Crashed

Symptoms: Bot shows offline, no responses

Check:

pm2 status

Fix:

pm2 restart openclaw

Prevent future crashes:

pm2 start index.js --name openclaw --max-memory-restart 1G

2. API Rate Limits

Symptoms: Bot responds sometimes, errors in logs mentioning "rate limit"

Check logs:

pm2 logs openclaw | grep -i "rate"

Fix:

• Reduce request frequency
• Implement request queuing
• Upgrade API tier

Add to config:

RATE_LIMIT_REQUESTS=10
RATE_LIMIT_WINDOW=60000

3. Invalid API Key

Symptoms: Bot online but never responds, authentication errors in logs

Check:

pm2 logs openclaw | grep -i "auth\|key\|401"

Fix:

1. Verify API key at console.anthropic.com
2. Update .env file
3. Restart bot: pm2 restart openclaw

4. Discord Token Expired

Symptoms: Bot shows offline in Discord

Check:

pm2 logs openclaw | grep -i "discord\|token\|gateway"

Fix:

1. Regenerate token in Discord Developer Portal
2. Update .env with new token
3. Restart: pm2 restart openclaw

5. Memory Exhaustion

Symptoms: Bot becomes slow, then stops responding

Check:

pm2 monit
free -h

Fix:

pm2 restart openclaw

Prevent:

# Increase Node.js memory limit
pm2 delete openclaw
pm2 start index.js --name openclaw --node-args="--max-old-space-size=2048"
pm2 save

6. Network Issues

Symptoms: Intermittent responses, timeout errors

Check:

ping api.anthropic.com
curl -I https://discord.com/api/v10/gateway

Fix:

• Check VPS provider status page
• Verify firewall rules: sudo ufw status
• Test DNS: nslookup api.anthropic.com

7. Outdated Dependencies

Symptoms: Strange errors, deprecated warnings

Fix:

cd /opt/openclaw
git pull
npm install
pm2 restart openclaw

Diagnostic Commands

Run these to gather information:

# Full system check
echo "=== PM2 Status ===" && pm2 status
echo "=== Recent Logs ===" && pm2 logs openclaw --lines 50
echo "=== Memory ===" && free -h
echo "=== Disk ===" && df -h
echo "=== Network ===" && ping -c 3 api.anthropic.com

Log Analysis

Common error patterns and meanings:

| Error Message | Cause | Solution | |---------------|-------|----------| | ECONNREFUSED | Can't reach API | Check network/firewall | | 401 Unauthorized | Invalid API key | Update credentials | | 429 Too Many Requests | Rate limited | Reduce frequency | | ENOMEM | Out of memory | Increase RAM or restart | | ETIMEDOUT | Network timeout | Check connectivity |

Preventive Measures

1. Set Up Monitoring

pm2 install pm2-logrotate
pm2 set pm2-logrotate:max_size 10M
pm2 set pm2-logrotate:retain 7

2. Enable Auto-Restart

pm2 startup
pm2 save

3. Configure Health Checks

Add to your ecosystem file:

module.exports = {
  apps: [{
    name: 'openclaw',
    script: 'index.js',
    max_memory_restart: '1G',
    restart_delay: 5000,
    max_restarts: 10
  }]
}

Still Having Issues?

If you've tried everything and your bot still isn't working:

1. Check Anthropic Status - API outages happen
2. Review recent changes - Did you update anything?
3. Reset to known state - git checkout . && npm install

Get Professional Help

Tired of troubleshooting? Our maintenance plans include:

• 24/7 monitoring
• Automatic restarts
• Priority support
• Regular updates

Contact us for immediate assistance.

Related Articles

• Bot Keeps Crashing
• High Memory Usage
• PM2 Process Errors
• OpenClaw Offline Fixes