If remote, is the tunnel/Tailscale link up?

Then tail logs:
openclaw logs --follow
Docs: Dashboard, Remote access, Troubleshooting.

Telegram setMyCommands fails with network errors What should I check
Start with logs and channel status:
openclaw channels status
openclaw channels logs --channel telegram
If you are on a VPS or behind a proxy, confirm outbound HTTPS is allowed and DNS works. If the Gateway is remote, make sure you are looking at logs on the Gateway host.
Docs: Telegram, Channel troubleshooting.

TUI shows no output What should I check
First confirm the Gateway is reachable and the agent can run:
openclaw status
openclaw models status
openclaw logs --follow
In the TUI, use /status to see the current state. If you expect replies in a chat channel, make sure delivery is enabled (/deliver on).
Docs: TUI, Slash commands.

How do I completely stop then start the Gateway
If you installed the service:
openclaw gateway stop
openclaw gateway start
This stops/starts the supervised service (launchd on macOS, systemd on Linux). Use this when the Gateway runs in the background as a daemon.
If you’re running in the foreground, stop with Ctrl‑C, then:
openclaw gateway run
Docs: Gateway service runbook.

ELI5 openclaw gateway restart vs openclaw gateway
openclaw gateway restart: restarts the background service (launchd/systemd).
openclaw gateway: runs the gateway in the foreground for this terminal session.
If you installed the service, use the gateway commands. Use openclaw gateway when you want a one-off, foreground run.

What’s the fastest way to get more details when something fails
Start the Gateway with --verbose to get more console detail. Then inspect the log file for channel auth, model routing, and RPC errors.