Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

The Matrix plugin's createMatrixClient does not accept or forward any SSRF policy parameter, so the channels.matrix.network.dangerouslyAllowPrivateNetwork config key defined in the schema has no effect and connections to homeservers resolving to private IPs fail with "Blocked: resolves to private/internal/special-use IP address".

Steps to reproduce

1. Run a Matrix homeserver (e.g. Conduit/Continuwuity/Synapse) at a hostname that resolves to a private IP (RFC1918, loopback, etc.) — for example matrix.example.local → 192.168.x.x or localhost.

2. In ~/.openclaw/openclaw.json, configure the Matrix channel pointing at that homeserver:

   "channels": {
     "matrix": {
       "enabled": true,
       "network": {
         "dangerouslyAllowPrivateNetwork": true
       },
       "accounts": {
         "default": {
           "homeserver": "https://matrix.example.local",
           "accessToken": "<valid token>",
           "network": {
             "dangerouslyAllowPrivateNetwork": true
           }
         }
       }
     }
   }

1. Run openclaw doctor — config validates successfully with no schema errors.

2. Run openclaw gateway restart.

3. Observe in the dashboard (Channels > Matrix) or openclaw doctor output: Matrix: failed (unknown) - Blocked: resolves to private/internal/special-use IP address

Expected: With dangerouslyAllowPrivateNetwork: true set, the Matrix plugin should connect to the homeserver. Actual: The plugin blocks the connection regardless of the config value.

Expected behavior

The Matrix plugin fails to connect to homeservers resolving to private IPs regardless of the dangerouslyAllowPrivateNetwork config value. The dashboard (Channels > Matrix) and openclaw doctor report:

Matrix: failed (unknown) - Blocked: resolves to private/internal/special-use IP address

Inspection of the plugin source at extensions/matrix/src/matrix/client/create-client.ts shows that createMatrixClient accepts only homeserver, userId, accessToken, encryption, localTimeoutMs, and accountId — no policy/network/allowPrivateNetwork parameter is accepted or forwarded to the @vector-im/matrix-bot-sdk MatrixClient constructor.

The SSRF gate raising the error is located in the shared plugin SDK at dist/plugin-sdk/ssrf-*.js, which reads policy?.dangerouslyAllowPrivateNetwork and policy?.allowPrivateNetwork via resolveAllowPrivateNetwork(params.policy). Because the Matrix plugin never passes a policy object through this code path, neither channels.matrix.network.dangerouslyAllowPrivateNetwork nor the per-account accounts.*.network.dangerouslyAllowPrivateNetwork has any effect.

Grepping the Matrix extension for dangerouslyAllowPrivateNetwork, allowPrivateNetwork, ssrf, or "resolves to private" returns no matches in non-test source, confirming the plugin has no integration with the SSRF policy layer.

Actual behavior

The Matrix plugin fails to connect to homeservers resolving to private IPs regardless of the dangerouslyAllowPrivateNetwork config value. The dashboard (Channels > Matrix) and openclaw doctor report:

Matrix: failed (unknown) - Blocked: resolves to private/internal/special-use IP address

Inspection of the plugin source at extensions/matrix/src/matrix/client/create-client.ts shows that createMatrixClient accepts only homeserver, userId, accessToken, encryption, localTimeoutMs, and accountId — no policy/network/allowPrivateNetwork parameter is accepted or forwarded to the @vector-im/matrix-bot-sdk MatrixClient constructor.

The SSRF gate raising the error is located in the shared plugin SDK at dist/plugin-sdk/ssrf-*.js, which reads policy?.dangerouslyAllowPrivateNetwork and policy?.allowPrivateNetwork via resolveAllowPrivateNetwork(params.policy). Because the Matrix plugin never passes a policy object through this code path, neither channels.matrix.network.dangerouslyAllowPrivateNetwork nor the per-account accounts.*.network.dangerouslyAllowPrivateNetwork has any effect.

Grepping the Matrix extension for dangerouslyAllowPrivateNetwork, allowPrivateNetwork, ssrf, or "resolves to private" returns no matches in non-test source, confirming the plugin has no integration with the SSRF policy layer.

OpenClaw version

2026.4.14 (323493f)

Operating system

MacOS 15.7.3

Install method

npm global

Model

Not relevant

Provider / routing chain

Not relevant

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

Affected users/systems/channels: Self-hosted users running a Matrix homeserver on a private/LAN IP address (RFC1918, loopback, .local, etc.) and configuring the OpenClaw Matrix channel to connect to it. Any homeserver resolving to a non-public IP is affected — whether reached by hostname or IP.

Severity: Blocks workflow. The Matrix channel cannot be used at all when pointed at a self-hosted homeserver on a private network. No config change or documented workaround resolves it; only workarounds that remove the private-IP condition entirely (e.g. exposing the homeserver publicly via a Cloudflare tunnel) restore functionality.

Frequency: Always reproducible. Occurs on every connection attempt regardless of which account or homeserver is configured, as long as DNS resolves to a private-range address.

Consequence: The Matrix channel is fully non-functional for self-hosted Matrix deployments on LAN, which is a primary use case for self-hosted OpenClaw users. Affected users must either expose their homeserver to the public internet (adding infrastructure complexity and attack surface) or abandon the Matrix channel entirely.

Additional information

No response