I will describe how I got into this situation below, but the bottom line is I’ve attempted two renewals today that failed. It is now configured correctly, LetsEncrypt sent me an email, today, saying my certs will be invalidated TOMORROW due to a bug on their part, and now I’ve got a 48hr hold on attempting the renewal again, which will leave me with invalid certs for almost two days.
I went to figure out how to force a renewal (which I figured out you can configure auto renewal down to a day, temporarily, to “force” it). I saw the new version button and foolishly upgraded my CertifyTheWeb software BEFORE I took care of my urgent issue. (I definitely know better, ugh).
Assuming all would be fine, I clicked to renew. I have several domains registered, some use http auth, some DNS auth. My first auth rule had no domains specified, for http-auth. This was the default rule. But after the upgrade, it used this rule even though the next rule specified to use DNS authentication for some of the domains. I fixed this issue by specifying the domain to use http-auth, and, in a rush, tried again. This time it is my encrypted DNS auth-key and secret that could not be decrypted after the upgrade, and so the renewal failed a second time. I fixed that issue by reentering them. This time I used the TEST button. All looked good. But when I clicked to renew, it says I’ve failed twice, and I’m blocked for 24 hours! I urgently need this cert renewed by tomorrow, there must be some way to make an exception?? Should I just start over and use “Request Certificate” instead of renewing? Will that have the same restriction?
I’m really not happy with the upgrade process, but I still love this product. But I really urgently need to override this 48hr waiting period.
Any help, even creative rube-goldberg ones, would be greatly appreciated!. Should I be conversing with LetsEncrypt about this? Is this their restriction, and certifytheweb cannot do anything about it?
Thanks in advance for any and all feedback that can help!