How to Reach the OpenClaw Dashboard Remotely Without Port Forwarding

Keep the gateway bound safely, then use an SSH tunnel or Tailscale-style access instead of exposing the control UI directly to the public internet.

The video topic is remote dashboard access, but the safest written version is not 'make the control UI public'. Keep the gateway on loopback or a private tailnet and bring your browser to it with a tunnel.

Quick answer

Do not publish the dashboard port directly. Keep the gateway local, print the dashboard link on the host, and use SSH tunneling or Tailscale to reach it from outside.

Command line steps

1. Confirm the gateway is running locally

Start from a healthy local gateway before you layer on any remote access method.

2. Use SSH port forwarding instead of opening the port

This keeps the OpenClaw gateway private and only forwards it into your local browser session.

3. If you already use Tailscale, keep access on the tailnet

A tailnet is safer than raw port forwarding because the gateway is not exposed as an open public service.

What to check if it still fails

• If you see pairing or auth issues, regenerate the dashboard URL with openclaw dashboard --no-open on the host itself.
• If you changed bind settings earlier, inspect them with openclaw config get gateway.bind and avoid lan unless you have a reason.
• If remote access is failing, debug the gateway first with openclaw gateway status --require-rpc and openclaw logs --follow.