Closed GabrielMajeri closed 2 years ago
Just went through the process for the same reasons so thought I would share.
services
.AddLettuceEncrypt()
.PersistDataToDirectory(Directory.CreateDirectory("/data/lets-encrypt"), "secret");
mv /data/lets-encrypt/certs /data/lets-encrypt/certs_old
systemctl restart my-app
[18:36:50 INF] Created certificate CN=my-app.com (OIHIUHEFIUOWEHFOIUH#$I@UH$OI@U#H$)
Created certificate CN=my-app.com (EFWF@#$F$#GT#$T$#T#$T$#F)
info: LettuceEncrypt.Internal.AcmeStates.ServerStartupState[0]
[18:36:47 INF] Creating certificate for my-app.com
Creating certificate for my-app.com
info: LettuceEncrypt.Internal.AcmeStates.ServerStartupState[0]
ls /data/lets-encrypt/certs
Thank you, @lawrence-laz! This solution works perfectly.
I'll ask @natemcmaster to close this issue if they don't have a suggestion for a different way of force-renewing the certificate, and maybe pinning this issue to help other interested people find it.
Deleting the certs folder and restarting the server is the mechanism I would recommend, too. Thanks for sharing the details, @lawrence-laz
Great! I'm closing this, then.
I've received the following e-mail this morning, from Let's Encrypt, related to an ASP.NET Core web app I'm securing using LettuceEncrypt. It's related to a problem they had with the TLS-ALPN-01 challenge method:
Do you have some recommendations on how this will affect LettuceEncrypt users? Is there anything I can do to help/force LettuceEncrypt to renew the certificate, as requested by Let's Encrypt? I've tried looking it up in the
README
, but it's not very clear how I can do this (without deleting all my existing certificates, which might not be the right solution?)