SEC.01
The playbook
The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.
- 01reconTailscale already installed?
- 02recondaemon active? already connected to a tailnet (then verify and skip)?
- 03recon/dev/net/tun present (missing in some LXC containers)
- 04reconcurrent default route and resolver (must stay identical)
- 05recondistro and version
- 06actDownload the official installerverify
- 07actInstall Tailscaleverify
- 08actConnect (auth key if provided, otherwise login link)verify
SEC.02
What it verifies
Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.
- 01verifyDownload the official installerVerified by
head -1 /tmp/tailscale-install.sh - 02verifyInstall TailscaleVerified by
tailscale version | head -1 && systemctl is-active tailscaled - 03verifyConnect (auth key if provided, otherwise login link)Verified by
tailscale ip -4 && ip -4 route show default
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Never break the server connectivity: no change to the default route, /etc/resolv.conf or the rules that let the Servor agent and the SSH session out. Compare the default route and DNS resolution before/after. Never --exit-node, --accept-routes, --ssh or --reset without an explicit request; keep --accept-dns=false. Do not re-run tailscale up, nor tailscale down/logout, on a node already connected. The auth key is a secret: do not display it.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${authkey} | Auth key (tskey-…) |
SEC.05
How a recipe runs in Servor
Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.06
Deploy on Servor button
Maintain Tailscale or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.
Dark background
Light background[](https://servor.app/deploy/install-tailscale)SEC.07
More networking recipes
- 01WireGuardWireGuard VPN server + a first client, without touching routing. Destructive: network interface.
- 02Pi-holePi-hole v6 (DNS + ad blocking) in a container, on the chosen IP. Destructive when listening on 0.0.0.0 (port 53).
- 03AdGuard HomeAdGuard Home filtering DNS, local UI. Destructive: may free port 53.
- 04OpenVPNOpenVPN server via the road-warrior script (angristan), first client created. Destructive: network.
- 05DNS resolver (Unbound)Unbound validating (DNSSEC) recursive DNS resolver, on localhost.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.