Old clients can't connect to the AWS load balancer: security policy disables TLS 1.0/1.1 (or requires it)
The ELB/ALB/NLB SSL negotiation policy doesn't allow the protocol/ciphers the client uses.
ELBSecurityPolicy TLS 1.0 clients failALB security policy TLS version not supportedSSL negotiation policy ELB TLS 1.0ELB SSL handshake failure old clients Meaning
Choose a policy that matches your audience: ELBSecurityPolicy-TLS13-1-2-2021-06 for modern clients, a -Res- or older policy for legacy ones. Compliance may require TLS 1.2+. Check access logs for tls_version/cipher, and upgrade clients rather than weakening the policy.
Common causes
- Policy removed TLS 1.0/1.1
- Client only supports legacy ciphers
- ECDSA vs RSA certificate suites mismatch
- FIPS/PCI policy
- Policy updated automatically (predefined default)
⚡ Quick fix
- Check client TLS versions from access logs
- Pick the appropriate predefined security policy
- Upgrade legacy clients
Detailed fix by platform
Shell
aws elbv2 modify-listener --listener-arn LISTENER_ARN --ssl-policy ELBSecurityPolicy-TLS13-1-2-2021-06
How to diagnose
- Policy — Which?
- Client TLS — Supported?
- Logs — tls_version?
🔧 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
- ACM region CloudFront can't use my ACM certificate: it must be requested in us-east-1 (N. Virginia)
- ALB listener ALB HTTPS listener: CertificateNotFound / default certificate missing or SNI certificate list incomplete
- AWS_CA_BUNDLE AWS CLI/SDK: SSL validation failed for https://... certificate verify failed (custom CA bundle / proxy)
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