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

tlsv1 alert unknown ca — the other side doesn't trust the certificate's issuer

A TLS alert 48: the peer received a certificate chain whose CA it doesn't know.

Exact message you may see tlsv1 alert unknown caSSL alert number 48sslv3 alert unknown caSSL routines:ssl3_read_bytes:tlsv1 alert unknown ca
Seen on: SSL OpenSSL Linux

Meaning

Often seen when a client rejects the server's chain (missing CA in its trust store/intermediate not sent) or a server rejects a client certificate. Install the CA on the rejecting side, send the full chain, and check which side sent the alert.

Common causes

  • Server cert signed by an internal CA missing from the client store
  • Intermediate not sent
  • Client cert's CA not in server's CA file
  • Wrong CAfile in the app
  • Container without CA bundle

⚡ Quick fix

  1. Add the CA to the trust store (update-ca-certificates)
  2. Serve the full chain
  3. Point ssl_client_certificate at the correct CA

Detailed fix by platform

Shell

  1. sudo cp internal-ca.crt /usr/local/share/ca-certificates/ && sudo update-ca-certificates

How to diagnose

  1. Which side — Sent the alert?
  2. CA — In trust store?
  3. Chain — Complete?

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

bad certificate — sslv3 alert bad certificate — server rejected the client certificate (mutual TLS) (SSL / TLS)bad certificateDjango — Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port) (Email / SMTP)Djangoinsufficient security — tlsv1 alert insufficient security — server rejects the offered protocol/cipher/key strength (SSL / TLS)insufficient securityinternal error — tlsv1 alert internal error — the TLS peer hit an internal problem during the handshake (SSL / TLS)internal errorNSURLErrorServerCertificateUntrusted (-1202) — iOS: Error Domain=NSURLErrorDomain Code=-1202 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be 'example.com'" (SSL / TLS)NSURLErrorServerCerti…Schannel 36887 — Schannel Event 36887: A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 46/48/40 (SSL / TLS)Schannel 36887SSL inspection — Corporate proxy TLS inspection (Zscaler, Netskope, Palo Alto): certificate issued by an untrusted corporate root (SSL / TLS)SSL inspectionUNABLE_TO_VERIFY_LEAF_SIGNATURE — Node.js: Error: unable to verify the first certificate (code: UNABLE_TO_VERIFY_LEAF_SIGNATURE) (SSL / TLS)UNABLE_TO_VERIFY_LEAF…unknown ca

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.