SSL error: bad record mac (decryption failed or corrupted TLS record)
A TLS record failed its integrity check, so the connection is dropped.
bad record macSSL3_READ_BYTES:sslv3 alert bad record macerror:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mactlsv1 alert bad record mac Meaning
Causes include a buggy middlebox/load balancer or TLS offload, mismatched session keys after session resumption across servers, MTU/packet corruption, a misconfigured proxy mixing TLS sessions, or an OpenSSL bug. Disable session tickets/offload to test, update TLS libraries and check network devices.
Common causes
- Faulty NIC offload or middlebox
- Session ticket keys not shared across servers
- Proxy terminating TLS inconsistently
- Packet corruption/MTU issue
- Library bug or thread-safety problem
⚡ Quick fix
- Try without session tickets/offload
- Share ticket keys across backends
- Update OpenSSL and check network hardware
Detailed fix by platform
Nginx
ssl_session_tickets off;
How to diagnose
- Offload — Enabled?
- Tickets — Shared?
- Network — Corrupting?
🔧 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
- 530 530 5.7.0 Must issue a STARTTLS command first (TLS required before AUTH or sending)
- curl 56 curl: (56) OpenSSL SSL_read: Connection reset by peer, errno 104 (TLS connection dropped mid-transfer)
- disabledAlgorithms Java: SSLHandshakeException — TLSv1/TLSv1.1 or algorithm disabled by jdk.tls.disabledAlgorithms
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