Adapted community discussion: Translated, paraphrased, and condensed from an anonymized public OpenClaw Discord support conversation from August 2026. Technical guidance was reviewed for OpenClaw 2026.9.3.
We migrated and restored the full OpenClaw file ecosystem. The files look intact, but Discord, Telegram, and WhatsApp do not respond, and our main agent appears offline.
When every channel fails together, check the Gateway before reauthenticating any one channel. On the restored host, run:
openclaw --version
openclaw status --all
openclaw gateway status --deep
openclaw channels status --probe
Redact credentials. A stopped Gateway, a different config path, missing plugins, and missing secrets produce different recovery paths.
The probe shows nothing listening on the local Gateway port. The user-level systemd service is disabled or not installed. The channel entries exist, but live probes were skipped because the Gateway is down.
Install and enable the user service on the restored host, then verify it before changing channel credentials:
openclaw gateway install
systemctl --user enable --now openclaw-gateway.service
openclaw gateway status --deep
openclaw channels status --probe
If the service stops again, inspect its user journal. Avoid --force and channel reauthentication until the Gateway itself remains healthy.
The Gateway is now installed and persistent. WhatsApp is healthy, while Telegram and Discord start but remain disconnected.
That separates service recovery from channel recovery. Restart once, run openclaw channels status --probe, and watch openclaw logs --follow while sending a test message. For Discord, confirm the bot remains in the server, the required message-content intent is enabled, and the channel grants view, send, and history permissions. A token probe marked works proves credential access, not an active transport connection.