tlsv1 alert internal error — the TLS peer hit an internal problem during the handshake
The server sent alert 80, usually because its TLS configuration is broken or it can't pick a certificate.
tlsv1 alert internal errorSSL alert number 80ssl3_read_bytes:tlsv1 alert internal errorTLS alert internal_error 80 Meaning
Typical causes are a missing/unreadable certificate for the requested SNI name, a certificate/key mismatch, an ACME/cert reload in progress, an unsupported curve, or an exhausted resource. Check the server error log at the time of the handshake.
Common causes
- No certificate for the requested hostname (SNI)
- Certificate or key unreadable/mismatched
- Broken reload or ACME renewal
- Unsupported curve/cipher configuration
- Server out of memory/file descriptors
⚡ Quick fix
- Read the server's TLS error log
- Verify the certificate for that SNI name
- Run
nginx -t/ reload cleanly
Detailed fix by platform
Shell
- bash
sudo tail -n 50 /var/log/nginx/error.log openssl s_client -connect host:443 -servername host
How to diagnose
- Server log — Error?
- Cert for SNI — Present?
- Reload — Clean?
🔧 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)
- bad record mac SSL error: bad record mac (decryption failed or corrupted TLS record)
- 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