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.
tlsv1 alert unknown caSSL alert number 48sslv3 alert unknown caSSL routines:ssl3_read_bytes:tlsv1 alert unknown ca 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
CAfilein the app - Container without CA bundle
⚡ Quick fix
- Add the CA to the trust store (
update-ca-certificates) - Serve the full chain
- Point
ssl_client_certificateat the correct CA
Detailed fix by platform
Shell
sudo cp internal-ca.crt /usr/local/share/ca-certificates/ && sudo update-ca-certificates
How to diagnose
- Which side — Sent the alert?
- CA — In trust store?
- 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:
Similar errors
- bad certificate sslv3 alert bad certificate — server rejected the client certificate (mutual TLS)
- Django Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port)
- insufficient security tlsv1 alert insufficient security — server rejects the offered protocol/cipher/key strength
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