A cron that runs Certbot is automation the way a sticky note is monitoring. It works until Cloudflare starts proxying the name, until someone closes port 80, until QA rebuilds the same hostname five times and Let’s Encrypt returns too many certificates already issued for exact set of domains.
SSL automation at more than one terminator is a pipeline: prove control, fetch a consistent full chain, install it everywhere that name terminates, reload, verify from outside, record the result, page on failure. Miss verify and you have “job green, users still warned.” Miss paging and you have cert-manager logging DNS-01 errors for 23 days while Saturday checkout dies.
This is how that pipeline is supposed to run inside enterprise SSL management. Stage vocabulary: certificate lifecycle management.
What “working Certbot” actually covers
On a single Nginx or Caddy box with a public A record and port 80 open, ACME is genuinely good. The Let’s Encrypt Community is full of people for whom that is the whole problem.
Enterprises add:
- A load balancer or CDN in front that is not the thing running the client
- Windows IIS (Certbot’s IIS story is weak; people use win-acme / Certify The Web and then hit cache vs rate-limit issues)
- Panel AutoSSL already “owning” some names
- Appliances that want a PFX pasted in a GUI
- Security teams that will not give an ACME identity write access to every DNS zone
An r/sysadmin write-up that made the rounds described ~700 mixed hosts, no outbound internet, HTTP-01 eaten by the LB, DNS-01 blocked because the provider had no per-zone ACL. Replies that only swapped ACME clients did not move the wall. Automation has to match how TLS is actually terminated—and which names even need a public CA.
The happy path, with the usual landmines
1. Enrollment and one owner per binding
Declare hostnames (and wildcards), ACME vs commercial, and targets: IIS sites, Nginx servers, panel accounts, appliances.
Policy worth writing down in one sentence: two ACME clients must not fight for the same binding. AutoSSL + win-acme overnight is not HA. It is flapping certificates and a mysterious “it fixed itself.”
2. Domain control
HTTP-01 — CA fetches a token under /.well-known/acme-challenge/ starting on port 80. Common breaks, all documented to death on community.letsencrypt.org:
- Origin redirects HTTP→HTTPS, but the HTTPS vhost does not serve the token (or Cloudflare Flexible SSL creates a redirect loop).
- Orange-cloud proxy: the CA talks to Cloudflare, not your Certbot webroot, unless you put the challenge on both 80 and 443 or switch to DNS-01.
- Wrong machine answering: DNS A/AAAA still on the old hoster after a move; win-acme 404s on an IP that is not yours.
DNS-01 — TXT at _acme-challenge. Required for wildcards. Breaks on leftover TXT, tokens that cannot delete, slow providers, and CNAME conflicts with CDN “verify this domain” records.
Details: HTTP-01 vs DNS-01. Wildcards: wildcard SSL automation.
Use staging ACME until the challenge is boring. Production rate limits are how people lock themselves out for a week after a bad IIS experiment.
3. Issuance and chain assembly
The CA returns a leaf. Automation must also grab the current intermediates. Leaf-only is still a top cause of “works on my Chrome, fails on Android / old Java.” See incomplete SSL certificate chain.
4. Deployment to every terminator
Multi-server SSL means the same generation on every node that terminates that name—or you accept regional “Not Secure” reports.
- Windows agents: store + IIS rebind (hash must change on the site binding).
- Linux: PEM/fullchain path + reload Nginx/Apache.
- Panels: connector, not a second local client.
- F5 / similar: import and attach to the Client SSL profile; GUI expiry updating is not the same as TMM serving the new object.
Hand-import PFX should be the exception for awkward appliances, not the weekly ritual.
5. Reload and verification (the step cron skips)
Reload without an external check is optimism. After deploy:
echo | openssl s_client -connect checkout.example.com:443 \
-servername checkout.example.com 2>/dev/null \
| openssl x509 -noout -dates -serial
Compare serial / fingerprint to what the job just installed. If origin is new and the load balancer still serves old material, this is how you find out before Twitter does.
Check the hostname customers type, with SNI, from outside the VPC. Internal synthetics that hit port 80 or an internal hostname are how teams stayed green for seven hours while checkout was red.
6. Schedule, retry, alert on the job
For ~90-day certs, starting renew around 30 days remaining is a common baseline (Let’s Encrypt’s own client does this). Tune for change freezes. Alerts belong on failed jobs and stuck pending orders, not only on calendar dates. Monitoring design: SSL certificate expiry monitoring for enterprises. Lifetime context: validity periods.
Quiet failures (forum greatest hits)
| Symptom | Likely break |
|---|---|
| Job green, users warned | Wrong terminator; CDN/LB stale; F5 profile cache |
| Challenge pending forever | HTTP-01/DNS-01 path; IPv6 ghost; Cloudflare |
| Renew works on one node | Farm not in scope |
| “Fixed after reboot” | Binding still on old store entry |
| Success in panel, fail in browser | Missing intermediate |
Fine in QA rebuilds, then rateLimited |
Duplicate certs; --force / cancel+reissue loops (win-acme GitHub issues) |
| Site up, iOS app “network error” | Pinning or HSTS; expiry is not “refresh the page” |
Already in the red interstitial? Restore first—expired certificate playbook—then fix the pipeline so the next cycle is boring.
Free ACME and commercial in the same factory
Automation does not require free certificates. Paid certificates do not remove automation. Many estates run Let’s Encrypt on bulk hostnames and commercial DV where procurement wants an invoice or an appliance vendor only documents their portal.
Same deploy/monitor loop either way: free vs paid SSL. Panel shortcuts still need central visibility: cPanel SSL automation, Plesk SSL automation, IIS Let’s Encrypt.
Scattered crons vs a control plane
Scattered crons scale with the number of people who remember they exist. A control plane is one retry button, one audit trail, and one answer to “what failed last night?” That is the practical meaning of centralized certificate management. Scale checklist: manage 100 SSL certificates centrally. Philosophy: manual vs centralized.
If a name never faces a browser, do not drag it through public ACME just because Certbot is free. Internal CA / private PKI is a different pipeline. Mixing the two in one binding is how corp laptops work and home networks do not.
How Certinite runs the loop
Certinite orchestrates enrollment, ACME or commercial issuance, deployment through agents and connectors, and renewal scheduling with job history you can paste into an incident review. Hub: enterprise SSL. Then create an account and automate one non-critical name—including a deliberate failed challenge in lab—so you know the alert fires before you migrate production.
FAQ
Is a working Certbot hook “enterprise automation”?
It can be excellent for one host. Enterprise usually means many hosts, mixed OS, shared visibility, and alerts that do not depend on someone reading mail from root@server17.
How early should renewals run?
Early enough to absorb challenge outages and a human DNS fix, without hammering rate limits. ~30 days remaining on a 90-day cert is a starting point, not a religion.
Do we still need humans?
For break-glass and policy exceptions, yes. For routine renew of known-good names, humans watch dashboards; they do not paste PEM.
What about internal-only certificates?
Same pipeline shape if you operate a private CA; challenge methods differ. Do not force Let’s Encrypt onto a RabbitMQ box that only exists on RFC1918—r/devops has the thread where someone pointed public DNS at a private IP to make HTTP-01 work. That is the wrong tool.
Closing
Enterprise SSL automation is challenge → issue → full-chain deploy → reload → verify → schedule → alert on failure. Cron is one gear. Build the rest, or shorter public lifetimes will schedule the next outage for you.