certbot
NetworkPackage: certbot
Obtains and renews Let's Encrypt certificates by proving control of the domain, and installs a timer for renewal. certbot renew --dry-run rehearses the procedure without issuing anything.
What its options do in the lessons
From the same glossary the lessons render under their commands, so the two cannot disagree.
certbot --deploy-hook- A command to run after each successful renewal of that certificate, never after a failure. It is saved into the renewal configuration file and so applies to every later renewal: it is how a
certonlyissuance gets nginx reloaded. certbot --run-deploy-hooks- Runs the deploy hooks during a
--dry-runafter all, once the simulation has succeeded. Without it, a rehearsal says nothing about your reload. certbot -d- A domain name to include in the certificate, repeated once per name. Each is validated separately, so one failing name fails the whole certificate.
certbot --nginx- Uses the Nginx plugin: certbot edits the configuration and reloads the server itself.
certbot --dry-run- Rehearses the whole renewal against the staging server: no certificate issued, no rate limit consumed. The only honest way to check renewal will work.