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. 02reconCertbot already present (package or snap)?
3. 03recondoes a certificate already exist for this domain? when does it expire?
4. 04reconis the chosen web server running? (required by the certbot plugin)
5. 05recondoes the domain point to this server’s public IP?
6. 06reconis a firewall (ufw or firewalld) active?
7. 07actInstall Certbot + ${webserver} pluginverify
8. 08actIssue the certificateverify
9. 09actAutomatic renewalverify
10. 10actHTTPS 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 Certbot + ${webserver} pluginVerified bycertbot --version
2. 02verifyIssue the certificateVerified bycertbot certificates -d ${domain} 2>/dev/null | grep -c "VALID"
3. 03verifyAutomatic renewalVerified bysystemctl list-timers --all 2>/dev/null | grep -c certbot
4. 04verifyHTTPS respondsVerified bycurl -s -o /dev/null -w '%{http_code}' https://${domain}/

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 Let's Encrypt certificate 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.