Guide

Access OpenClaw Dashboard Remotely

OpenClaw's Dashboard runs on localhost by default. Here are 4 ways to access it from any device, anywhere.

Quick Answer

Access OpenClaw remotely with ClawSquire (automatic SSH tunnel), manual SSH tunnel (ssh -NL 18789:localhost:18789 user@server), or Tailscale VPN.

Recommended

ClawSquire — Easiest Remote Access

ClawSquire is the simplest way to access OpenClaw remotely. Add your VPS, click Connect, and you're done. No manual SSH commands, no port numbers to remember — ClawSquire creates the SSH tunnel automatically and opens the Dashboard in a secure local window.

VPS Manager — Add Server, Click Connect

Enter your server host, SSH user, and password. One click connects you to the remote OpenClaw Dashboard.

ClawSquire VPS Manager showing remote server connection form with host field, SSH port 22, username, password authentication, and green Connect button for automatic SSH tunnel to OpenClaw Dashboard
Dashboard in Remote Mode

Once connected, manage OpenClaw on your VPS — config, channels, health check — all from your laptop.

ClawSquire Dashboard in Remote Mode connected to OpenClaw on a VPS showing OpenClaw Dashboard button, Safety Level, Quick Actions for setup and health check
Channels — Configure Telegram, DeepSeek

Add and manage messaging channels and LLM providers from the visual interface.

ClawSquire Channels page showing Telegram channel with Configured badge, DeepSeek provider, and Add Channel button for OpenClaw messaging setup

Other Methods

Manual Alternative

1

SSH Tunnel (Simplest)

ssh -L 18789:localhost:18789 user@your-server-ip

Then open http://localhost:18789 in your browser. Works immediately, no config needed. Closes when SSH session ends.

For persistent tunnels:

ssh -fN -L 18789:localhost:18789 user@your-server-ip
2

Tailscale (Zero Config VPN)

  • Install Tailscale on both your computer and the server
  • Both devices join your Tailscale network
  • Access via http://your-server-tailscale-ip:18789
  • Always encrypted, works across NAT, no port forwarding
3

Reverse Proxy with HTTPS (Production)

Caddy example:

openclaw.yourdomain.com {
  reverse_proxy localhost:18789
}

Nginx example with Let's Encrypt:

server {
  listen 443 ssl;
  server_name openclaw.yourdomain.com;
  ssl_certificate /etc/letsencrypt/live/...;
  location / {
    proxy_pass http://localhost:18789;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
  }
}

Requires domain name and DNS setup. WebSocket upgrade headers are critical for the Dashboard to work.

Comparison

Method
Setup Time
Always On
Needs Domain
Best For
SSH Tunnel
1 min
No
No
Quick access
Tailscale
10 min
Yes
No
Personal use
HTTPS Proxy
30 min
Yes
Yes
Production/team
ClawSquire
2 min
On demand
No
Desktop users

Troubleshooting

Dashboard loads but shows 'Disconnected'+
WebSocket not proxied — add Upgrade headers to your reverse proxy. See the Nginx example above.
Connection refused+
Check the gateway is running on the server: openclaw gateway status
Device identity error+

Next Steps

Download ClawSquire — Free

Guided setup, health diagnostics, 7 languages.