Failing to Renew about letsencrypt-siteextension HOT 4 CLOSED

I was reluctant to respond to the comment from @mmsigi<https://github.com/mmsigi> to avoid unnecessary clutter in everyone’s inbox, but as an early adopter of Simon’s extension, and despite a few bumps in the road, I am grateful for everyone’s contributions to this little “hobby”! We are a small shop with over a dozen Web apps using the Azure Let’s Encrypt extension, each with several domains, so even if we have to update the extension occasionally, the benefits far exceed the minor and infrequent drawbacks. Thank you again Simon and all other contributors; this extension has saved us thousands of Dollars (Euros, Pounds, Yen, Rubles, etc.) over the years! From: Simon J.K. Pedersen <[email protected]> Sent: Tuesday, March 2, 2021 11:08 AM To: sjkp/letsencrypt-siteextension <[email protected]> Cc: Subscribed <[email protected]> Subject: Re: [sjkp/letsencrypt-siteextension] Failing to Renew (#385) @mmsigi<https://github.com/mmsigi> - Thanks for you feedback. It is always annoying when something free doesn't work as you want it to. But like I clearly state in the readme it is a hobby project without any enterprise support (sounds like your use case is a little more professional), and if you care about the uptime of your sites, you should go with an Azure supported (but not free) way of setting up SSL. I agree that the update model for site extensions are not very great, but I cant fix that. However there has been one update to the siteextension in the last year (I wouldn't exactly call that constantly need for updating). It was trigged by a change in intermediate certificates from Lets Encrypt, not something that I'm in control of. Before that, there was more frequent updates because we were still ironing out bugs and adding features. The email notification feature from Lets Encrypt works flawlessly for me. If you get a Lets Encrypt warning email then you need to take action, you should never receive it, if everything is working as it should, as the certificate should be renewed 21 days before expiration. Dont get me wrong, I would love to fix this extension so it was perfect, but to be honest the siteextension model+webjob is not the right fit for the job, however it is still a solution, so for now I consider it to be in support mode for those people who benefit from it. Building an alternative and more perfect solution, based on the knowledge gained from this project, and the advances of Azure, is not something that I'm willing to invest my spare time in, knowing that Microsoft can make it obsolete over night by providing their own certificate service. Something I honestly thought they would have done a long long time ago. The alternative of building a pay-to-use service is in my opinion unfair to an otherwise great open source service from Lets Encrypt. So that leaves us where we are today, not in the most ideal place for a use-case like yours. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#385 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFCZ5CTRH7TCWE6X2TMQGD3TBUEPLANCNFSM4YMVHXAQ>.