The certificate has already expired
Visitors see a full-page browser warning and most of them leave. The renewal job stopped running at some point and nobody noticed until today.
Valid certificate back within the hour
Certificate expired?
An expired certificate takes the whole site offline for anyone using a modern browser, and the warning page scares off customers within seconds. We get a valid certificate back on the server first, then find out why the automatic renewal stopped working.
What it is
Let's Encrypt is a free, automated certificate authority run by the non-profit Internet Security Research Group (ISRG), launched in public beta in 2015. It issues domain-validated TLS certificates valid for 90 days, using the ACME protocol so that issuance and renewal can both happen without a person pressing any buttons.
Clients that talk to it include certbot, acme.sh, lego, Caddy (which does it automatically), traefik, cPanel AutoSSL, nginx-proxy and Kubernetes cert-manager. The certificates it issues are trusted by every mainstream browser, so a correctly configured site looks identical to one using a paid certificate.
The honest version
No technology is all upside. This is where SSL certificates (Let's Encrypt) earns its place and where it tends to cause trouble.
Sound familiar?
The SSL certificates (Let's Encrypt) problems that bring people to us, and what you have once each one is fixed.
Visitors see a full-page browser warning and most of them leave. The renewal job stopped running at some point and nobody noticed until today.
Valid certificate back within the hour
The timer still runs, but every attempt errors out. Usually a changed DNS record, a path rewrite in nginx, or a plugin that blocks the well-known directory.
Renewal runs clean on a schedule
A proxy, a redirect to https, or a firewall rule gets in the way of the acme-challenge request before it arrives.
Challenge path left open and tested
Dozens of retries during a panic have tripped the weekly limit for the registered domain, so new attempts are refused for days.
Routed around the limit, then issued cleanly
Wildcard certificates cannot be issued through http-01 at all. The DNS provider needs an API token and the client needs to be taught how to use it.
Wildcard issued through DNS-01
Browsers look fine, but older devices, mail clients or monitoring tools reject the connection because the server is sending only the leaf certificate.
Full chain served, every client happy
After a server migration or an OS upgrade, the certbot timer was never re-enabled. Nothing is renewing anything.
Timer active, first renewal verified
What we do
Call us for an urgent expiry, or hand us every certificate you run.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Stop retrying blindly, because every failed attempt eats into the weekly rate limit. Get in touch and we will issue a fresh certificate, install it, and only then look at why the renewal stopped. In most cases the site is loading cleanly again within the hour.
The common causes are a changed DNS or hosting configuration that blocks the http-01 challenge, a Cloudflare proxy setting that intercepts the challenge request, a disabled certbot timer after a server upgrade, or a well-known path that a plugin or redirect now swallows. The log usually makes the reason obvious once someone reads it.
Yes. Wildcard certificates need the DNS-01 challenge, which means the client has to be able to add a temporary record through your DNS provider's API. We set that up with a scoped token so nothing else on the server can touch your DNS.
Yes. They provide the same encryption and are trusted by the same browsers as any paid domain-validated certificate. The only reason to buy one is if you specifically need organisation-validated or extended-validation, which Let's Encrypt does not offer.
Either the certificate has expired, it does not cover the exact hostname being visited (for instance www versus bare domain), or the server is not sending the full chain. All three are quick to diagnose from the browser and the server logs together.
Estimates are free. Tell us the domain and what the browser is showing, and you get a price before any work begins.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: