-
-
Notifications
You must be signed in to change notification settings - Fork 118
Automatic renewal of ZeroSSL didn't happen #1007
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
Comments
Hmm ... do you have automatic renewal enabled on the Let's Encrypt page in Virtualmin? Also, did you get any email about the renewal failure? Also, does renewing manually work? |
Yes, automatic renewal is enabled. The manual renewal just worked—but it literally took 30 minutes. And, there were emails! First was a failure email:
...which must be false-positive. And then, in a about an hour it happened to be successful:
...and then two more emails, with interval of 2 days, which are extremely misleading:
It's worth noting that this is a ZeroSSL certificate, and, most importantly, neither the certificate itself nor the domain configuration file was actually updated! |
Whoa, very odd that it said the cert was updated but it actually failed! Do you have any kind of unusual setup for this domain regarding the SSL cert, like it being a symlink or stored in a non-standard location? |
No, nothing’s different. Everything is the same as on all other domains—the certificates are in the default Also, I just realized I should mention that it was originally set up with Let’s Encrypt and then switched to ZeroSSL—might this be related to the issue? |
No that shouldn't matter. Does this continue to fail consistently on this domain? If so, you might try adding some debug code to see where the SSL cert is being saved to. |
Hello Jamie!
Three months ago, I set up ZeroSSL to be used for one of my domains, but today it expired without renewing automatically. Background status collection is enabled, and other Let’s Encrypt renewals are working fine.
It seems like a bug.
The text was updated successfully, but these errors were encountered: