I am on aws and tried your step-by-step instructions. I have everything seemingly up and running; but the challenge hangs. I guess it is not resolving hostname or something. I am getting this within the kubectl describe challenges command:
Waiting for HTTP-01 challenge propagation: failed to perform self check GET request 'http://example.com/.well-known/acme-challenge/TOKEN': Get "http://example.com/.well ... : dial tcp: lookup no such host
I tried kubectl describe certificate and see:
Normal Requested cert-manager Created new CertificateRequest resource
what step am I missing? I tried adding an A record in Route 53 with same dns name for the nginx ingress ext ip. But that didn't do anything. Would appreciate some help. Thanks.
for challenges to work, you need to use a real domain name that can be publicly resolved and reachable on public network. example.com is not a real domain name, hence let's encrypt cannot solve it.
Hi,
I am on aws and tried your step-by-step instructions. I have everything seemingly up and running; but the challenge hangs. I guess it is not resolving hostname or something. I am getting this within the
kubectl describe challenges
command:I tried
kubectl describe certificate
and see:what step am I missing? I tried adding an A record in Route 53 with same dns name for the nginx ingress ext ip. But that didn't do anything. Would appreciate some help. Thanks.