OpenClaw troubleshooting works best when you reduce the problem.
Start with the AI key. Then check web chat. Then check Telegram. Then check private access or deeper workflow behavior.
That order matters because each step removes a layer of noise.
The Short Answer
If the bot is not working, first ask: does it answer in web chat after the AI key is accepted?
If yes, debug the channel or workflow. If no, fix the hosted bot or AI-key setup first.
First Triage
Use this table before changing anything else.
| Symptom | Check first | Next guide |
|---|---|---|
| Bot exists but does not answer | Public web chat and AI-key validation | Setup problems and fixes |
| AI key is not accepted | Provider, copied key, account access | BYOK security and key ownership |
| Telegram does not reply | Web chat first, then BotFather token | Telegram setup guide |
| Web chat works but output feels wrong | Prompt scope and model choice | Setup checklist |
| Private access is confusing | Whether the bot really needs a private path | Private Tailscale web chat |
| Pricing is unclear | Hosting charges vs AI provider charges | Pricing and cancellation explained |
Rule 1: Web Chat Before Telegram
If web chat does not work, Telegram is not the right place to debug.
Public web chat proves:
- the bot exists,
- the hosted environment is reachable,
- the AI key can produce a reply,
- the issue is not only an external messaging channel.
Once web chat works, Telegram troubleshooting gets much easier.
Rule 2: Fix The AI Key Before Tuning The Bot
If the AI key is not accepted, stop there.
Most AI-key failures are ordinary:
- wrong provider selected,
- copied key includes extra spaces,
- provider account cannot use the selected AI model,
- key was changed or turned off,
- account billing or quota is blocked on the provider side.
OpenClaw VPS can host the bot, but AI provider charges still belong to your AI provider account. That split is the point of BYOK.
Rule 3: One Prompt Before A Whole Workflow
A complex workflow can fail for many reasons. A simple prompt usually fails for one or two.
Start with:
- "Reply with one sentence if you can read this."
- A short practical prompt from your work.
- A small file or image if the workflow needs attachments.
If those work, the bot is alive. If they fail, you have a smaller debugging problem.
Rule 4: Do Not Assume Unsupported Channels Are Live
OpenClaw VPS hosted channels that are live today:
- public web chat,
- Telegram,
- private web chat through Tailscale on paid bots.
Slack, Discord, WhatsApp, and iMessage are not sold as live hosted OpenClaw VPS channels today.
Check channel status before planning a workflow around a channel.
When To Use Support
Use support when:
- the AI key is accepted but web chat still does not answer,
- Telegram does not reply after web chat works,
- the bot appears stuck while it is being created,
- private access is unclear,
- billing looks wrong,
- you need help deciding whether the issue is OpenClaw, the model provider, or the hosted environment.
That support path is part of the hosted product. You should not have to become the server admin to get one useful bot running.
Best Next Pages
- OpenClaw VPS setup checklist
- Common OpenClaw VPS setup problems and fixes
- Public web chat for OpenClaw VPS
- How BYOK works for OpenClaw VPS
- OpenClaw VPS channel status
What To Remember
Debug the smallest thing first. Web chat tells you whether the bot itself works before you spend time on Telegram, private access, or a bigger workflow.