Hello,
Upgrade your client (if it's win-acme, then version 2.0.19 is needed).
Then run the client, go to manage renewals, and renew all. That should fix it.
opened 09:54AM - 19 May 21 UTC
question
Hi everyone,
I received the following email by letsencrypt:
_Hello from th… e staff at Let's Encrypt._
_On September 30, there will be a change in how older browsers and devices trust Let's Encrypt certificates, resulting in a minor decrease in compatibility. If you run a typical website, you won't notice a difference. Devices and browsers running up-to-date software will continue working fine, and we've taken steps to make sure the vast majority of older devices will too. If you run a large website, or need to support less common software (particularly non-browser software), you'll want to read about the details at:_
_https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/_
_In either case, no action is required from you. We're letting you know so you can provide answers to any questions your site visitors may have._
_Here is a sample hostname from one of your current Let's Encrypt certificates: exampledomain.com_
_Since 2015 we've served the world with 1.6 billion free certificates, each one providing security and privacy to people on the Web. It's work that's 100% funded by charitable donations since we are a nonprofit. If your company is interested in sponsorship, please email sponsor@letsencrypt.org. If you can make a donation, we ask that you consider supporting our work today: https://letsencrypt.org/donate/_
_Thank you._
_- The Let's Encrypt team_
I observe that my certificates have the following certification path (executed with Chrome in W10): DST Root CA X3 --> R3 --> mywebsite
My certificates are generated in win-acme (for WServer 2019) for apache (not ISS).
Do you know if this Let's Encrypt change is a problem in win-acme?
Thanks for advance.
system
October 30, 2021, 6:00pm
#4
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.