OpenClaw Chatbot Frozen? Diagnostic Steps That Work

What Healthy Output Looks Like

• openclaw gateway status

  should return

  Runtime: running

  and

  Connectivity probe: ok

  .

• openclaw channels status --probe

  should show that the transport is connected, and for supported platforms, a works or

  audit ok

  status line.

• openclaw status

  should not reveal any obvious authentication errors or config errors.

If the Freeze Started After an Update

Post-update freezes are often caused by corrupted plugin dependency trees. The official fix path, straight from the OpenClaw docs, is to run

openclaw status --all

openclaw doctor --fix

openclaw gateway restart

openclaw status --all

If you spot

plugin load failed: dependency tree corrupted

openclaw doctor --fix

Telegram-Specific Freeze Symptoms

Telegram bots have their own set of failure signatures that look like a generic freeze. Here's how to triage each one:

• Bot is online but /start doesn't yield usable replies: The pairing relationship is likely broken. Run

  openclaw pairing list telegram

  to check the pairing status before doing anything else.
• Bot responds in private chat but is silent in a group: Check whether the group requires mentions to trigger the bot and verify the bot's privacy mode setting inside the group. Both can cause complete silence even with a healthy connection.
• Logs show network errors when reaching Telegram's API: Troubleshoot DNS resolution, IPv6 routing, or proxy configuration. The connection to Telegram's servers is being blocked somewhere in your network stack.
• Startup log shows

  getMe returned 401

  : The bot token is invalid. Update it—whether it's stored in botToken, tokenFile, or the TELEGRAM_BOT_TOKEN environment variable—with a fresh token from BotFather.
• Polling stalls or reconnects far too slowly: Watch

  openclaw logs --follow

  for clues. If the problem persists across restarts, the root cause is likely still a proxy, DNS, or IPv6 routing issue, not a bug in OpenClaw itself.

When the Gateway Itself Is the Problem

• If your terminal is running an older OpenClaw binary by mistake—for example, because your PATH still points to a stale installation—update your PATH so openclaw resolves to the newer install, then rerun whatever action was failing.
• If the gateway service was installed from a mismatched version or an old wrapper script is interfering, the documented fix is to reinstall the gateway service from the correct version and remove any stale system packages or old wrappers that still point to an outdated openclaw binary.

Quick Symptom-to-Fix Map

• Gateway not running or connectivity probe fails: Diagnose the gateway, service, and PATH issues.
• Gateway shows healthy but chatbot won't reply: The problem is downstream in the channel flow. Check pairing, mention gating, privacy mode, token validity, and network connectivity to Telegram's API.
• Freeze appeared immediately after an update: Start with

  openclaw doctor --fix

  and a gateway restart.
• Logs are looping fatal errors: A corrupted config or plugin is actively breaking, not just lagging temporarily. Run the full diagnostic ladder.

Bottom Line

Stop guessing. The fix path for OpenClaw always starts with the same five baseline commands, then branches to either the Telegram or gateway track depending on what those commands reveal. If you run the sequence above and paste 20–30 lines of output from

openclaw gateway status

openclaw channels status --probe

openclaw logs --follow