Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
The operating system my web server runs on is (include version): Windows 2008 R2
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Mid-day today it looks like our Certificate has expired. When trying to open an https it reverts to http. The major problem is that a 3rd party, using an API web service is unable to communicate with this server now. When I check the certificate via IIS and win-acme 220.127.116.117 it shows the Certificate renewed on 9/27/2021 and is valid till 12/26/2021.
Could this be part of the 9/30 cert changes?
I'm not very familiar with certificates. Not sure if there is anything I should try? I'm afraid of just requesting new certs and breaking the existing.
I deleted the IIS certificate in my first post from the IIS > Site Certificates
Ran win-acme (newest version) and generated a new cert
In IIS > Edit Bindings I selected the new cert for my https but it's still not working?
I tried a reboot