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

Docker container can't make HTTPS calls: x509 certificate signed by unknown authority (image has no ca-certificates)

Minimal or scratch images ship without a CA bundle, so every TLS verification fails inside the container.

Exact message you may see x509: certificate signed by unknown authority containerno CA certificates in image scratchx509: failed to load system roots and no roots providedError loading system roots ca-certificatesSSL certificate problem inside Docker container
Seen on: Docker Go SSL

Meaning

Install ca-certificates in the image (apt-get install -y ca-certificates / apk add ca-certificates), or copy the bundle from a builder stage into scratch/distroless. For corporate CAs, add them and run update-ca-certificates.

Common causes

  • scratch/slim/alpine image without ca-certificates
  • Bundle not copied into the final stage
  • Corporate root missing
  • Stale bundle in an old image
  • Wrong cert path for the runtime

⚡ Quick fix

  1. RUN apt-get update && apt-get install -y ca-certificates
  2. COPY --from=builder /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/
  3. Rebuild images regularly

Detailed fix by platform

Dockerfile

  1. bash
    FROM scratch
    COPY --from=builder /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/
    COPY app /app

How to diagnose

  1. Image — Minimal?
  2. Bundle — Present?
  3. Corporate CA — Added?

🔧 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):

ACM region — CloudFront can't use my ACM certificate: it must be requested in us-east-1 (N. Virginia) (SSL / TLS)ACM regionALB listener — ALB HTTPS listener: CertificateNotFound / default certificate missing or SNI certificate list incomplete (SSL / TLS)ALB listenerDjango — Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port) (Email / SMTP)DjangoTimeout 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)Traefikwget — wget: ERROR: cannot verify <host>'s certificate, issued by ... Unable to locally verify the issuer's authority (SSL / TLS)wgetx509: certificate signed by unknown authority — x509: certificate signed by unknown authority (docker pull/login) (Docker)x509: certificate sig…x509: certificate signed by unknown authority — Go: x509: certificate signed by unknown authority (Go)x509: certificate sig…ca-certif…

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.