openclaw - 💡(How to fix) Fix [Bug]: Mattermost internal network deployment, gateway cannot be established [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#74958Fetched 2026-05-01 05:39:36
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
2
Author
Timeline (top)
labeled ×2closed ×1commented ×1

After installing OpenClaw and Mattermost, and configuring channels, mattermost, and baseUrl to a specific internal IP address, OpenClaw gateway failed to start. Code analysis revealed that the OpenClaw mattermost plugin does not support bypassing verification by setting dangerouslyAllowPrivateNetwork to true.

The error message is as follows: 14:16:50 [security] blocked URL fetch (mattermost-probe) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address 14:16:50 [gateway] http server listening (8 plugins: acpx, bonjour, browser, device-pair, mattermost, memory-core, phone-control, talk-voice; 4.3s) 14:16:50 [gateway] log file: /tmp/openclaw/openclaw-2026-04-30.log 14:16:50 [gateway] security warning: dangerous config flags enabled: gateway.controlUi.allowInsecureAuth=true, browser.ssrfPolicy.dangerouslyAllowPrivateNetwork=true. Run openclaw security audit. 14:16:50 [gateway] starting channels and sidecars... 14:17:01 [codex/catalog] codex model discovery failed; using fallback catalog 14:17:15 [mattermost] [default] starting channel 14:17:15 [security] blocked URL fetch (mattermost-api) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address 14:17:15 [mattermost] API auth failed: SsrFBlockedError: Blocked hostname or private/internal/special-use IP address 14:17:15 [mattermost] API not accessible, retrying in 2s 14:17:15 [plugins] embedded acpx runtime backend registered (cwd: /home/xxx/.openclaw/workspace) 14:17:16 [browser/server] Browser control listening on http://127.0.0.1:18791/ (auth=token) 14:17:16 [gateway] ready 14:17:16 [heartbeat] started 14:17:16 [plugins] [hooks] running gateway_start (1 handlers) 14:17:18 [security] blocked URL fetch (mattermost-api) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address 14:17:18 [mattermost] API auth failed: SsrFBlockedError: Blocked hostname or private/internal/special-use IP address 14:17:18 [mattermost] API not accessible, retrying in 4s 14:17:21 [security] blocked URL fetch (mattermost-api) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address

Error Message

The error message is as follows: Openclaw gateway failed launch. The error message is as follows:

Root Cause

After installing OpenClaw and Mattermost, and configuring channels, mattermost, and baseUrl to a specific internal IP address, OpenClaw gateway failed to start. Code analysis revealed that the OpenClaw mattermost plugin does not support bypassing verification by setting dangerouslyAllowPrivateNetwork to true.

The error message is as follows: 14:16:50 [security] blocked URL fetch (mattermost-probe) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address 14:16:50 [gateway] http server listening (8 plugins: acpx, bonjour, browser, device-pair, mattermost, memory-core, phone-control, talk-voice; 4.3s) 14:16:50 [gateway] log file: /tmp/openclaw/openclaw-2026-04-30.log 14:16:50 [gateway] security warning: dangerous config flags enabled: gateway.controlUi.allowInsecureAuth=true, browser.ssrfPolicy.dangerouslyAllowPrivateNetwork=true. Run openclaw security audit. 14:16:50 [gateway] starting channels and sidecars... 14:17:01 [codex/catalog] codex model discovery failed; using fallback catalog 14:17:15 [mattermost] [default] starting channel 14:17:15 [security] blocked URL fetch (mattermost-api) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address 14:17:15 [mattermost] API auth failed: SsrFBlockedError: Blocked hostname or private/internal/special-use IP address 14:17:15 [mattermost] API not accessible, retrying in 2s 14:17:15 [plugins] embedded acpx runtime backend registered (cwd: /home/xxx/.openclaw/workspace) 14:17:16 [browser/server] Browser control listening on http://127.0.0.1:18791/ (auth=token) 14:17:16 [gateway] ready 14:17:16 [heartbeat] started 14:17:16 [plugins] [hooks] running gateway_start (1 handlers) 14:17:18 [security] blocked URL fetch (mattermost-api) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address 14:17:18 [mattermost] API auth failed: SsrFBlockedError: Blocked hostname or private/internal/special-use IP address 14:17:18 [mattermost] API not accessible, retrying in 4s 14:17:21 [security] blocked URL fetch (mattermost-api) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After installing OpenClaw and Mattermost, and configuring channels, mattermost, and baseUrl to a specific internal IP address, OpenClaw gateway failed to start. Code analysis revealed that the OpenClaw mattermost plugin does not support bypassing verification by setting dangerouslyAllowPrivateNetwork to true.

The error message is as follows: 14:16:50 [security] blocked URL fetch (mattermost-probe) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address 14:16:50 [gateway] http server listening (8 plugins: acpx, bonjour, browser, device-pair, mattermost, memory-core, phone-control, talk-voice; 4.3s) 14:16:50 [gateway] log file: /tmp/openclaw/openclaw-2026-04-30.log 14:16:50 [gateway] security warning: dangerous config flags enabled: gateway.controlUi.allowInsecureAuth=true, browser.ssrfPolicy.dangerouslyAllowPrivateNetwork=true. Run openclaw security audit. 14:16:50 [gateway] starting channels and sidecars... 14:17:01 [codex/catalog] codex model discovery failed; using fallback catalog 14:17:15 [mattermost] [default] starting channel 14:17:15 [security] blocked URL fetch (mattermost-api) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address 14:17:15 [mattermost] API auth failed: SsrFBlockedError: Blocked hostname or private/internal/special-use IP address 14:17:15 [mattermost] API not accessible, retrying in 2s 14:17:15 [plugins] embedded acpx runtime backend registered (cwd: /home/xxx/.openclaw/workspace) 14:17:16 [browser/server] Browser control listening on http://127.0.0.1:18791/ (auth=token) 14:17:16 [gateway] ready 14:17:16 [heartbeat] started 14:17:16 [plugins] [hooks] running gateway_start (1 handlers) 14:17:18 [security] blocked URL fetch (mattermost-api) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address 14:17:18 [mattermost] API auth failed: SsrFBlockedError: Blocked hostname or private/internal/special-use IP address 14:17:18 [mattermost] API not accessible, retrying in 4s 14:17:21 [security] blocked URL fetch (mattermost-api) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address

Steps to reproduce

  1. start openclaw latest (2026.4.30)
  2. install openclaw and config model 、channel (mattermost ip:192.168....) etc...
  3. launch openclaw gateway

Expected behavior

It supports bypassing mattermost internal network verification through configuration, such as setting dangerouslyAllowPrivateNetwork to true. The OpenClaw gateway can start normally.

Actual behavior

Openclaw gateway failed launch. The error message is as follows: 14:16:50 [security] blocked URL fetch (mattermost-probe) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address 14:16:50 [gateway] http server listening (8 plugins: acpx, bonjour, browser, device-pair, mattermost, memory-core, phone-control, talk-voice; 4.3s) 14:16:50 [gateway] log file: /tmp/openclaw/openclaw-2026-04-30.log 14:16:50 [gateway] security warning: dangerous config flags enabled: gateway.controlUi.allowInsecureAuth=true, browser.ssrfPolicy.dangerouslyAllowPrivateNetwork=true. Run openclaw security audit. 14:16:50 [gateway] starting channels and sidecars... 14:17:01 [codex/catalog] codex model discovery failed; using fallback catalog 14:17:15 [mattermost] [default] starting channel 14:17:15 [security] blocked URL fetch (mattermost-api) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address 14:17:15 [mattermost] API auth failed: SsrFBlockedError: Blocked hostname or private/internal/special-use IP address 14:17:15 [mattermost] API not accessible, retrying in 2s 14:17:15 [plugins] embedded acpx runtime backend registered (cwd: /home/xxx/.openclaw/workspace) 14:17:16 [browser/server] Browser control listening on http://127.0.0.1:18791/ (auth=token) 14:17:16 [gateway] ready 14:17:16 [heartbeat] started 14:17:16 [plugins] [hooks] running gateway_start (1 handlers) 14:17:18 [security] blocked URL fetch (mattermost-api) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address 14:17:18 [mattermost] API auth failed: SsrFBlockedError: Blocked hostname or private/internal/special-use IP address 14:17:18 [mattermost] API not accessible, retrying in 4s 14:17:21 [security] blocked URL fetch (mattermost-api) targetOrigin=http://192.168.55.138:30025 reason=Blocked hostname or private/internal/special-use IP address

OpenClaw version

2026.4.26

Operating system

ubutu22.04

Install method

npm global

Model

qwen3.5

Provider / routing chain

openclaw->ai gateway -> qwen3.5

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The OpenClaw gateway fails to start due to the Mattermost plugin not supporting bypassing verification for private networks, despite setting dangerouslyAllowPrivateNetwork to true.

Guidance

  • The error message indicates that the Mattermost plugin is blocking the URL fetch due to a private/internal IP address, suggesting a configuration issue.
  • Verify that the dangerouslyAllowPrivateNetwork flag is set to true in the browser's SSRF policy, but note that this may not be sufficient for the Mattermost plugin.
  • Check the OpenClaw documentation for any specific configuration options or workarounds for the Mattermost plugin and private networks.
  • Consider using a different IP address or hostname for the Mattermost server that is not considered private or internal.

Example

No code snippet is provided as the issue seems to be related to configuration and plugin compatibility.

Notes

The OpenClaw version used is 2026.4.26, and the operating system is Ubuntu 22.04. The installation method was via npm global. However, without further information on the Mattermost plugin's configuration options, it's difficult to provide a more specific solution.

Recommendation

Apply a workaround by using a different IP address or hostname for the Mattermost server that is not considered private or internal, as the current configuration does not seem to be supported by the Mattermost plugin.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

It supports bypassing mattermost internal network verification through configuration, such as setting dangerouslyAllowPrivateNetwork to true. The OpenClaw gateway can start normally.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Mattermost internal network deployment, gateway cannot be established [1 comments, 2 participants]