44 replies

Error: SECURITY ERROR: Gateway URL "ws://172.23.0.2:18789" uses plaintext ws:// in Docker

Hello

I have a MiniPC server on my network with Ubuntu. In it, I have installed openclaw with docker. I managed to set up the web ui + telegram bot. But the web UI can't run commands, so I'd like to give it access.

The problem is that when I call the command

/approve id allow-always

/approve id allow-always

I get the following error on the chat (both when called fom webui and telegram):

Failed to submit approval: Error: SECURITY ERROR: Gateway URL "ws://172.23.0.2:18789" uses plaintext ws:// to a non-loopback address.
Both credentials and chat data would be exposed to network interception.
Source: local lan 172.23.0.2
Config: /home/node/.openclaw/openclaw.json
Fix: Use wss:// for the gateway URL, or connect via SSH tunnel to localhost.

Failed to submit approval: Error: SECURITY ERROR: Gateway URL "ws://172.23.0.2:18789" uses plaintext ws:// to a non-loopback address.
Both credentials and chat data would be exposed to network interception.
Source: local lan 172.23.0.2
Config: /home/node/.openclaw/openclaw.json
Fix: Use wss:// for the gateway URL, or connect via SSH tunnel to localhost.

This is my gateway configuration:

"gateway": {
    "port": 18789,
    "mode": "local",
    "bind": "lan",
    "controlUi": {
      "allowInsecureAuth": true
    },
    "auth": {
      "mode": "token",
      "token": "my-token-here-matches-.env"
    },
    "trustedProxies": [
      "172.23.0.0/16", "127.0.0.1"
    ],
    "tailscale": {
      "mode": "off",
      "resetOnExit": false
    },
    "nodes": {
      "denyCommands": [
        "camera.snap",
        "camera.clip",
        "screen.record",
        "calendar.add",
        "contacts.add",
        "reminders.add"
      ]
    }
  },

"gateway": {
    "port": 18789,
    "mode": "local",
    "bind": "lan",
    "controlUi": {
      "allowInsecureAuth": true
    },
    "auth": {
      "mode": "token",
      "token": "my-token-here-matches-.env"
    },
    "trustedProxies": [
      "172.23.0.0/16", "127.0.0.1"
    ],
    "tailscale": {
      "mode": "off",
      "resetOnExit": false
    },
    "nodes": {
      "denyCommands": [
        "camera.snap",
        "camera.clip",
        "screen.record",
        "calendar.add",
        "contacts.add",
        "reminders.add"
      ]
    }
  },

To run commands I have to log into the MiniPC through ssh and run this:

docker compose run --rm openclaw-cli devices list --url ws://127.0.0.1:18789 --token "$OPENCLAW_GATEWAY_TOKEN"

docker compose run --rm openclaw-cli devices list --url ws://127.0.0.1:18789 --token "$OPENCLAW_GATEWAY_TOKEN"

which is not ideal. I'd like for the WebUI to be able to create some cron jobs and so on.

I don't want to setup HTTPS as this runs in a contained network.

And just to clarify my network is:

[PC]  ---   [MINI PC [Docker container] ]

[PC]  ---   [MINI PC [Docker container] ]

And I'm connecting to the UI from the PC

What's wrong with this setup? What should I do to fix it?

FotC�

Friends of the Crustacean 🦞🤝•3w ago•

44 replies

lpares12

Error: SECURITY ERROR: Gateway URL "ws://172.23.0.2:18789" uses plaintext ws:// in Docker

Hello

/approve id allow-always

/approve id allow-always

I get the following error on the chat (both when called fom webui and telegram):

Failed to submit approval: Error: SECURITY ERROR: Gateway URL "ws://172.23.0.2:18789" uses plaintext ws:// to a non-loopback address.
Both credentials and chat data would be exposed to network interception.
Source: local lan 172.23.0.2
Config: /home/node/.openclaw/openclaw.json
Fix: Use wss:// for the gateway URL, or connect via SSH tunnel to localhost.

Failed to submit approval: Error: SECURITY ERROR: Gateway URL "ws://172.23.0.2:18789" uses plaintext ws:// to a non-loopback address.
Both credentials and chat data would be exposed to network interception.
Source: local lan 172.23.0.2
Config: /home/node/.openclaw/openclaw.json
Fix: Use wss:// for the gateway URL, or connect via SSH tunnel to localhost.

This is my gateway configuration:

"gateway": {
    "port": 18789,
    "mode": "local",
    "bind": "lan",
    "controlUi": {
      "allowInsecureAuth": true
    },
    "auth": {
      "mode": "token",
      "token": "my-token-here-matches-.env"
    },
    "trustedProxies": [
      "172.23.0.0/16", "127.0.0.1"
    ],
    "tailscale": {
      "mode": "off",
      "resetOnExit": false
    },
    "nodes": {
      "denyCommands": [
        "camera.snap",
        "camera.clip",
        "screen.record",
        "calendar.add",
        "contacts.add",
        "reminders.add"
      ]
    }
  },

"gateway": {
    "port": 18789,
    "mode": "local",
    "bind": "lan",
    "controlUi": {
      "allowInsecureAuth": true
    },
    "auth": {
      "mode": "token",
      "token": "my-token-here-matches-.env"
    },
    "trustedProxies": [
      "172.23.0.0/16", "127.0.0.1"
    ],
    "tailscale": {
      "mode": "off",
      "resetOnExit": false
    },
    "nodes": {
      "denyCommands": [
        "camera.snap",
        "camera.clip",
        "screen.record",
        "calendar.add",
        "contacts.add",
        "reminders.add"
      ]
    }
  },

To run commands I have to log into the MiniPC through ssh and run this:

docker compose run --rm openclaw-cli devices list --url ws://127.0.0.1:18789 --token "$OPENCLAW_GATEWAY_TOKEN"

docker compose run --rm openclaw-cli devices list --url ws://127.0.0.1:18789 --token "$OPENCLAW_GATEWAY_TOKEN"

which is not ideal. I'd like for the WebUI to be able to create some cron jobs and so on.

I don't want to setup HTTPS as this runs in a contained network.

And just to clarify my network is:

[PC]  ---   [MINI PC [Docker container] ]

[PC]  ---   [MINI PC [Docker container] ]

And I'm connecting to the UI from the PC

What's wrong with this setup? What should I do to fix it?

Error: SECURITY ERROR: Gateway URL "ws://172.23.0.2:18789" uses plaintext ws:// in Docker

Similar Threads

Error: SECURITY ERROR: Gateway URL "ws://172.23.0.2:18789" uses plaintext ws:// in Docker

Similar Threads

Similar Threads

Similar Threads