Reach your dashboard

Just Dashboard 0.8.4 is a root-equivalent control panel. Keep it on your tailnet or behind an SSH tunnel. The installer configures one of these paths and prints the exact URL and port at the end.

TailscaleCopy Anchor Link

Tailscale is the installer's default. It connects the server to your tailnet (installing Tailscale first if you agree), binds the proxy to the server's tailnet address, and allows tailnet and loopback addresses through the API perimeter. If the machine still is not on a tailnet after that step, the installer falls back to an SSH tunnel and says so. Open the address printed by the installer from a device on the same tailnet, usually:

https://your-box.tailnet-name.ts.net:8443

With HTTPS enabled for the tailnet and a MagicDNS name, the installer requests a trusted certificate using tailscale cert; Just Dashboard renews it. If the tailnet has no MagicDNS name or certificate issuance fails, the panel still runs with Caddy's internal certificate, and the browser shows a certificate warning. You can enable tailnet HTTPS and change the certificate mode later under Settings → Configuration.

SSH tunnelCopy Anchor Link

Choose this when you want access only while an SSH connection is open. The tunnel installation serves plain HTTP on the server's loopback interface. From your laptop or other client device, run the command printed by the installer. With the usual port, it looks like:

ssh -N -L 8443:localhost:8443 you@your-server

Leave that command running and open http://localhost:8443 on the client device. The SSH connection carries the traffic. If the installer chose another port, replace both 8443 values and use its printed URL.

The installer also prints a tunnel command as a fallback for Tailscale installations. A Tailscale installation usually uses HTTPS, so its localhost fallback may show a certificate-name warning; the certificate belongs to the MagicDNS name.

A server linked to your just-dashboard.com account shows this command, with its own port, user and host, on its page under Servers, and a Tailscale install shows its tailnet address there too. The site only shows the way in; it never carries the traffic.

Change an existing installationCopy Anchor Link

An administrator can edit the address, port, certificate mode, allowlist, and two-factor policy under Settings → Configuration. The page checks the new configuration and rolls back automatically if the restarted stack does not come up. Keep 127.0.0.1/32 and ::1/128 in JD_ALLOWED_CIDRS so a tunnel remains a recovery path.

The API checks JD_ALLOWED_CIDRS before login. If your browser cannot reach the sign-in page at all, inspect the private network connection, the printed port, and that allowlist. From the cloned directory on the server, sudo ./scripts/manage.sh status shows the containers and their health, and sudo ./scripts/manage.sh restart recreates the stack after you edit .env by hand; run it over SSH, because the web terminal disconnects. See troubleshooting for more.