Summary

Since upgrading to v2026.4.8, Telegram media downloads (images, files) fail with "could not download media" when routing traffic through an HTTP proxy (Tinyproxy). Downgrading to v2026.4.7 or earlier resolves the issue.

Regression window

• v2026.4.7: Fixed proxy-based media downloads (PR fix(slack): honor HTTPS_PROXY for Socket Mode WebSocket connections #62878 area — "stop rejecting operator-configured proxy hostnames in SSRF-guarded fetches") ✅ Media works
• v2026.4.8: Introduced "Network/fetch guard: skip target DNS pinning when trusted env-proxy mode is active" (PR fix(net): skip DNS pinning before trusted env proxy dispatch #59007) ❌ Media downloads break
• v2026.4.12: Still broken — no fix applied in 4.9–4.12

Environment

• Host: macOS (dave-mini, arm64) behind GFW
• Proxy: Tinyproxy on remote AWS instance (jp-aws), accessed via Tailscale
• Config: channels.telegram.proxy = "http://100.80.46.108:8888" in openclaw.json
• OpenClaw version (working): v2026.3.28
• Broken versions: v2026.4.8 through v2026.4.12

Expected behavior

Telegram media (images, voice messages, files) should download through the configured HTTP proxy, as they did in v2026.4.7 and earlier.

Actual behavior

Media downloads fail with "could not download media" error. Text messages and other channel operations work fine — only media downloads through the proxy are affected.

Likely cause

The DNS pinning change in v2026.4.8 (PR #59007) appears to interfere with how the proxy resolves Telegram CDN domains (*.t.me, cdn.telegram.org). When trusted env-proxy mode is active, skipping DNS pinning may cause the fetch guard to reject or misroute media download requests that go through the proxy.

Steps to reproduce

1. Configure Telegram channel with an HTTP proxy (Tinyproxy)
2. Upgrade to v2026.4.8+
3. Send or receive an image/media message
4. Observe "could not download media" error

Workaround

Downgrade to v2026.4.7 or earlier (v2026.3.28 confirmed working).