Unable to connect Mac node to remote gateway
✅Solved
I'm trying to connect to my remote gateway as a node on my mac, through the macos menu bar companion app. Tailscale was configured independently. I am able to ssh into the vps through ssh.
Details:
Remote gateway
$ openclaw --version
2026.3.2
Local:
$openclaw status
Dashboard: http://127.0.0.1:18789/
OS: macos 26.3 (arm64) · node 25.6.1
Tailscale: off
Channel: stable (default)
Update: pnpm · npm latest 2026.3.2
Gateway: remote · wss://100.94.254.65:18789 (config gateway.remote.url) · unreachable (connect failed: connect ECONNREFUSED 100.94.254.65:18789)
Gateway service: LaunchAgent installed · not loaded · unknown
Node service: LaunchAgent not installed
Agents: 1 · no bootstrap files · sessions 2 · default main active 23h ago
...
- Tailscale set up independently, but tailscale automation not enabled.
- Hostinger firewall accepts udp from 41641
- No pending devices to approve on remote.
- Removing optional port on ssh string on macos app stuck on testing (maybe because the key is passphrase protected?)
Details:
Remote gateway
$ openclaw --version
2026.3.2
Local:
$openclaw status
Dashboard: http://127.0.0.1:18789/
OS: macos 26.3 (arm64) · node 25.6.1
Tailscale: off
Channel: stable (default)
Update: pnpm · npm latest 2026.3.2
Gateway: remote · wss://100.94.254.65:18789 (config gateway.remote.url) · unreachable (connect failed: connect ECONNREFUSED 100.94.254.65:18789)
Gateway service: LaunchAgent installed · not loaded · unknown
Node service: LaunchAgent not installed
Agents: 1 · no bootstrap files · sessions 2 · default main active 23h ago
...
- Tailscale set up independently, but tailscale automation not enabled.
- Hostinger firewall accepts udp from 41641
- No pending devices to approve on remote.
- Removing optional port on ssh string on macos app stuck on testing (maybe because the key is passphrase protected?)
Solution
2) Put that token into the macOS app (Remote over SSH setup)
In the macOS app settings for the remote gateway connection, enter that value in the field that’s usually labeled Gateway Token / Auth token (not the SSH key/passphrase).If you don’t see a token field in the SSH settings, another reliable way to confirm you have the right token is:
- keep your tunnel active
- open
http://127.0.0.1:18789/- in the Control UI, paste the token in Gateway Access and connect
(If the browser connects with that token, the app will too — it’s the same gateway auth.)
3) If you previously rotated tokens
Make sure you didn’t accidentally set a different token on the Mac side (e.g. ingateway.remote.token- VPS:
gateway.auth.token- Clients (mac app / Control UI / remote CLI): must use that exact token
If you tell me whether
openclaw config get gateway.auth.token
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Was this page helpful?
