Environment

• openclaw: 2026.3.11
• Node.js: v22.22.0
• OS: Ubuntu 24.04 (Vultr VPS)
• IPv6: present but not routable (times out)

Problem

On a VPS where IPv6 is present but not routable, the Telegram provider enters a permanent failure loop:

1. Attempts IPv6 connection → ETIMEDOUT / ENETUNREACH
2. Logs fetch fallback: enabling sticky IPv4-only dispatcher
3. Attempts to start provider via IPv4
4. Silently fails — no error logged, no retry, no confirmation
5. Provider never connects

Discord and WhatsApp connect successfully every time. Only Telegram fails.

Config tried

• autoSelectFamily: false (original) — fails
• autoSelectFamily: true + dnsResultOrder: ipv4first — fallback triggers but still fails

Verified working

• curl -4 to api.telegram.org → works
• Node.js TCP connection to 149.154.166.110:443 → works
• node fetch('https://api.telegram.org/...') → works
• Bot token valid (getMe returns ok)

Expected behavior

After IPv4 fallback triggers, the provider should connect successfully via IPv4 and log a successful polling confirmation.

Workaround

None found. Gateway restart loop only works intermittently.