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. 01reconAdGuard Home already installed? (then verify and skip)
2. 02reconwho holds port 53 (systemd-resolved?) and port 3000
3. 03reconcurrent server resolver (must keep working)
4. 04reconarchitecture (amd64, arm64, armv7…)
5. 05actDownload AdGuard Homeverify
6. 06actInstall into /opt/AdGuardHomeverify
7. 07actFree port 53 (only if systemd-resolved holds it)destructiveverify
8. 08actInstall the serviceverify
9. 09actThe setup wizard respondsverify

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. 01verifyDownload AdGuard HomeVerified bytar -tzf /tmp/AdGuardHome.tar.gz | grep -c 'AdGuardHome/AdGuardHome$'
2. 02verifyInstall into /opt/AdGuardHomeVerified by/opt/AdGuardHome/AdGuardHome --version
3. 03verifyFree port 53 (only if systemd-resolved holds it)Verified bygetent ahosts static.adtidy.org | head -1
4. 04verifyInstall the serviceVerified bysystemctl is-active AdGuardHome
5. 05verifyThe setup wizard respondsVerified bycurl -sL -o /dev/null -w '%{http_code}' http://127.0.0.1:3000/

SEC.03

Guardrails

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

SEC.04

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.05

Deploy on Servor button

Maintain AdGuard Home 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.06

More networking recipes

1. 01TailscaleTailscale mesh VPN: auth key or login link, without touching the server DNS.
2. 02WireGuardWireGuard VPN server + a first client, without touching routing. Destructive: network interface.
3. 03Pi-holePi-hole v6 (DNS + ad blocking) in a container, on the chosen IP. Destructive when listening on 0.0.0.0 (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.