Tailscale
Tailscale is the recommended way to reach a machine’s dashboard from your other devices. It puts your machines and phone on one private network (a tailnet), gives each machine a name such asdesk.tailnet-1234.ts.net (its MagicDNS name), and can serve the dashboard
over HTTPS at that name with Tailscale Serve.
Overdeck sets this up for you in Settings → Anywhere → Set up Tailscale, also in the
command palette, or in a terminal with pan tailscale setup. Both walk
the same steps. Set up Tailscale appears only in a browser on this machine (the root
session); a paired device cannot change Tailscale settings.
Overdeck keeps no copy of Tailscale’s state. The only things setup saves are
Require a token to sign in and the trusted address https://<MagicDNS name>. Every
step reads the live state from the tailscale command, so you can also make any change by
hand and Overdeck picks it up.
Set up Tailscale is new. Its guided steps were not run end to end on a real machine
before release. If a step does not work for you, report it on
GitHub Issues.
What Set up Tailscale does
Setup reads Tailscale’s state and shows the first step that is not done yet:
Any command that may need an administrator password runs in a terminal inside
the dialog (or in your own terminal for
pan tailscale setup). You type the
password there. Overdeck never asks for it, sees it or stores it.
If the sign-in attempt says access is denied, this user is not the Tailscale
operator. The dashboard then shows the operator step with a Try signing in again
button; pan tailscale setup runs the operator command and retries sign-in once by
itself.
Per platform
If your user name contains characters that are unsafe in a shell command,
Overdeck shows the Linux installer command and the operator step as text
instead of running them.
Userspace mode
Overdeck can also install Tailscale for one Linux user with no administrator password: it downloads the official static tarball, checks its published SHA-256 checksum, and runstailscaled --tun=userspace-networking under a
systemd user service, overdeck-tailscaled.service. The files live under
~/.overdeck/tailscale/:
When that
bin/tailscale exists, Overdeck uses it in preference to any other
tailscale on the machine. A systemd user service stops when you log out
unless lingering is on for your user (loginctl enable-linger); Overdeck does
not turn lingering on.
Serve HTTPS and token sign-in
Turn on HTTPS access runs, in this order:- It turns on Require a token to sign in (
dashboard.require_token_mint). - It trusts
https://<MagicDNS name>as an address of this dashboard. - It runs
tailscale serve --bg --https=443 http://127.0.0.1:<port>. Tailscale gets an HTTPS certificate for the MagicDNS name and forwards to the dashboard.--bgkeeps the setting in Tailscale, so it survives restarts of Tailscale and of Overdeck. - It checks that
https://<MagicDNS name>/api/environmentanswers with this machine’s identity. The first request can take a few seconds while Tailscale gets the certificate.
127.0.0.1, so without that setting every
visitor on your tailnet would look like a local caller and could open the
dashboard. A browser that already has a session keeps working. Every new
browser, including one at the Serve address, must pair: run
pan pair --url https://<MagicDNS name> or use Pair a device. If a later
step fails, token sign-in stays on.
While Serve forwards to this dashboard, Overdeck keeps Require a token to sign
in on: a Settings save that turns it off keeps it on and logs a warning. To
turn token sign-in off, turn Serve off first with
tailscale serve --https=443 off.
If Serve was turned on by hand while token sign-in was off, the Anywhere
status card shows “Tailscale Serve sends tailnet visitors to this dashboard, but
a token is not required to sign in” with a Protect the dashboard button.
Overdeck never turns Serve off and never replaces another Serve handler. It
refuses to continue when port 443 already serves something else, or when
Tailscale Funnel publishes port 443 on the public internet. tailscale serve status shows what is there.
Serve needs Tailscale 1.52 or later.
Funnel on port 8443
Overdeck never publishes the dashboard with Funnel. Two opt-in features use Funnel on port 8443 for single paths, and Overdeck prints the commands instead of running them: webhook triggers mount/hooks,
and Public MCP mounts /mcp,
/.well-known and /oauth so a hosted bot such as Grok Bot can sign in.
Tailnet settings
Serve HTTPS needs two tailnet-wide settings, which only the tailnet’s admin can change: MagicDNS and HTTPS certificates. Turn both on at login.tailscale.com/admin/dns, then press Check again. If Serve itself is not enabled for the tailnet, Tailscale prints a link to enable it, and Overdeck shows that link.The phone app
When setup is ready, it shows a QR code for tailscale.com/download. Install Tailscale on your phone and sign in with the same account shown under the code. Then press Pair a device to pair the phone’s browser with this dashboard.Discovering other machines
When Tailscale is ready, Settings → Anywhere lists Overdeck on your tailnet: the other online tailnet machines whose dashboard answers. For each online peer, Overdeck askshttps://<peer MagicDNS name>/api/environment and
http://<peer tailnet address>:<this dashboard's port>/api/environment at the
same time, 2.5 seconds each, and lists the peer when either answers with an
Overdeck identity. It shows each machine’s label, host name, Overdeck version
and address, and counts the other tailnet devices. The list loads when the page
opens and on Refresh. pan tailscale status prints the same list.
The list has no Link action. To link one of these machines, use Link a machine in
Settings → Anywhere or pan machines link <pairing-url>; see
Linked machines.