Selig
4c966a3ad2
6 custom skills (assign-task, dispatch-webhook, daily-briefing, task-capture, qmd-brain, tts-voice) with technical documentation. Compatible with Claude Code, OpenClaw, Codex CLI, and OpenCode.
41 lines
1.1 KiB
Markdown
41 lines
1.1 KiB
Markdown
# Channel Troubleshooting
|
|
|
|
## Overview
|
|
|
|
This guide provides diagnostic guidance for resolving channel configuration issues in OpenClaw.
|
|
|
|
## Diagnostic Commands
|
|
|
|
Start with these commands:
|
|
|
|
```bash
|
|
openclaw doctor
|
|
openclaw channels status --probe
|
|
```
|
|
|
|
The `channels status --probe` command prints warnings when it can detect common channel misconfigurations, and includes small live checks (credentials, some permissions/membership).
|
|
|
|
## Supported Channels
|
|
|
|
Three primary channels have dedicated troubleshooting sections:
|
|
|
|
- Discord
|
|
- Telegram
|
|
- WhatsApp
|
|
|
|
## Telegram-Specific Solutions
|
|
|
|
### Network Request Failures
|
|
|
|
IPv6 DNS problems may cause `HttpError` messages for 'sendMessage' or 'sendChatAction'.
|
|
|
|
**Solution:** Force IPv4 or enable IPv6 support.
|
|
|
|
### Command Configuration Issues
|
|
|
|
When `setMyCommands failed` appears in logs, verify outbound HTTPS and DNS reachability to `api.telegram.org`. This frequently fails on restricted VPS environments or proxy setups.
|
|
|
|
## Additional Resources
|
|
|
|
See the complete documentation index at https://docs.openclaw.ai/llms.txt for discovering additional resources.
|