macOS NodeHost over SSH tunnel → unauthorized: gateway token mismatch (LaunchAgent env + Docker gate
✅Solved
I’ve got an OpenClaw Gateway running on a VPS in Docker (Discord + Telegram working). I also have a macOS NodeHost installed as a LaunchAgent to enable browser proxy / system.run on my Mac.
The NodeHost connects via an SSH tunnel to the VPS gateway, using:
--host 127.0.0.1 --port 18790 (local end of the tunnel)
tunnel forwards to the VPS gateway WS port
It used to work, but now the NodeHost fails with:
unauthorized: gateway token mismatch (provide gateway auth token)
node host gateway closed (1008): unauthorized: gateway token mismatch
nc -vz 127.0.0.1 18790 succeeds, so something is listening on that local port, but auth fails.
What I suspect: the LaunchAgent doesn’t have OPENCLAW_GATEWAY_TOKEN set (or it’s stale vs the token the Docker gateway is currently using). I’m looking for the correct/idiomatic way to:
1) retrieve/verify the gateway token on the VPS (Docker env vs config), without pasting secrets in chat
2) persist OPENCLAW_GATEWAY_TOKEN for the Mac LaunchAgent so the NodeHost stays connected across reboots/logouts
Any recommended best practice here (LaunchAgent EnvironmentVariables vs launchctl setenv vs other)?
The NodeHost connects via an SSH tunnel to the VPS gateway, using:
--host 127.0.0.1 --port 18790 (local end of the tunnel)
tunnel forwards to the VPS gateway WS port
It used to work, but now the NodeHost fails with:
unauthorized: gateway token mismatch (provide gateway auth token)
node host gateway closed (1008): unauthorized: gateway token mismatch
nc -vz 127.0.0.1 18790 succeeds, so something is listening on that local port, but auth fails.
What I suspect: the LaunchAgent doesn’t have OPENCLAW_GATEWAY_TOKEN set (or it’s stale vs the token the Docker gateway is currently using). I’m looking for the correct/idiomatic way to:
1) retrieve/verify the gateway token on the VPS (Docker env vs config), without pasting secrets in chat
2) persist OPENCLAW_GATEWAY_TOKEN for the Mac LaunchAgent so the NodeHost stays connected across reboots/logouts
Any recommended best practice here (LaunchAgent EnvironmentVariables vs launchctl setenv vs other)?
Solution
Outline / runbook of what we did (and how to re‑debug fast):
- On Mac: port
- Who’s listening:
- Is it reachable:
0) What “good” looks like
- On VPS:nodes status --connectedbrowser,system- On Mac: port
187901) Prove what’s failing: tunnel vs token
Tunnel check (Mac):- Who’s listening:
- Is it reachable:
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,827Members
Resources
Was this page helpful?
