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. 01recondistro and version: apt (Debian/Ubuntu) or dnf (RHEL/Fedora/Rocky/Alma)?
2. 02reconDocker Engine + compose plugin present? (otherwise the docker step installs them)
3. 03reconNginx Proxy Manager already deployed (/opt/npm, compose.yaml or docker-compose.yml)?
4. 04reconis port 80 already taken (by which process)?
5. 05reconis port 443 already taken (by which process)?
6. 06reconis port 81 already taken (by which process)? (admin UI, bound to 127.0.0.1)
7. 07reconis a firewall (ufw or firewalld) active?
8. 08actInstall Docker Engine (only if missing)verify
9. 09actWrite /opt/npm/compose.yamlverify
10. 10actStartverify
11. 11actOpen 80/443 (only if a firewall is active)verify
12. 12actThe admin UI 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. 01verifyInstall Docker Engine (only if missing)Verified bydocker compose version && systemctl is-active docker
2. 02verifyWrite /opt/npm/compose.yamlVerified bydocker compose -f /opt/npm/compose.yaml config -q && echo ok
3. 03verifyStartVerified bydocker compose -f /opt/npm/compose.yaml ps --status running -q | wc -l
4. 04verifyOpen 80/443 (only if a firewall is active)Verified byufw status 2>/dev/null | grep -E "^(80|443)/tcp"; firewall-cmd --list-services 2>/dev/null; true
5. 05verifyThe admin UI respondsVerified bycurl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:81/

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 Nginx Proxy Manager 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 web server recipes

1. 01nginxnginx web server, started, enabled at boot and verified.
2. 02CaddyCaddy with automatic HTTPS for a domain.
3. 03Apache httpdApache web server, started, enabled and verified.
4. 04HAProxyHAProxy load balancer, started and verified.
5. 05TraefikTraefik reverse proxy via Docker, with the dashboard and automatic TLS.