Skip to content

[Bug]: SECURITY ERROR on bind for remote access #21158

@autronix

Description

@autronix

Summary

Installed 2026.2.19 from 2026.2.17, gateway no longer starts with "bind": "lan". Running openclaw doctor --fix yields:

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

Steps to reproduce

  1. was running 2026.2.17 with bind set to lan, was able to access openclaw on the local network
  2. updated to 2026.2.19 using curl -fsSL --proto '=https' --tlsv1.2 https://openclaw.ai/install.sh | bash -s --git
  3. no longer able to access openclaw on local network, doctor throws error.

Expected behavior

  • blocking is fine, but correct configuration setting should be recommended for openclaw.json
  • document this case

Actual behavior

  • no information about how to resolve the issue and be able to start the gateway with the "insecure" configuration

OpenClaw version

2026.2.19

Operating system

Ubuntu 24.04

Install method

online bash

Logs, screenshots, and evidence

Image

Impact and severity

No response

Additional information

I tried setting the gateway.remote.url to wss://ip:port, but it doesn't seem to have an impact. (I see the error is triggered here

if (!isSecureWebSocketUrl(url)) {
).

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingsecuritySecurity documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions