A cert-manager Certificate stays at READY False with Let's Encrypt
Certificate READY is False and stays FalseShort answer
A Certificate that stays not ready is waiting on a chain: Issuer, CertificateRequest, Order, Challenge. Describe each one in that order. The first object with an error or a pending reason is the cause. Usual ones are an unready Issuer, a failing HTTP-01 self-check, or a DNS-01 self-check that cannot see the TXT record.
Fix it fast
1Find out which cause you have
List the chain of objects in the namespace, then describe the last one that exists.
kubectl get certificate,certificaterequest,order,challenge -n my-namespace kubectl describe challenge -n my-namespace2Match what you see, then jump to its fix
- 1
kubectl get clusterissuer shows READY FalseThe Issuer or ClusterIssuer is not readyFix - 2
Challenge stays pending and the self-check reports 404 or tls: handshake failureThe HTTP-01 challenge URL is not reachableFix - 3
Waiting for dns-01 challenge propagation in the challenge reasonThe DNS-01 self-check cannot see the TXT recordFix
- 1
What does the error look like?
Certificate READY is False and stays FalseIssuing certificate as Secret does not existWaiting for dns-01 challenge propagation
Cause 1 of 3
The Issuer or ClusterIssuer is not ready
1Check
Read the Conditions and Events of the issuer. The docs name an invalid contact email (error invalidEmail) and a leftover ACME account secret from an earlier issuer.
kubectl get issuer,clusterissuer -A
kubectl describe clusterissuer letsencrypt-prod2Fix
Use a real contact email in the issuer. If an old account secret is the problem, delete that secret so cert-manager creates a new account.
kubectl edit clusterissuer letsencrypt-prod
kubectl delete secret letsencrypt-prod-account-key -n cert-manager3Verify
The issuer reports ready.
kubectl get clusterissuer letsencrypt-prodConfirmed by cert-manager.io
Cause 2 of 3
The HTTP-01 challenge URL is not reachable
1Check
The challenge URL must be reachable from the public internet, and the solver pod and its Ingress must exist. A 404 means check the URL, the solver pod and kubectl describe ingress.
kubectl get pods,ingress -n my-namespace
kubectl describe challenge -n my-namespace2Fix
Fix the Ingress path or class so the solver is served. For tls: handshake failure the docs say to set the issue-temporary-certificate annotation, and add the http01-edit-in-place annotation if the ingress controller conflicts over the hostname.
metadata:
annotations:
cert-manager.io/issue-temporary-certificate: "true"
acme.cert-manager.io/http01-edit-in-place: "true"3Verify
The challenge moves to valid.
kubectl get challenges -n my-namespaceConfirmed by cert-manager.io
Cause 3 of 3
The DNS-01 self-check cannot see the TXT record
1Check
Confirm the TXT record is visible publicly or in your DNS provider UI. If it is public but not seen from inside the cluster, the self-check nameservers differ.
dig +short TXT _acme-challenge.example.com
kubectl describe challenge -n my-namespace2Fix
Change the nameservers cert-manager uses for the self-check. The docs also note that cert-manager relies on SOA records, so a resolver that filters them (dnsmasq with --filterwin2k) causes the wrong zone to be used.
# set the self-check nameservers in the cert-manager controller
# settings, as the troubleshooting page describes, to servers
# that can see your public zone3Verify
The Order reaches valid.
kubectl describe order -n my-namespaceConfirmed by cert-manager.io
How do I stop it coming back?
- Use Let's Encrypt staging while you test an issuer, then switch to production.
- Keep contact emails real.
- Alert on Certificates that stay not ready for more than a few minutes.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Servers
Argo CD behind an nginx Ingress loops with too many redirects
307 Temporary Redirect on every request to the Argo CD host
The browser and Argo CD disagree about who handles TLS.
3 causes, each with a fixServers
Let's Encrypt cannot find the _acme-challenge TXT record for your domain
The TXT record added at the DNS host never shows up for validation
With the DNS-01 challenge, Let's Encrypt looks up a TXT record named _acme-challenge under your domain.
3 causes, each with a fixServers
Docker container cannot resolve hostnames (pip, apt, curl fail)
[Errno -3] Temporary failure in name resolution
A container copies its DNS settings from the host.
3 causes, each with a fixServers
Kubernetes in Docker Desktop will not start or stays on starting
kubectl shows no contexts, or errors against the docker-desktop context
When the Docker Desktop cluster hangs on starting, the usual causes are too few resources, a broken cluster state, or the kubeadm provisioner failing.
4 causes, each with a fixServers
Docker pull or container DNS fails with "server misbehaving"
docker pull fails while a browser on the same machine opens the registry fine
'Server misbehaving' is a Go resolver error: the DNS server answered, but with a reply code that is neither success nor name-not-found.
3 causes, each with a fixServers
EKS managed node group ends in Create failed because nodes never joined
NodeCreationFailure
Nodes that do not register within 15 minutes cause NodeCreationFailure and a Create failed status.
4 causes, each with a fix