cert-manager SSL / TLS Origin: Network OSI layer 6 · Presentation Last updated 18 Nov 2026

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.

Exact message you may see 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
Seen on: Kubernetes SSL

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

  1. kubectl describe certificate,certificaterequest,order,challenge -n NS
  2. Curl http://domain/.well-known/acme-challenge/token
  3. Set the right ingressClassName in the issuer solver

Detailed fix by platform

Shell

  1. bash
    kubectl describe challenge -n app
    curl -v http://app.example.com/.well-known/acme-challenge/TEST

How to diagnose

  1. Challenge status — Pending?
  2. Path — Reachable?
  3. 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:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

Caddy — Caddy: obtaining certificate failed — ACME challenge error (port 80/443 blocked or DNS wrong) (SSL / TLS)CaddyChallenge 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 (SSL / TLS)Challenge failed for …Django — Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port) (Email / SMTP)DjangoInvalid response from .well-known/acme-challenge: 404 — Certbot: Detail: Invalid response from http://example.com/.well-known/acme-challenge/abc: 404 (SSL / TLS)Invalid response from…issuer — cert-manager: Issuer or ClusterIssuer not ready — ACME account registration failed / referenced issuer not found (SSL / TLS)issuernf_conntrack: table full, dropping packet — Networking: kernel: nf_conntrack: table full, dropping packet — new connections fail on a Linux firewall/NAT host (Networking)nf_conntrack: table f…rate limit — cert-manager: acme: urn:ietf:params:acme:error:rateLimited (too many certificates / failed validations) (SSL / TLS)rate limitSAN limit — Certificate request failed: too many domain names in one certificate (SAN limit exceeded) (SSL / TLS)SAN limitcert-mana…

Explore the map of this error Full error map →

🧠 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.