5 replies

SECURITY ERROR: Gateway URL uses plaintext ws:// to a non-loopback address.

I am running Openclaw on a VM behind NPM on the host. It was working fine until today.

Now I'm getting the error below. I have tried many things but have not been able to resolve it.

[openclaw] Failed to start CLI: Error: SECURITY ERROR: Gateway URL "ws://192.168.2.6:18789" uses plaintext ws:// to a non-loopback address.
Both credentials and chat data would be exposed to network interception.
Source: local lan 192.168.2.6
Config: /***/.openclaw/openclaw.json
Fix: Use wss:// for the gateway URL, or connect via SSH tunnel to localhost.
    at buildGatewayConnectionDetails (file:///***/.npm-global/lib/node_modules/openclaw/dist/call-DZzTR0NL.js:312:40)
    at file:///***/.npm-global/lib/node_modules/openclaw/dist/status-CuCaWzfB.js:1537:29
    at async withProgress (file:///***/.npm-global/lib/node_modules/openclaw/dist/progress-Clpi3Ckj.js:116:10)
    at async scanStatus (file:///***/.npm-global/lib/node_modules/openclaw/dist/status-CuCaWzfB.js:1509:9)
    at async statusCommand (file:///***/.npm-global/lib/node_modules/openclaw/dist/status-CuCaWzfB.js:1622:249)
    at async Object.run (file:///***/.npm-global/lib/node_modules/openclaw/dist/run-main-ymxgIjRa.js:139:3)
    at async runCli (file:///***/.npm-global/lib/node_modules/openclaw/dist/run-main-ymxgIjRa.js:377:6)

[openclaw] Failed to start CLI: Error: SECURITY ERROR: Gateway URL "ws://192.168.2.6:18789" uses plaintext ws:// to a non-loopback address.
Both credentials and chat data would be exposed to network interception.
Source: local lan 192.168.2.6
Config: /***/.openclaw/openclaw.json
Fix: Use wss:// for the gateway URL, or connect via SSH tunnel to localhost.
    at buildGatewayConnectionDetails (file:///***/.npm-global/lib/node_modules/openclaw/dist/call-DZzTR0NL.js:312:40)
    at file:///***/.npm-global/lib/node_modules/openclaw/dist/status-CuCaWzfB.js:1537:29
    at async withProgress (file:///***/.npm-global/lib/node_modules/openclaw/dist/progress-Clpi3Ckj.js:116:10)
    at async scanStatus (file:///***/.npm-global/lib/node_modules/openclaw/dist/status-CuCaWzfB.js:1509:9)
    at async statusCommand (file:///***/.npm-global/lib/node_modules/openclaw/dist/status-CuCaWzfB.js:1622:249)
    at async Object.run (file:///***/.npm-global/lib/node_modules/openclaw/dist/run-main-ymxgIjRa.js:139:3)
    at async runCli (file:///***/.npm-global/lib/node_modules/openclaw/dist/run-main-ymxgIjRa.js:377:6)

FotC�

Friends of the Crustacean 🦞🤝•3w ago•

5 replies

BarryB

SECURITY ERROR: Gateway URL uses plaintext ws:// to a non-loopback address.

I am running Openclaw on a VM behind NPM on the host. It was working fine until today.

Now I'm getting the error below. I have tried many things but have not been able to resolve it.

[openclaw] Failed to start CLI: Error: SECURITY ERROR: Gateway URL "ws://192.168.2.6:18789" uses plaintext ws:// to a non-loopback address.
Both credentials and chat data would be exposed to network interception.
Source: local lan 192.168.2.6
Config: /***/.openclaw/openclaw.json
Fix: Use wss:// for the gateway URL, or connect via SSH tunnel to localhost.
    at buildGatewayConnectionDetails (file:///***/.npm-global/lib/node_modules/openclaw/dist/call-DZzTR0NL.js:312:40)
    at file:///***/.npm-global/lib/node_modules/openclaw/dist/status-CuCaWzfB.js:1537:29
    at async withProgress (file:///***/.npm-global/lib/node_modules/openclaw/dist/progress-Clpi3Ckj.js:116:10)
    at async scanStatus (file:///***/.npm-global/lib/node_modules/openclaw/dist/status-CuCaWzfB.js:1509:9)
    at async statusCommand (file:///***/.npm-global/lib/node_modules/openclaw/dist/status-CuCaWzfB.js:1622:249)
    at async Object.run (file:///***/.npm-global/lib/node_modules/openclaw/dist/run-main-ymxgIjRa.js:139:3)
    at async runCli (file:///***/.npm-global/lib/node_modules/openclaw/dist/run-main-ymxgIjRa.js:377:6)

[openclaw] Failed to start CLI: Error: SECURITY ERROR: Gateway URL "ws://192.168.2.6:18789" uses plaintext ws:// to a non-loopback address.
Both credentials and chat data would be exposed to network interception.
Source: local lan 192.168.2.6
Config: /***/.openclaw/openclaw.json
Fix: Use wss:// for the gateway URL, or connect via SSH tunnel to localhost.
    at buildGatewayConnectionDetails (file:///***/.npm-global/lib/node_modules/openclaw/dist/call-DZzTR0NL.js:312:40)
    at file:///***/.npm-global/lib/node_modules/openclaw/dist/status-CuCaWzfB.js:1537:29
    at async withProgress (file:///***/.npm-global/lib/node_modules/openclaw/dist/progress-Clpi3Ckj.js:116:10)
    at async scanStatus (file:///***/.npm-global/lib/node_modules/openclaw/dist/status-CuCaWzfB.js:1509:9)
    at async statusCommand (file:///***/.npm-global/lib/node_modules/openclaw/dist/status-CuCaWzfB.js:1622:249)
    at async Object.run (file:///***/.npm-global/lib/node_modules/openclaw/dist/run-main-ymxgIjRa.js:139:3)
    at async runCli (file:///***/.npm-global/lib/node_modules/openclaw/dist/run-main-ymxgIjRa.js:377:6)

SECURITY ERROR: Gateway URL uses plaintext ws:// to a non-loopback address.

Similar Threads

SECURITY ERROR: Gateway URL uses plaintext ws:// to a non-loopback address.

Similar Threads

Similar Threads

Similar Threads