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. 02reconnginx present? which version?
3. 03recondoes a vhost for this domain already exist (where)? do not overwrite it
4. 04recondoes the upstream respond? (000 = nothing listening)
5. 05reconSELinux Enforcing? (RHEL: httpd_can_network_connect required)
6. 06reconis a firewall (ufw or firewalld) active?
7. 07actInstall nginx (if missing)verify
8. 08actWrite the vhostverify
9. 09actEnable the vhostverify
10. 10actReloadverify
11. 11actOpen 80/443 (only if a firewall is active)verify
12. 12actThe proxy 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 nginx (if missing)Verified bynginx -v 2>&1
2. 02verifyWrite the vhostVerified bytest -f /etc/nginx/sites-available/${domain} -o -f /etc/nginx/conf.d/${domain}.conf && echo ok
3. 03verifyEnable the vhostVerified bynginx -t 2>&1 | tail -1
4. 04verifyReloadVerified bysystemctl is-active nginx
5. 05verifyOpen 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
6. 06verifyThe proxy respondsVerified bycurl -s -o /dev/null -w '%{http_code}' -H 'Host: ${domain}' http://127.0.0.1/

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 nginx reverse proxy 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 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.