Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

When using the Comfy plugin in mode: "local" with a DNS hostname as baseUrl that resolves to a private/LAN IP (e.g. https://comfy.local.example.com → 192.168.178.xx), the image_generate call is blocked by the SSRF guard with:

Blocked: resolves to private/internal/special-use IP address

Using the same ComfyUI endpoint with an IP literal as baseUrl (e.g. http://192.168.178.xxx:port) works correctly.

Configuration

{ "plugins": { "entries": { "comfy": { "config": { "mode": "local", "baseUrl": "https://comfy.local.example.com", "allowPrivateNetwork": true, "image": { "workflowPath": "~/.openclaw/workflows/comfy/flux-api.json", "promptNodeId": "27", "promptInputName": "text", "outputNodeId": "9" } } } } } }

Root Cause

In workflow-runtime-*.js, resolveComfyNetworkPolicy builds the SSRF bypass policy only when isPrivateOrLoopbackHost(hostname) returns true:

function resolveComfyNetworkPolicy(params) { const hostname = normalizeOptionalLowercaseString(parsed.hostname) ?? ""; if (!hostname || !params.allowPrivateNetwork || !isPrivateOrLoopbackHost(hostname)) return {}; return { apiPolicy: mergeSsrFPolicies( buildHostnameAllowlistPolicyFromSuffixAllowlist([hostname]), ssrfPolicyFromDangerouslyAllowPrivateNetwork(true) ) }; }

isPrivateOrLoopbackHost (in net-*.js) checks if the hostname string is a parseable IP literal or localhost. DNS hostnames like comfy.local.example.com are not parseable as IPs, so it returns false — even though the hostname resolves to 192.168.178.xx (RFC1918 private).

As a result, resolveComfyNetworkPolicy returns {} (no bypass policy). The subsequent HTTP fetch goes through the default SSRF guard, which does resolve DNS and correctly identifies the IP as private → blocked.

The gap: the plugin correctly sets allowPrivateNetwork: true for local mode, but the function that builds the SSRF bypass only works for IP literal hostnames, not DNS hostnames that resolve to private IPs.

Expected Behavior

When mode: "local" and allowPrivateNetwork: true, Comfy API requests to baseUrl should be allowed regardless of whether the hostname is an IP literal or a DNS name resolving to a private IP.

Workaround

Use an IP literal as baseUrl instead of a DNS hostname. This works but loses TLS/SNI and requires knowing the IP address at config time.

Environment

• OpenClaw: latest (installed via npm) • Host: Linux, kernel 6.8.0-110-generic • DNS: Local AdGuard Home resolving *.local.example.com to LAN IPs • ComfyUI: v0.20.1 on Docker

Steps to reproduce

Steps to Reproduce

1. Set up ComfyUI on a LAN host (e.g. Docker on Ip:Port)

2. Configure a DNS hostname pointing to a private/LAN IP (e.g. AdGuard Home: comfy.local.example.com → Ip of server hosting Comfy)

3. Set up a reverse proxy (e.g. AdGuard) to forward https://comfy.local.example.com to the ComfyUI container

4. Configure OpenClaw Comfy plugin in openclaw.json:{ "plugins": { "entries": { "comfy": { "config": { "mode": "local", "baseUrl": "https://comfy.local.example.com", "allowPrivateNetwork": true, "image": { "workflowPath": "~/.openclaw/workflows/comfy/flux-api.json", "promptNodeId": "6", "outputNodeId": "9" } } } } } }

5. Restart OpenClaw Gateway

6. Call image_generate with model: "comfy/workflow" and any prompt

7. Request fails with: Blocked: resolves to private/internal/special-use IP address

8. Change baseUrl to http://ip:port (IP literal)

9. Restart Gateway and retry — request succeeds

Expected behavior

When mode: "local" and allowPrivateNetwork: true, the Comfy plugin should allow requests to the configured baseUrl regardless of whether it's a DNS hostname or IP literal. The allowPrivateNetwork: true flag (automatically set for local mode) should permit private network access, including for DNS hostnames that resolve to private IPs.

Actual behavior

Requests to baseUrl values that are DNS hostnames resolving to private/LAN IPs are blocked by the SSRF guard with error: Blocked: resolves to private/internal/special-use IP address. The root cause is that isPrivateOrLoopbackHost() in resolveComfyNetworkPolicy only recognizes IP literals (e.g. 192.168.178.xx) and localhost — not DNS hostnames (e.g. comfy.local.example.com) that resolve to private IPs. Since the function returns false for DNS hostnames, the network bypass policy is never built, and the lower-level SSRF guard (which does resolve DNS) blocks the request.

OpenClaw version

v2026.5.3-1

Operating system

Ubuntu 24.04.4 LTS

Install method

npm global

Model

gpt 5.5

Provider / routing chain

openclaw local -> codex via api

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response