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.

1. 01reconWireGuard already installed?
2. 02reconinterface or wg0.conf already present? never overwrite them
3. 03recondefault route to preserve, and no overlap with the chosen VPN subnet
4. 04reconUDP port free?
5. 05reconactive firewall to open for the UDP port
6. 06recondistro and kernel (WireGuard module built in since 5.6)
7. 07actInstall WireGuardverify
8. 08actGenerate the server keysverify
9. 09actWrite /etc/wireguard/wg0.confverify
10. 10actOpen the UDP port (only if ufw or firewalld is active)verify
11. 11actEnable wg0destructiveverify
12. 12actCreate the first clientverify

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.

1. 01verifyInstall WireGuardVerified bywg --version && modprobe wireguard && echo ok
2. 02verifyGenerate the server keysVerified bystat -c %a /etc/wireguard/privatekey && test -s /etc/wireguard/publickey && echo ok
3. 03verifyWrite /etc/wireguard/wg0.confVerified bywg-quick strip wg0 >/dev/null && stat -c %a /etc/wireguard/wg0.conf
4. 04verifyOpen the UDP port (only if ufw or firewalld is active)Verified byufw status 2>/dev/null | grep -c "${port}/udp" || firewall-cmd --list-ports
5. 05verifyEnable wg0Verified bywg show wg0 listen-port && ip -4 route show default
6. 06verifyCreate the first clientVerified bywg show wg0 peers | grep -c "$(cat /etc/wireguard/clients/${client_name}.pub)" && test -s /etc/wireguard/clients/${client_name}.conf && echo ok

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

SEC.04

Variables

What you choose before launching — the recipe fills in the rest.

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.

SEC.06

Deploy on Servor button

Maintain WireGuard 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.

SEC.07

More networking recipes

1. 01TailscaleTailscale mesh VPN: auth key or login link, without touching the server DNS.
2. 02Pi-holePi-hole v6 (DNS + ad blocking) in a container, on the chosen IP. Destructive when listening on 0.0.0.0 (port 53).
3. 03AdGuard HomeAdGuard Home filtering DNS, local UI. Destructive: may free port 53.
4. 04OpenVPNOpenVPN server via the road-warrior script (angristan), first client created. Destructive: network.
5. 05DNS resolver (Unbound)Unbound validating (DNSSEC) recursive DNS resolver, on localhost.