romtuck/openclaw
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
92697edb7c
openclaw/docs/channels/troubleshooting.md
Jon Shapiro 92697edb7c fix(venice): add compat settings to prevent HTTP 400 errors 
Venice's API doesn't support certain OpenAI-compatible parameters that
Clawdbot sends by default:

- `store`: Venice returns HTTP 400 with no body when this is present
- `developer` role: Not supported by Venice's API

This adds VENICE_COMPAT settings (supportsStore: false,
supportsDeveloperRole: false) to all Venice model definitions, both
from the static catalog and dynamically discovered models.

Fixes issues reported in PR #1666 where users experienced silent
failures (HTTP 400, no body) when using Venice models.

Co-authored-by: jonisjongithub <jonisjongithub@users.noreply.github.com>
Co-authored-by: Clawdbot <bot@clawd.bot>
2026-01-26 17:56:01 -08:00

1.2 KiB
Raw Blame History

summary read_when
Channel-specific troubleshooting shortcuts (Discord/Telegram/WhatsApp)
A channel connects but messages don’t flow
Investigating channel misconfiguration (intents, permissions, privacy mode)

Channel troubleshooting

Start with:

clawdbot doctor
clawdbot channels status --probe

channels status --probe prints warnings when it can detect common channel misconfigurations, and includes small live checks (credentials, some permissions/membership).

Channels

Telegram quick fixes

  • Logs show HttpError: Network request for 'sendMessage' failed or sendChatAction → check IPv6 DNS. If api.telegram.org resolves to IPv6 first and the host lacks IPv6 egress, force IPv4 or enable IPv6. See /channels/telegram#troubleshooting.
  • Logs show setMyCommands failed → check outbound HTTPS and DNS reachability to api.telegram.org (common on locked-down VPS or proxies).