stummel.example was down for 47 minutes
The certificate expired at 06:00. Renewal had failed for three weeks, and the warning mails went to a folder I never open.
- Status
- Resolved
- Severity
- Major
- Started
- Resolved
- Duration
Every short link answered with a certificate error for 47 minutes on Wednesday morning. The certificate expired at 06:00 CEST. Its renewal had failed every night for three weeks, and each failure sent a mail that a filter of mine moved into a folder I never open.
Timeline
- 2026-10-21 06:00 CEST The certificate for stummel.example expires.
- 06:31 Investigating: Pegel reports the TLS check failing. The page wakes me.
- 06:38 Identified: Renewal fails because port 80 is closed since the firewall change on 2026-09-29.
- 06:44 Port 80 open again for the ACME challenge only.
- 06:47 Monitoring: New certificate issued, links answer again.
- 06:47 Resolved: Every check green for 30 minutes.
What went wrong
I closed port 80 when I moved the server, because stummel only serves HTTPS. The HTTP-01 challenge needs port 80. Renewal failed quietly for 21 nights.
What changed
- Port 80 answers the challenge path and redirects everything else.
- Renewal errors go to the pager, not to mail.
- Pegel checks the certificate’s expiry date and warns at 14 days.
subscribe
New entries and the next chapter by mail, nothing else.