MSK · UTC+3 · 18 Nov 2026note

← all notes

Certificate renewals fail silently

tls8 Nov 2026 · 4 min read

Let's Encrypt certificates last 90 days, and every automation around them assumes the renewal works. The failure mode is quiet: one host renews, another does not, and nothing in the world tells you until a client refuses to connect.

The host nobody watched

A customer had 19 hosts with certificates. Eighteen renewed through a cron job with a log nobody read. The nineteenth was a mail gateway that “never changes”, so its renewal was written by hand when the host was built, three years earlier, with a webroot path that had since been removed.

The certificate expired on a Saturday. On Monday, scan-to-email on the office printer stopped working — which is how the ticket arrived, as “the printer is broken”.

renewal due expiry on Saturday issued
Renewal was due on day 60. It failed. The certificate died on day 90, and nobody noticed until the printer complained.

What we changed

The lesson was not “monitor more”. It was “the boring host is the one that will fail, so make every host print the same line”.