Certificate expired?

SSL expired or renewal broken? We fix it today.

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.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

letsencrypt.log

still failing

What it is

SSL certificates (Let's Encrypt) at a glance

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.

Type
Free, automated TLS certificate authority
First released
2015 public beta
License
Free for domain-validated certificates
Maintained by
Internet Security Research Group (ISRG)
Typically used for
Websites, APIs, mail servers, internal services, anything that needs TLS

The honest version

SSL certificates (Let's Encrypt) pros and cons

No technology is all upside. This is where SSL certificates (Let's Encrypt) earns its place and where it tends to cause trouble.

Where SSL certificates (Let's Encrypt) is strong

  • Free, and trusted everywhereNo licence fee, and the certificates are accepted by every mainstream browser out of the box. There is no reason to pay for a basic domain-validated certificate any more.
  • Automated issuance and renewalTools like certbot, acme.sh and cPanel AutoSSL handle the whole process. Caddy and traefik go further and do it by themselves with no configuration at all.
  • Wildcard certificates are supportedA single certificate can cover every subdomain of a domain, issued through the DNS-01 challenge against your DNS provider's API.
  • Short 90-day lifetimeA certificate only lives for 90 days, which keeps private keys fresh and forces whatever renews them to actually work. Problems surface in weeks, not years.
  • Automation is the defaultThe whole ecosystem is built around scripts and timers, so there is strong encouragement to set things up once and stop touching them.

Where SSL certificates (Let's Encrypt) bites

  • Something must renew automatically, and it must workThe 90-day lifetime is only a virtue when the renewal job runs on its own. A broken cron or a dead systemd timer is the single most common cause of an expired certificate.
  • Rate limits bite during recoveryA registered domain is limited to 50 certificates per week. Repeated failed attempts during a panic can lock you out of issuing new ones for days.
  • The http-01 challenge is fragileIf the site sits behind basic auth, a staging password, or a Cloudflare proxy configured awkwardly, the challenge request never reaches the server and issuance fails.
  • Needs an open port 80The standard http challenge needs inbound port 80 reachable from the internet. Firewalls that block it entirely need DNS-01 instead.
  • No OV or EV certificatesOnly domain-validated certificates are issued. If you need the organisation name baked into the certificate itself, you still have to buy that from a commercial authority.

Sound familiar?

Common SSL certificates (Let's Encrypt) problems we fix

The SSL certificates (Let's Encrypt) problems that bring people to us, and what you have once each one is fixed.

Your connection is not private

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

renew: certificate renewal failed

Auto-renewal has been failing quietly

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

Failed authorization procedure (http-01)

The http challenge never reaches the server

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

too many certificates already issued

Rate limited after too many failed attempts

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 cert requires DNS-01

Needs a wildcard but only http-01 is set up

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

cert chain does not include intermediate

Some clients refuse the certificate

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

systemctl status certbot.timer: inactive

The renewal timer is simply not running

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

SSL certificate help, from rescue to upkeep

Call us for an urgent expiry, or hand us every certificate you run.

Emergency rescue
Expired right now. We get a valid certificate installed and the site loading cleanly again, usually within the hour.
Renewal repair
Find out why the automatic renewal stopped, fix the underlying cause, and prove it with a forced run.
Wildcard and DNS-01 setup
Wildcards issued through your DNS provider's API, with credentials kept out of the web server.
Proxy and load balancer work
Certificates in front of Cloudflare, nginx, Apache, traefik or a Kubernetes ingress, configured so the chain is complete and renewal keeps working.
Monitoring
Alerts that fire weeks before expiry, not after, so a broken renewal is caught before customers see it.
Managed Tech
Certificates, renewals and the servers behind them, looked after on an ongoing basis.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running SSL certificates (Let's Encrypt) alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

SSL certificates (Let's Encrypt) questions

Something else? Call+1 737 727 7327

My SSL certificate expired, what do I do right now?

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.

Why is the Let's Encrypt auto-renewal failing?

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.

Can you set up a wildcard SSL certificate for us?

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.

Are Let's Encrypt certificates safe for a commercial website?

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.

Why do visitors see 'your connection is not private' on my site?

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.

How much does SSL certificate help cost?

Estimates are free. Tell us the domain and what the browser is showing, and you get a price before any work begins.

Free estimate

Certificate expired or renewal broken?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.