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: Auto renewal
It produced this output: The expiration date does not change after automatic renewal.(wacs.exe in cmd)
My web server is (include version):
The operating system my web server runs on is (include version): Windows
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): We're not using cerbot.
The expiration date does not change after automatic renewal.
It was first renewed on May 10. The expiration date was August 8. June 20th is the automatic renewal date. I checked if it was automatically renewed on June 20th, but when I connected cmd to admin mode and ran wacs, the expiration date remained the same on August 8th. The expiration date should be changed to September 18th, but it hasn't been changed. In the \ProgramData\win-acme\acme.api.letsencrypt.org~~~.renewal.json file, the history shows that the expiration date has changed as follows, but the expiration date has not changed in the cmd window.
It seems that 4 .pem files have been changed to June 20th.
What I'm curious about is
- Based on my situation, is the certificate updated properly?
- If it has been updated properly, why can't I change the expiration date by running wacs on cmd and how can I change it?
- If it hasn't been updated properly, how can I get automatic renewal to work properly? (Automatic renewal used to be registered in the job scheduler while installing win-acme.)