cert-manager: Challenge stuck pending — HTTP-01 self check failed / waiting for ingress solver
A Kubernetes Certificate stays "Not Ready" because the ACME challenge can't be completed.
Waiting for HTTP-01 challenge propagation: wrong status code '404', expected '200'Challenge pending cert-managerWaiting for HTTP-01 challenge propagation: failed to perform self check GET requestcert-manager challenge state pendingIssuing certificate as Secret does not exist Meaning
Describe the Challenge (kubectl describe challenge) and check: the solver pod/ingress exists and is reachable from outside, DNS points at the ingress, the ingress class matches ingressClassName, no redirect/auth blocks /.well-known/acme-challenge/, and the self-check passes. For wildcards use DNS-01.
Common causes
- DNS doesn't point to the ingress
- Wrong ingress class for the solver
- HTTP→HTTPS redirect or auth blocking the path
- Network policy/firewall blocking
- Challenge solver pod not scheduled
⚡ Quick fix
kubectl describe certificate,certificaterequest,order,challenge -n NS- Curl
http://domain/.well-known/acme-challenge/token - Set the right
ingressClassNamein the issuer solver
Detailed fix by platform
Shell
- bash
kubectl describe challenge -n app curl -v http://app.example.com/.well-known/acme-challenge/TEST
How to diagnose
- Challenge status — Pending?
- Path — Reachable?
- Ingress class — Matches?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Caddy Caddy: obtaining certificate failed — ACME challenge error (port 80/443 blocked or DNS wrong)
- Challenge failed for domain Let’s Encrypt / Certbot: Challenge failed for domain example.com — Invalid response from http://example.com/.well-known/acme-challenge/x: 404
- Django Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port)
Most viewed in SSL / TLS
- HTTPSConnectionPool: Max retries exceeded (SSLError) Python requests: HTTPSConnectionPool(host='api.example.com', port=443): Max retries exceeded with url: /v1 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] ...')))
- DST Root CA X3 expired (old clients fail) Old clients: certificate has expired — Let's Encrypt chain uses expired DST Root CA X3 (OpenSSL 1.0.x, Android < 7.1.1)
- Keystore was tampered with, or password was incorrect Java keytool: java.io.IOException: Keystore was tampered with, or password was incorrect
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026