New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Renewal stuck on Send GET to https://acme-v02.api.letsencrypt.org/directory #2567
Comments
Let me guess, this is an AWS VM? |
No @WouterTinus , it is a win 2k19 VM on Hyper-V on-prem |
I would recommend trying different values for the proxy setting, see for options here: |
I dont have any proxy, which proxy you are refering to? |
Regardless, the software will try to detect if you have a proxy, which has been known to cause issues sometimes. So I recommend to change the detection method or disable proxy detection all together. |
@WouterTinus I disabled proxy as follows rerun same thing is happening, tool gets stuck at "Send get to ........" |
The null hould be without quotes, sorry if that's not clear from the docs 😄 |
It's one of the things that is considered but in this case the actual certificate expiry date wins 😄 |
Not sure I understand why "actual certificate expiry date wins" If I renew it with indicating to be 365 days instead of 55? Do you mean that next time I renew in 55 days the 365 will win? |
The validity date is generally up to the certificate provider, not up to the client. Let's Encrypt won't issue anything valid longer (or shorter) than 90 days. |
OK, got it. so the schedueled task created by the client will run everyday and on the day 90 will do the renewal? |
Release 2.2.9 contains a fix that automatically disables proxy detection after a 30 second timeout. |
Hi, I am trying to renew my certificate for IIS, I noticed that the schedueled task gets hanged and keeps in status running, I issued
wacs --renew --force --verbose
and it gets stuck as follows
and after 1 hour I broke the sessionn
in the log I have same thing
the log for the shedueled task also gets stuck
Thanks for your help
The text was updated successfully, but these errors were encountered: