Ending Support for Expiration Notification Emails
letsencrypt.org
Since its inception, Let’s Encrypt has been sending expiration notification emails to subscribers that have provided an email address to us. We will be ending this service on June 4, 2025. The decision to end this service is the result of the following factors: Over the past 10 years more and more of our subscribers have been able to put reliable automation into place for certificate renewal. Providing expiration notification emails means that we have to retain millions of email addresses connected to issuance records.

I think it’s a good idea, everyone should be automating this anyway.

  • themoonisacheeseEnglish
    191·
    14 hours ago

    Pretty much all monitoring solutions on the market track cert expiration nowadays. I get an alert when any of my certs have <5 days left

    • a_fancy_kiwi@lemmy.worldEnglish
      3·
      12 hours ago

      What monitoring solution do you use? I need to set something up for my own projects but haven’t gotten around to it. Any experience with Nagios?

      • justcallmelarry@lemmy.dbzer0.comEnglish
        2·
        7 hours ago

        I set up uptime kuma to also monitor certs this week when I got the reminder email about them stopping the email warnings, been using it for some time for uptime monitoring (mostly to see if some auto docker image update screws up my services) and the notification parts has worked nicely for that, so I’m also assuming it will work nicely for the certificates

      • CosmicTurtle0@lemmy.dbzer0.comEnglish
        2·
        9 hours ago

        I use NewRelic myself. They are software agnostic and only connect to your URL to get the expiration date.

        If you set up LE correctly, it should never get an alert. I haven’t been alerted since I set it up, to the point that I wonder if I set up the monitor correctly.

        The only thing I wish it could do is use custom ports. I have some services running on non standard ports.