This PR moves looking up info for HTTP {challenge,validation} from an error to a warning level.
The reasoning for this is as follows: we see with our certmagic deploy that the .well-known/acme-challenge/xxx paths are automatically checked by old issuers that still think they are managing the domain. These acme-challenge paths are then checked by certmagic to solve the challenge, but as it's an unknown challenge token, this fails.
It's still a relevant message to log, although not at the error level, IMHO.
This PR moves
looking up info for HTTP {challenge,validation}
from an error to a warning level.The reasoning for this is as follows: we see with our certmagic deploy that the
.well-known/acme-challenge/xxx
paths are automatically checked by old issuers that still think they are managing the domain. These acme-challenge paths are then checked by certmagic to solve the challenge, but as it's an unknown challenge token, this fails.It's still a relevant message to log, although not at the error level, IMHO.
Fixes https://github.com/caddyserver/certmagic/issues/268