docs: recommend loopback-only gateway bind

This commit is contained in:
Peter Steinberger
2026-02-14 12:36:23 +01:00
parent 1fb52b4d7b
commit e21a7aad54

View File

@@ -53,7 +53,13 @@ For threat model + hardening guidance (including `openclaw security audit --deep
### Web Interface Safety
OpenClaw's web interface is intended for local use only. Do **not** bind it to the public internet; it is not hardened for public exposure.
OpenClaw's web interface (Gateway Control UI + HTTP endpoints) is intended for **local use only**.
- Recommended: keep the Gateway **loopback-only** (`127.0.0.1` / `::1`).
- Config: `gateway.bind="loopback"` (default).
- CLI: `openclaw gateway run --bind loopback`.
- Do **not** expose it to the public internet (no direct bind to `0.0.0.0`, no public reverse proxy). It is not hardened for public exposure.
- If you need remote access, prefer an SSH tunnel or Tailscale serve/funnel (so the Gateway still binds to loopback), plus strong Gateway auth.
## Runtime Requirements