docs: clarify private ws node setup

This commit is contained in:
Peter Steinberger
2026-04-24 07:32:11 +01:00
parent f85806b6d7
commit b7fba2100f
6 changed files with 21 additions and 4 deletions

View File

@@ -77,7 +77,9 @@ Options:
For a node connecting to a non-loopback `ws://` Gateway on a trusted private
network, set `OPENCLAW_ALLOW_INSECURE_PRIVATE_WS=1`. Without it, node startup
fails closed and asks you to use `wss://`, an SSH tunnel, or Tailscale.
`openclaw node install` persists this opt-in into the supervised node service.
This is a process-environment opt-in, not an `openclaw.json` config key.
`openclaw node install` persists it into the supervised node service when it is
present in the install command environment.
## Service (background)