Caddy: obtaining certificate failed — ACME challenge error (port 80/443 blocked or DNS wrong)
Caddy can't get a certificate automatically, so HTTPS isn't available for the site.
Caddy obtaining certificate failedcould not get certificate from issueracme: error: 403 :: urn:ietf:params:acme:error:unauthorizedtls.obtain error obtaining certificateCaddy ACME challenge failed Meaning
Make sure DNS points to the server, ports 80 and 443 reach Caddy (no other service on them, firewall open), the domain is public, and rate limits aren't hit. Check logs (journalctl -u caddy) for the ACME error and use the staging CA while testing. For private/dev use tls internal.
Common causes
- Ports 80/443 blocked or in use
- DNS not pointing to the server
- Behind a proxy/CDN intercepting challenges
- Let's Encrypt rate limit
- Local/private domain name
⚡ Quick fix
- Open 80/443 and stop other listeners
- Fix DNS A/AAAA records
- Use
tls internalfor private names
Detailed fix by platform
Shell
- bash
sudo journalctl -u caddy --no-pager | tail -50 ss -ltnp | grep -E ":(80|443)"
How to diagnose
- Ports — Reachable?
- DNS — Correct?
- Error — Which ACME problem?
🔧 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
- cert-manager cert-manager: Challenge stuck pending — HTTP-01 self check failed / waiting for ingress solver
- 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