# cert-manager: Challenge stuck pending — HTTP-01 self check failed / waiting for ingress solver

**Code:** `cert-manager` · **Category:** SSL / TLS · **Seen on:** Kubernetes, SSL

A Kubernetes `Certificate` stays "Not Ready" because the ACME challenge can't be completed.

## 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?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/ssl/cert-manager-challenge-pending-http01)
