openclaw doctor --non-interactive and openclaw config validate as merge gates. All behavior is governed by upstream official documentation — including the configuration reference, CLI doctor, and gateway doctor.
Goal: Loopback-only Control Plane, Minimize Attack Surface
The OpenClaw gateway multiplexes WebSocket and HTTP on port 18789 by default. The configuration reference states that gateway.bind: "loopback" locks the listener to the local loopback address, while non-loopback binding requires gateway auth (token, password, or a strictly configured trusted proxy). For shared remote Macs, the best approach is: loopback binding + token mode, where operators and automation access the port via an encrypted tunnel instead of exposing 18789 on the host's public network interface.
This article pairs with: OpenClaw on nozcloud Germany: Daemon Onboarding and Compliance Baseline. To purchase or adjust configuration, visit the purchase page and compare plans on the pricing page.
Minimal Reproducible Steps (Remote Mac)
Run the following procedure on a test machine first, then push the same plist, SSH config, and CI jobs to production after validation.
- SSH baseline setup. Create a dedicated macOS user for OpenClaw. Install only the approved OpenClaw version, then verify non-interactive SSH via key authentication (disable password auth for that account in
sshd_configif policy allows). - Declare binding and auth in JSON5. In
~/.openclaw/openclaw.json, keepgateway.mode: "local", setgateway.bind: "loopback", and configuregateway.auth.mode: "token"withgateway.auth.token: "${OPENCLAW_GATEWAY_TOKEN}". If both token and password objects are present, explicitly setgateway.auth.modeto avoid ambiguity at startup. - Inject the token — don't commit secret paths to Git. Export
OPENCLAW_GATEWAY_TOKENvia the LaunchDaemon'sEnvironmentVariablesdictionary or a root-owned environment file with strict POSIX permissions. For first boot, runopenclaw doctor --generate-gateway-tokenin a secure admin shell. - No-TTY health check. Run
openclaw config validatethenopenclaw doctor --non-interactivein sequence. The--non-interactiveflag skips interactive prompts, applies safe migrations, and avoids interactive OAuth refresh — ideal for cron and CI. - Install or restart the gateway service. Use the vendor's standardized process (e.g.
openclaw gateway installwith your pinned parameters). Confirm thatopenclaw gateway statusshows the listener healthy on loopback only. - Establish SSH LocalForward from your local workstation. Run
ssh -N -L 18789:127.0.0.1:18789 openclaw-svc@germany-host.example(replace the username and hostname). Local tools can then reachws://127.0.0.1:18789while traffic is encrypted over SSH. - Verify the token path. Once the tunnel is up, connect to
127.0.0.1:18789from your laptop using Bearer Token as documented in your runbook. Intentionally send a wrong token: you should see an auth failure rather than silent pass — proof of end-to-end enforcement.
0.0.0.0 without compensating controls dramatically increases service-discovery and brute-force risk. If non-SSH access is truly required, put a hardened reverse proxy with mTLS or Tailscale Serve in front and re-read the trusted-proxy section of the configuration reference instead of skipping auth.
Compliance-Oriented Attack Surface Checklist
The following items do not constitute legal advice; they translate the principle of "least privilege" into concrete checkpoints that security reviewers can verify.
- No plaintext tokens in shell history: Load secrets via LaunchDaemon or a CI secret injector — never inline
exportin a shared screen session. - Separate ops SSH accounts from service accounts: Human users have their own UNIX principals; the OpenClaw daemon user should not own your personal dotfiles.
- Review gateway config changes in PRs: Any modification to
gateway.bind,gateway.auth,hooks, orgateway.httpendpoints requires two-person review. - Back up config before doctor runs: Keep a timestamped copy of
openclaw.jsonbefore upgrades; if a migration drops auth metadata, restore from artifact storage and restart the service. - Document emergency procedures: If someone temporarily relaxes binding mode during incident response, file a ticket immediately and roll back within the SLA window.
Merge Gate Approach (GitHub Actions Pseudocode Example)
Commit a read-only pinned copy or sanitized excerpt of your production config to Git — never the production token. Inject a one-time OPENCLAW_GATEWAY_TOKEN via CI secrets so that validation paths requiring environment variable substitution execute correctly. The job should include the following steps:
- Install the same OpenClaw minor version as production.
- Apply
openclaw config validateagainst the merged result of the checked-in template and test secrets. - Run
openclaw doctor --non-interactive; fail if warnings exceed policy thresholds (many teams treat any "auth missing" line as a hard error). - Optionally run
openclaw doctor --deepnightly rather than on every PR — deep scans take longer and may require elevated privileges.
Follow your internal ops runbook for upgrade issues; if you hit blockers around provisioning or SSH access, submit a ticket via the Help Center link below.
Need dedicated hardware for this setup?
Deploy a Mac mini on a Germany node via the purchase page, match unified memory and model workload on the pricing page, and contact the Help Center for provisioning or SSH access issues.