Why is OpenClaw not responding to my messages?
Clawpedia · For Humans
Diagnose and fix the most common reasons why OpenClaw stops responding, from gateway issues to model errors.
Why Is OpenClaw Not Responding to My Messages?
When OpenClaw stops responding entirely — no errors, no output, just silence — it can be frustrating. This comprehensive troubleshooting guide walks through every possible cause, from the simplest to the most obscure.
Quick Diagnostic
Run the built-in health check first:
openclaw doctor
# Output:
# ✅ OpenClaw process running (PID 12345)
# ✅ Configuration valid
# ❌ Model API unreachable (timeout after 10s)
# ✅ Memory database accessible
# ✅ Skills loaded (12 active)
# ⚠️ 2 warnings in recent logs
This immediately narrows down the problem area.
Cause 1: OpenClaw Process Not Running
The agent process may have crashed or not started:
# Check if OpenClaw is running
openclaw status
# Output (if not running):
# Status: ❌ Not running
# Last active: 2024-06-18 14:23:00 UTC
# Last exit code: 1 (error)
# Crash log: ~/.openclaw/logs/crash-20240618.log
# Start OpenClaw
openclaw start
# Start with verbose output for debugging
openclaw start --foreground --log-level debug
Cause 2: Model API Unreachable
The most common cause — the AI model provider is down or unreachable:
# Test model connectivity
openclaw models test
# Output:
# Testing gpt-4o... ❌ timeout (10s)
# Testing llama-3-8b (local)... ✅ 230ms
# Testing claude-3-sonnet... ✅ 890ms
# Check provider status pages:
# OpenAI: status.openai.com
# Anthropic: status.anthropic.com
# Google: status.cloud.google.com
Solutions:
# config.yaml — configure fallback models
models:
primary:
provider: openai
model: gpt-4o
timeout_seconds: 30
fallback:
provider: local
model: llama-3-8b
enabled: true
trigger_on:
- timeout
- api_error
- rate_limit
Cause 3: Network Issues
# Full network diagnostic
openclaw network test
# Output:
# DNS resolution: ✅ OK
# Internet access: ✅ OK (ping 23ms)
# OpenAI API: ❌ Blocked (HTTP 403)
# Anthropic API: ✅ OK
# Proxy configured: No
# If behind a corporate proxy
openclaw config set network.proxy.http "http://proxy.company.com:8080"
openclaw config set network.proxy.https "http://proxy.company.com:8080"
openclaw config set network.proxy.no_proxy "localhost,127.0.0.1"
Cause 4: Stuck in a Processing Loop
OpenClaw may be processing a complex task and appear unresponsive:
# Check current task status
openclaw tasks current
# Output:
# Task: "Analyze 500 log files"
# Status: In progress (45%% complete)
# Started: 12 minutes ago
# ETA: ~15 minutes remaining
# If stuck, cancel the current task
openclaw tasks cancel --current
# Set task timeouts to prevent future hangs
openclaw config set tasks.max_execution_time 300 # 5 minutes
openclaw config set tasks.warn_after 120 # Warn after 2 min
Cause 5: Corrupted Configuration
# Validate configuration file
openclaw config validate
# Output:
# Line 45: Invalid YAML — unexpected character
# Line 78: Unknown key "modle" (did you mean "model"?)
# Line 92: Value "abc" is not valid for timeout_seconds (expected integer)
# Fix by editing
openclaw config edit
# Or reset to defaults
openclaw config reset --backup-existing
Cause 6: Disk Space Full
If the disk is full, OpenClaw cannot write logs or update memory:
# Check disk usage
openclaw storage info
# Output:
# OpenClaw data: 2.1 GB
# Available disk: 0 bytes (❌ FULL)
# Clean up
openclaw cache clear --all
openclaw logs clean --older-than 7d
Cause 7: Input Channel Misconfigured
OpenClaw may be listening on the wrong input channel:
# Check active input channels
openclaw channels list
# Output:
# CHANNEL STATUS
# terminal ✅ active (listening)
# discord ❌ disconnected
# slack ⏸️ paused
# web-ui ✅ active (port 8080)
# Reconnect a channel
openclaw channels reconnect discord
# Resume a paused channel
openclaw channels resume slack
Cause 8: Resource Exhaustion
# Check system resource usage
openclaw system resources
# Output:
# CPU usage: 95%% (⚠️ high)
# Memory (RAM): 3.8 GB / 4.0 GB (⚠️ near limit)
# Open files: 1,023 / 1,024 (❌ at limit)
# Threads: 48 / 50 (⚠️ near limit)
# Reduce resource usage
openclaw config set performance.max_concurrent_tasks 2
openclaw config set performance.max_memory_mb 2048
Complete Troubleshooting Checklist
| # | Check | Command | Fix |
|---|
| 1 | Process running? | openclaw status | openclaw start |
|---|
| 2 | Config valid? | openclaw config validate | openclaw config edit |
|---|
| 3 | Model reachable? | openclaw models test | Enable fallback model |
|---|
| 4 | Network OK? | openclaw network test | Fix proxy/firewall |
|---|
| 5 | Disk space? | openclaw storage info | Clear cache/logs |
|---|
| 6 | Task stuck? | openclaw tasks current | openclaw tasks cancel |
|---|
| 7 | Channels connected? | openclaw channels list | Reconnect/resume |
|---|
| 8 | Resources available? | openclaw system resources | Reduce concurrency |
|---|
If the issue persists after all these steps, submit the diagnostic report to the community Discord or GitHub Issues for help.
Related Articles
- Why does OpenClaw say "Model not allowed" or "Unknown model"? — Fix model-related errors by verifying your model configuration, API keys, and provider compatibility.
- Troubleshooting Common OpenClaw Errors and Solutions — Quick fixes for the most common OpenClaw errors, crashes, and configuration problems.
- Memory Limitations and Troubleshooting — Understand memory capacity limits and troubleshoot common memory-related issues in OpenClaw.
- OpenClaw installation error: "git not found" – how to solve? — Fix the common "git not found" error during OpenClaw installation by installing and configuring Git correctly.
- Resolving Conflicts Between OpenClaw Skills — Fix skill conflicts and priority issues when multiple OpenClaw skills compete for the same triggers.