x/crypto/acme/autocert: better error messages for failed validations #60554
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes, with latest golang.org/x/crypto/acme/autocert on 2023-06-01.
What did you do?
I'm using golang.org/x/crypto/acme/autocert in https://github.com/mjl-/mox. A user of mox couldn't get a TLS certificate with autocert through Let's Encrypt. The error message only contained "no viable challenge type found". They had to try different software to see the error messages Let's Encrypt was sending back. Autocert does not expose the errors, even though they describe nicely what the problem was (CAA lookup failed in this case).
What did you expect to see?
An error message like this:
What did you see instead?
Suggested patch
The text was updated successfully, but these errors were encountered: