Let’s Encrypt / Certbot: Challenge failed for domain example.com — Invalid response from http://example.com/.well-known/acme-challenge/x: 404
Let’s Encrypt couldn’t verify you control the domain — the HTTP-01 challenge file wasn’t served, or DNS points elsewhere.
Challenge failed for domainInvalid response fromSome challenges have failedTimeout during connect (likely firewall problem) Meaning
Let’s Encrypt fetches /.well-known/acme-challenge/<token> over port 80. Wrong DNS (old server, IPv6 AAAA to another host), port 80 blocked, redirects to a wrong host, or a CDN/proxy intercepting the path cause failures. DNS-01 challenges fail when TXT records aren’t visible yet.
Common causes
- DNS A/AAAA records not pointing to this server (stale AAAA common)
- Port 80 blocked by firewall/security group
- Web server config not serving the challenge path (redirect/app routing)
- CDN/proxy (Cloudflare) interfering
⚡ Quick fix
- Make DNS point to this server (remove wrong AAAA)
- Open port 80 temporarily
- Use certbot --nginx/--apache or webroot matching the served root; or DNS-01 with a DNS plugin
Detailed fix by platform
Shell
- bash
dig +short A example.com; dig +short AAAA example.com sudo certbot certonly --webroot -w /var/www/html -d example.com -d www.example.com --dry-run
How to diagnose
- DNS — A/AAAA records
- Reach — curl http://example.com/.well-known/acme-challenge/test
- Proxy — CDN in front?
🔧 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
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] ...')))
- SSLCertificateFile: file does not exist Apache: AH02240: Server should be SSL-aware but has no certificate configured / SSLCertificateFile: file '/etc/ssl/x.crt' does not exist or is empty
- 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)
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 12 Oct 2026