Error during BlueBubbles integration with OpenClaw 4.11 - where is the gateway.json file?

[fossil raft]

Gateway throws error to connect to BlueBubbles API "blocked URL fetch (bluebubbles-api) target=http://****-macbook-air.tailb3913f.ts.net:12345/api/v1/ping reason=Blocked: resolves to private/internal/special-use IP address"). Hatched the agent via TUI and the gateway is embedded gateway. I need to change a "Security" setting in gateway.json file to set "allowInternalUrl" to true, but OpenClaw gateway does not pick the gateway.json file. I also cannot change this setting from Gateway control center UI .

I added a gateway.json file under ~/Library/Application Support/openclaw/gateway.json (in Mac), ~/.openclaw/gateway.json etc., but gateway does not pick these configuration files. How do I modify this configuration?

[elfin lava]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[tame cliff]

he problem is not with BlueBubbles itself. OpenClaw is blocking the BlueBubbles URL because the MacBook address is on a private/Tailscale network. Recent OpenClaw versions block these internal URLs by default for security.

The important point: OpenClaw does not use gateway.json for this setting.
The correct config file is:

~/.openclaw/openclaw.json

the Gateway reads config from ~/.openclaw/openclaw.json, not gateway.json. It also validates the config strictly, so wrong file names or wrong keys will be ignored or rejected.

Open this file:

~/.openclaw/openclaw.json

Find the BlueBubbles section and add this:

{
  channels: {
    bluebubbles: {
      enabled: true,
      serverUrl: "http://YOUR-MACBOOK-AIR.tailb3913f.ts.net:12345",
      password: "YOUR_BLUEBUBBLES_PASSWORD",
      webhookPath: "/bluebubbles-webhook",
      network: {
        dangerouslyAllowPrivateNetwork: true
      }
    }
  }
}

If the file already has channels.bluebubbles, do not replace the whole file. Just add this part inside BlueBubbles:

network: {
  dangerouslyAllowPrivateNetwork: true
}

This is the setting that has been used to fix BlueBubbles private-network blocking errors like:

blocked URL fetch (bluebubbles-api)
reason=Blocked hostname or private/internal/special-use IP address

Plz note this

A related OpenClaw issue shows the same BlueBubbles block and the fix using channels.bluebubbles.network.dangerouslyAllowPrivateNetwork: true.

Then restart OpenClaw Gateway

Run:

openclaw gateway restart

Then check:

openclaw health

or:

openclaw status --all