Closed bjburke002 closed 2 years ago
Hi, just to follow up--after adding a short delay before moving into this.WaitForVerificationWithTable() in OrderCommand, certs are being provided as expected. Appears this is a quirk where LetsEncrypt only allows for one check and it happens to occur before DNS records can finish propagating.
Just got this error and I'm running the latest release, is this really fixed?
I've noticed this behavior on new orders for the last few days specifically--the tool creates TXT records in the appropriate Azure DNS zone but doesn't seem to be able to validate afterward. I've also been able to confirm that if a TXT record is already in place, it will be updated, but the challenge only sees an invalid string.
I assume this is some kind of quirk regarding DNS propagation, but even when giving a 5 minute verification timer the order is still never verified. Any guidance would be appreciated.