←back to thread

LetsEncrypt – Expiration Notification Service Has Ended

(letsencrypt.org)
181 points zdw | 1 comments | 30 Jun 25 04:49 UTC | HN request time: 0.38s | source
Show context
leakycap ◴[30 Jun 25 04:52 UTC] No.44419518[source]▶
One could say it expired.

> Providing expiration notifications costs Let’s Encrypt tens of thousands of dollars per year, money that we believe can be better spent on other aspects of our infrastructure.

Appreciate the honesty (they had other reasons, too! but emails are a pain and expensive at their scale)

replies(2): >>44420397 #>>44420498 #
amenghra ◴[30 Jun 25 07:16 UTC] No.44420397[source]▶
They should just build a mobile app for the purpose of receiving these notifications. Make the app $2.99. Turn the expense into a profit. /s
replies(4): >>44420462 #>>44420493 #>>44420842 #>>44421074 #
bayindirh ◴[30 Jun 25 09:08 UTC] No.44421074[source]▶
As an other option, you install a cron job on your server, and send push notifications via pushover or ntfy.sh whenever it fails to renew.

Pushover is $5 once for personal use, ntfy.sh can be completely self-hostable if you prefer.

I have written a small tool which utilizes pushover for these reasons.

You can receive the notifications on your browser/mobile for free afterwards.

replies(1): >>44421222 #
0x073 ◴[30 Jun 25 09:30 UTC] No.44421222[source]▶
Or just a cronjob that fetches the tls certs and look at the expiration date and then send a mail or X.

So it's even work if you don't have control about the le client.

replies(2): >>44421360 #>>44421949 #
1. unilynx ◴[30 Jun 25 09:55 UTC] No.44421360[source]▶
Exactly this. Don't look at the renewal proces, look at its output. It'll work for all certificate sources and catch other potential errors too (eg the webserver reporting success but not presenting the new certificate)