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

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.

Exact message you may see ELBSecurityPolicy TLS 1.0 clients failALB security policy TLS version not supportedSSL negotiation policy ELB TLS 1.0ELB SSL handshake failure old clients
Seen on: AWS SSL

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

  1. Check client TLS versions from access logs
  2. Pick the appropriate predefined security policy
  3. Upgrade legacy clients

Detailed fix by platform

Shell

  1. aws elbv2 modify-listener --listener-arn LISTENER_ARN --ssl-policy ELBSecurityPolicy-TLS13-1-2-2021-06

How to diagnose

  1. Policy — Which?
  2. Client TLS — Supported?
  3. 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:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

ACM region — CloudFront can't use my ACM certificate: it must be requested in us-east-1 (N. Virginia) (SSL / TLS)ACM regionALB listener — ALB HTTPS listener: CertificateNotFound / default certificate missing or SNI certificate list incomplete (SSL / TLS)ALB listenerAWS_CA_BUNDLE — AWS CLI/SDK: SSL validation failed for https://... certificate verify failed (custom CA bundle / proxy) (SSL / TLS)AWS_CA_BUNDLECNAME — CloudFront: CNAMEAlreadyExists / alternate domain name not covered by the certificate (InvalidViewerCertificate) (SSL / TLS)CNAMEDjango — Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port) (Email / SMTP)DjangoHSTS — Chrome: You cannot visit example.com right now because the website uses HSTS (NET::ERR_CERT_… no bypass) (Browser)HSTSPermissions policy violation — Console: [Violation] Permissions policy violation: camera is not allowed in this document (Feature-Policy) (Browser)Permissions policy vi…Refused to display in a frame — Console: Refused to display 'https://…' in a frame because it set 'X-Frame-Options' to 'deny' / 'sameorigin' (Browser)Refused to display in…security …

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.