Happening on renewal on all our domains today, example:
• Information - Removing certificate "[IIS] tpsoffer.com, (any host) @ 2024/3/27" from store "WebHosting"
• Warning - Error updating renewal info: "Must specify a request path"
• Error - Error getting renewal information from server
• Information - Next renewal due after "2024/7/15"
IIS 10.0 on Windows Server 2019, using version wacs.exe 2.2.6.1571
Hello @agorist, welcome to the Let's Encrypt community.
You might have a geo blocking issue.
Please read these:
When you opened this thread in the Help section, you should have been provided with a questionnaire. Maybe you didn't get it somehow (which is weird), or you've decided to delete it. In any case, all the answers to this questionnaire are required:
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.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
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):
Your problem seems very similar to the one described in this thread. win-acme has a known problem with its support of ARI (ACME Renewal Info). See that thread for work-around and related info. I know your error message is slightly different but I am pretty sure your "Error - Error getting renewal information from server" is talking about ARI.
FYI, this issue has been resolved by the latest version of win-acme, 2.2.9.1. "This release changes the implementation of ARI (ACME Renewal Information) from the draft 1 to draft 3 of the specification, to remain compatible with the leading implementation in Boulder / Let's Encrypt. Previous win-acme releases from 2.2.3 to 2.2.8 are currently reporting non-fatal errors because draft 1 compatibility was dropped by Let's Encrypt"