#tons of telegram errors

1 messages · Page 1 of 1 (latest)

thick river
#

theres a ton of telegram errors like "network request for 'deleteWebhook' failed"e

final pelicanBOT
#

That specific one (telegram deleteWebhook failed: Network request for 'deleteWebhook' failed) is almost always not a “Telegram config” bug — it means the gateway tried to hit the Telegram Bot API to clear any leftover webhook state, and your host couldn’t reach api.telegram.org (DNS / IPv6 / proxy / egress / TLS).

A good quick triage:

  1. Version + baseline status
openclaw --version
openclaw channels status --probe
openclaw logs --follow
  1. Check if this is an IPv6/DNS egress issue (very common on some VPS/WSL2/etc.)
dig +short api.telegram.org A
dig +short api.telegram.org AAAA

If you get AAAA answers but your box has broken IPv6 egress, you’ll see exactly these “Network request failed” type errors.

#
  1. Force IPv4 behavior (workaround)
    In your config:
channels:
  telegram:
    network:
      autoSelectFamily: false

Or temporarily via env:

  • OPENCLAW_TELEGRAM_DISABLE_AUTO_SELECT_FAMILY=1
  1. If your host needs a proxy to reach Telegram, set:
channels:
  telegram:
    proxy: socks5://user:pass@proxy-host:1080