Health Score
23%
↓ 75pts · critical
Efficiency
0%
Bot offline · not processing
Gateway
Offline
Down 47 min
Auto-Repairs Tried
3
All failed · manual req.
Last Healthy
08:27 AM
Mar 20, 2026
📈 Uptime & Repair History · 30 days
90d view →
⚡ Services
OFFLINE
Gateway port 18789
Offline
Config invalid JSON
Corrupt
Telegram gateway offline
Offline
Webhook port 4000
Not resp.
AI Model OpenRouter
Reachable
Disk 48% · 42GB free
OK
🔧 Mechanic Diagnostic Report
Mar 20, 2026 · 08:30:14 AM
Config file corrupted — gateway cannot start
The configuration file at ~/.openclaw/openclaw.json contains invalid JSON. The gateway process cannot parse this file on startup, which prevents all services from initializing. This was likely caused by a partial write during an interrupted update. Auto-repair attempted to restore from backup 3 times, but the backup config was also found to be invalid.
What to do — follow in order
1. Gateway crash detected
Port 18789 stopped responding · detected at 08:28 AM
2. Auto-repair attempted (×3)
Container restart, config reload, backup restore — all failed
3. Open Terminal on your machine
Run the repair command below to re-generate the config file
4. Follow the wizard to re-enter API keys
The onboard wizard will guide you through re-entering your credentials
5. Mechanic will verify and confirm gateway is back online
Automatic health check will run after repair completes
openclaw onboard --repair --preserve-memory
📋 Incident Timeline
Today
08:28 AM
Gateway went offline
Port 18789 stopped responding
incident start
08:28 AM
Auto-repair #1 — container restart
Failed: config JSON parse error on startup
auto-repair
08:29 AM
Auto-repair #2 — config reload
Failed: backup config also invalid
auto-repair
08:30 AM
Auto-repair #3 — full restore
Failed: no valid backup found
auto-repair
08:30 AM
Escalated to manual repair
Diagnostic report generated
manual required