2026.2.19-2 breaks plaintext ws:// node connections on L
Upgraded gateway + two remote nodes from 2026.2.17 to 2026.2.19-2. Gateway starts fine on HQ (localhost). Both remote nodes now fail to connect with:
SECURITY ERROR: Cannot connect to "10.0.0.10" over plaintext ws://. Both credentials and chat data would be exposed to network interception.
This is a home lab โ all three machines on the same 10.0.0.x subnet. No internet exposure. Nodes connect to gateway at ws://10.0.0.10:18789.
Tried: OPENCLAW_ALLOW_INSECURE=1, OPENCLAW_INSECURE=1, gateway.remote.insecure, gateway.remote.allowInsecure, gateway.security.allowInsecureLan โ all rejected or ignored. openclaw node run has no --insecure flag.
Is there a way to allow plaintext ws:// on a trusted LAN? Or is wss:// with self-signed cert the only path forward? Rolled nodes back to 2026.2.17 for now. Gateway stays on 2026.2.19-2.
SECURITY ERROR: Cannot connect to "10.0.0.10" over plaintext ws://. Both credentials and chat data would be exposed to network interception.
This is a home lab โ all three machines on the same 10.0.0.x subnet. No internet exposure. Nodes connect to gateway at ws://10.0.0.10:18789.
Tried: OPENCLAW_ALLOW_INSECURE=1, OPENCLAW_INSECURE=1, gateway.remote.insecure, gateway.remote.allowInsecure, gateway.security.allowInsecureLan โ all rejected or ignored. openclaw node run has no --insecure flag.
Is there a way to allow plaintext ws:// on a trusted LAN? Or is wss:// with self-signed cert the only path forward? Rolled nodes back to 2026.2.17 for now. Gateway stays on 2026.2.19-2.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,426Members
Resources
Similar Threads
Was this page helpful?
