Gateway token mismatch port forwarding w/ VPS SSH and Docker
✅Solved
Can't access my local node via gateway token
Solution
Summary of what fixed the original “can’t access my local node via gateway token” issue (VPS + Docker + port-forwarding):
- Made the Gateway private (no internet exposure):
- Bound Docker-published ports 18789/18790 to the VPS Tailscale IP only (not
- Enabled Tailscale Serve to get an HTTPS Control UI URL on the tailnet:
- Removed public SSH by deleting UFW
- Fixed Control UI / token issues:
- “Token mismatch” was resolved by regenerating a fresh dashboard URL (
- Added
- Ensured the gateway auth token was set (stored in
- Fixed “can’t reach the local/Mac node” portion:
- Approved the pending device pairing request on the gateway (
- Reinstalled the Mac node host to connect via TLS through Tailscale Serve:
-
- then
- Made the Gateway private (no internet exposure):
- Bound Docker-published ports 18789/18790 to the VPS Tailscale IP only (not
0.0.0.0- Enabled Tailscale Serve to get an HTTPS Control UI URL on the tailnet:
https://<magicdns>.ts.net/- Removed public SSH by deleting UFW
22/tcp- Fixed Control UI / token issues:
- “Token mismatch” was resolved by regenerating a fresh dashboard URL (
openclaw dashboard --no-open- Added
gateway.controlUi.allowedOriginshttps://<magicdns>.ts.net- Ensured the gateway auth token was set (stored in
.env- Fixed “can’t reach the local/Mac node” portion:
- Approved the pending device pairing request on the gateway (
openclaw devices approve <requestId>- Reinstalled the Mac node host to connect via TLS through Tailscale Serve:
-
openclaw node install --host <magicdns>.ts.net --port 443 --tls --force- then
openclaw node restart
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
Recent Announcements
Similar Threads
Was this page helpful?
