openclaw - 💡(How to fix) Fix Telegram file download blocked by SSRF policy when using Fake-IP proxy (172.19.0.1 treated as private IP) [1 participants]

Bug Description

When OpenClaw runs behind a Clash/Mihomo proxy in Fake-IP mode, Telegram file downloads fail with the following error:

[security] blocked URL fetch (url-fetch) target=https://api.telegram.org/file/botXXXXXXXX:AAH.../photos/file_XX.jpg reason=Blocked hostname (not in allowlist): 172.19.0.1

The proxy resolves api.telegram.org to a private IP (e.g. 172.19.0.1) in Fake-IP mode, and the SSRF security module blocks the request.

Steps to Reproduce

1. Configure OpenClaw with a Telegram channel
2. Configure the Telegram channel to use a HTTP proxy (e.g. channels.telegram.proxy: "http://172.19.0.1:7897")
3. Ensure the proxy runs in Fake-IP DNS mode — this causes all DNS resolutions to return fake private IPs
4. Send a file via the Telegram bot (or forward a file to the bot)
5. OpenClaw attempts to download the file via api.telegram.org/file/...
6. The fetch resolves to a private IP (e.g. 172.19.0.1) and is blocked

Expected Behavior

Telegram files should download successfully. Even when proxy resolves the hostname to a private IP, the channels.telegram.network.dangerouslyAllowPrivateNetwork: true config should permit the request.

Actual Behavior

The request is blocked at the SSRF layer with Blocked hostname (not in allowlist): 172.19.0.1.

Configuration

{
  "channels": {
    "telegram": {
      "enabled": true,
      "proxy": "http://172.19.0.1:7897",
      "network": {
        "dangerouslyAllowPrivateNetwork": true
      }
    }
  }
}

Environment

• OpenClaw version: 2026.4.5
• Platform: WSL2 / Linux
• Proxy: Clash/Mihomo with Fake-IP DNS mode
• Telegram channel configured with proxy

Root Cause Analysis

The channels.telegram.network.dangerouslyAllowPrivateNetwork setting only controls the Telegram Bot API communication layer (grammY client), but file downloads are performed via a separate internal HTTP fetch call that goes through the SSRF security module. The SSRF module does not respect channels.telegram.network.dangerouslyAllowPrivateNetwork and blocks the private IP directly.

Suggested Fix

Either:

1. Make channels.telegram.network.dangerouslyAllowPrivateNetwork also apply to Telegram file download HTTP fetch calls, OR
2. Add a new config path like channels.telegram.network.ssrfPolicy.dangerouslyAllowPrivateNetwork specifically for file downloads, OR
3. Document that api.telegram.org should be added to a hostname allowlist in the SSRF policy

Workaround

Add DOMAIN-SUFFIX,api.telegram.org,DIRECT to the Clash/Mihomo proxy rules to bypass the proxy for Telegram API requests, avoiding Fake-IP resolution.