#Openclaw not responding at all
1 messages · Page 1 of 1 (latest)
?
First thing, what does this show?
openclaw --version
Since it died on both Telegram and WebSocket mid-chat, this sounds more like the gateway/agent/model path got stuck than a Telegram-only issue.
Please run these and paste the output:
openclaw status --all
openclaw gateway status
openclaw channels status --probe
openclaw logs --follow
If it’s still dead, do one clean restart:
openclaw gateway restart
Then send one test message and watch the logs again.
I’d look for:
- provider/model errors
- pairing/auth errors
mention required/ allowlist drops- gateway probe not ok
Docs:
- FAQ: https://docs.openclaw.ai/help/faq
- Troubleshooting: https://docs.openclaw.ai/gateway/troubleshooting
Paste openclaw --version plus the first suspicious log lines, and I’ll help narrow it down.
Sorry, I mean on the machine where OpenClaw is running, open a terminal and run this first:
openclaw --version
Then run:
openclaw status --all
openclaw gateway status
openclaw channels status --probe
Paste the output here.
If openclaw says command not found, tell me how you installed it, source, npm, Docker, or app, and I’ll adjust.