Hey, so we have a thread in the Portuguese support category in which a user is stuck and I thought I would summarize the problem in English just to see if someone knows more about this.
This user is using the Kubernetes cert-manager and got this log entry
I0329 19:16:49.167591 1 solver.go:87] cert-manager/acmesolver "msg"="got successful challenge request, writing key" "base_path"="/.well-known/acme-challenge" "host"="suporte.klavaecia.com.br" "path"="/.well-known/acme-challenge/JOs0RoZfu_XIKtVb2s1ZztgB3UjC8MnFL0KqQYgl8S0" "token"="JOs0RoZfu_XIKtVb2s1ZztgB3UjC8MnFL0KqQYgl8S0"
The HTTP-01 challenge file exists and is publicly accessible at this location (the challenge seems to me to have been correctly solved), but nothing else seems to have happened or gotten logged, and indeed the associated challenge (whose URL was identified with some kind of
kubectl command) is still, at this moment, in
pending state on the CA. So it seems like cert-manager never went on to inform the CA that the challenge had been satisfied.
Does anyone know why this might happen, or whether there is a command that would nudge it further along, or where we can find more logs in this environment that might help with debugging?