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

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.

Exact message you may see Caddy obtaining certificate failedcould not get certificate from issueracme: error: 403 :: urn:ietf:params:acme:error:unauthorizedtls.obtain error obtaining certificateCaddy ACME challenge failed
Seen on: Caddy SSL Linux

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

  1. Open 80/443 and stop other listeners
  2. Fix DNS A/AAAA records
  3. Use tls internal for private names

Detailed fix by platform

Shell

  1. bash
    sudo journalctl -u caddy --no-pager | tail -50
    ss -ltnp | grep -E ":(80|443)"

How to diagnose

  1. Ports — Reachable?
  2. DNS — Correct?
  3. 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:

Where this error sits

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

cert-manager — cert-manager: Challenge stuck pending — HTTP-01 self check failed / waiting for ingress solver (SSL / TLS)cert-managerChallenge 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)DjangoProblem binding to port 80: Could not bind to IPv4 or IPv6 — Certbot: Problem binding to port 80: Could not bind to IPv4 or IPv6 (standalone authenticator) (SSL / TLS)Problem binding to po…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 limitTimeout during connect (likely firewall problem) — Let's Encrypt: Fetching http://example.com/.well-known/acme-challenge/token: Timeout during connect (likely firewall problem) (SSL / TLS)Timeout during connec…Traefik — Traefik: Unable to obtain ACME certificate for domains (acme.json permissions, challenge, resolver) (SSL / TLS)TraefikCaddy

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.