You need two tokens: a DigitalOcean personal access token with read and write scope,
and a Tailscale API access token.
Where the two tokens come from
- DigitalOcean — control panel → API → Tokens →
Generate New Token, with read and write scope. It starts with
dop_v1_ and is shown once.
- Tailscale — admin console → Settings → Keys →
Generate access token. It starts with
tskey-api-.
Paste them into Credentials as one line, separated by a space, in either order. Your
password manager then keeps both as a single ordinary login. They are sent only to
DigitalOcean and Tailscale, and nothing is stored on this site.
No accounts yet?
Making a node
Press New node, leave Exit node picked, and choose a datacenter — whichever country you want your
traffic to appear from. The dialog closes at once and the node appears in the table
straight away, reporting each step as it goes — requesting a key, provisioning,
joining tailnet. About a minute later it settles into an ordinary row: running, on your
tailnet, and ready to use. You can keep working while it builds, start another, or open
its row and cancel — which rolls the half-built node back.
What a row will tell you
Click any node (or press Enter) to open it. The panel underneath holds everything
the two APIs report about it: the droplet's image, kernel, size, features and every
address it has; the tailnet machine's client version, key expiry, advertised and approved
routes, relay and round-trip latency; and what it has cost so far. A node still building
opens on its build log instead.
Connecting a device to it
Install Tailscale on whatever you want protected and sign in to the same Tailscale
account the API token came from. Then pick the node:
- iPhone / iPad — App Store → Tailscale → sign in → the
three-dot menu → Exit Node → your node.
- Android — Google Play → Tailscale → sign in → the three-dot
menu → Exit Node.
- macOS / Windows — tailscale.com/download, sign in, then the menu bar or tray icon
→ Exit Node.
- Linux —
curl -fsSL https://tailscale.com/install.sh | sh, then
sudo tailscale up --exit-node=<node name>.
Check it worked: open ifconfig.me on that device. It should show the node's public IP
— the one in the table here — and not your own. To stop using it, set
Exit Node back to None, or on Linux run
sudo tailscale up --exit-node=.
What "New node" actually does
- Issues a single-use, ephemeral Tailscale auth key.
- Provisions a droplet in the datacenter you picked, which installs Tailscale on first
boot and joins your tailnet with that key.
- Approves its exit routes, then revokes the auth key.
If any step fails, the droplet and the key are deleted again, so a failed attempt leaves
nothing behind. Because the node is ephemeral, deleting the droplet also drops the machine
from your tailnet on its own.
A watch party: Jellyfin on a node
Pick Jellyfin watch party in New node and the node runs a private media server
as well. It needs a bigger droplet — two cores and 4 GB, usually $24 a month, so
a three-hour party costs about ten cents — and the picker prices every datacenter for
it. Setup takes a few minutes more than an exit node; open its row to follow it.
- Add a video. Drop it on the node's row, or paste a link to the file. It is converted
once, so every phone, laptop and TV plays it without the server straining.
- Open Jellyfin from the row and sign in as
admin with the password shown
there.
- Invite the family. Turn on Share with guests and send the invite it writes:
a link and a guest login that work from anywhere, no Tailscale needed.
- Watch together. Everyone opens the video; you press SyncPlay (the group icon
at the top of Jellyfin) and start a group, everyone else joins it, and play and pause stay
in step.
It needs this computer on your tailnet, with MagicDNS and HTTPS
certificates turned on (Tailscale admin console → DNS), since the row talks to
the node directly. Sharing uses Tailscale Funnel, which new tailnets allow for every
member. Your browser may ask once whether this page may reach devices on your local network:
allow it. Passwords are worked out from your DigitalOcean token, so they are never stored and
any browser signed in with that token shows the same ones. Everything on the node, videos
included, goes when the node is deleted.
What it costs, and cleaning up
Each node is the cheapest droplet its datacenter sells, and the picker shows what it costs
for a month left running — usually $4. You pay only while it exists:
billed by the second with a one cent minimum. Burning, under the logo, is what the
nodes running right now cost per hour, with what that comes to over a month if you left
them all on. Cost so far in the table is what each node has run up. Deleting a node
stops its billing immediately. Nothing else here costs anything.
When something looks wrong
- Stuck on "joining tailnet" — the node is still booting. It is normally
ready inside two minutes; open the row to watch the log, and if it never appears,
cancel it and create another.
- "DigitalOcean rejected that token" — the token is wrong, expired, or lacks
write scope.
- "Tailscale relay unreachable" — droplet data still loads, but the tailnet
columns stay blank. Usually a network problem between you and this site.
- "route not approved" — the node joined but its exit routes were not
approved. Approve it in the Tailscale admin console under Machines, or delete the
node and create another.
- The node is listed but traffic still leaves from your own IP — the device
has Tailscale running but no exit node selected, or it is set to a different one.