Guide

OpenClaw Health Check

The health check diagnoses gateway status, provider connectivity, channel health, and config validation. Use it to find and fix issues before they cause problems.

Quick Answer

To run an OpenClaw health check: open ClawSquire, click Run Doctor on the Dashboard (or go to the Health Check page), and view categorized results for Installation, Configuration, and Backup. Alternatively, run openclaw doctor in the terminal.

What the health check covers

  • • Gateway status — Is the gateway running and reachable?
  • • Provider connectivity — Can API keys reach your LLM providers?
  • • Channel health — Are Telegram, WhatsApp, and other channels connected?
  • • Config validation — Is the config schema valid?

⟩Running the Health Check

Recommended: Use ClawSquire

ClawSquire provides a visual health check with categorized results — no terminal needed.

1

Open ClawSquire → click Run Doctor on Dashboard

Open ClawSquire and click Run Doctor on the Dashboard, or go to the Health Check page directly.

ClawSquire Dashboard showing OpenClaw version, Safety Level, Config Backups count, and Run Doctor Quick Action button for one-click health diagnostics
2

See categorized results: Installation, Configuration, Backup

Results show Pass/Warning/Fail for each category: Installation (OpenClaw version), Configuration (config file location), and Backup (backup count). Use Re-run to refresh.

ClawSquire Health Check results showing 3 Total, 3 Pass, 0 Warning, 0 Fail — Installation (OpenClaw 2026.3.7 installed - Pass), Configuration (Config File found at path - Pass), Backup (7 backup(s) found - Pass), with Re-run button and Community Search section

Manual Alternative

Run diagnostics from the terminal.

3

Run openclaw doctor

From the terminal, run:

openclaw doctor

The doctor runs a full diagnostic and prints the results. It also generates a gateway token if one is missing and creates default config files.

4

Understanding the report

Results are categorized by severity:

  • • Critical — Must fix before the system works (e.g., gateway not running, no API key)
  • • Warning — May cause issues (e.g., channel disconnected, deprecated config)
  • • Info — Informational (e.g., optional features not configured)
5

Common fixes

Here are quick fixes for frequent issues:

API key expired — Regenerate the key in your provider dashboard and update it in Config.

Gateway not running — Run openclaw gateway or start it via ClawSquire.

Channel disconnected — Re-pair the channel (e.g., send /pair to your Telegram bot).

⟩Troubleshooting

Health check says gateway not reachable+

Start the gateway with openclaw gateway. If it's already running, check the port (default 18789). Ensure no firewall is blocking localhost.

Provider connectivity fails+

Verify your API key is correct and has credits. Check ~/.openclaw/.env or the Dashboard Config page. Restart the gateway after changing keys.

Config validation errors+

Run openclaw doctor to see detailed errors. If you upgraded OpenClaw, the config schema may have changed. Check the changelog or restore a backup.

Next Steps

Download ClawSquire — FreeGet It Fixed — from $199

Guided setup, health diagnostics, 7 languages.