no shared cipher SSL / TLS Origin: Network OSI layer 6 · Presentation Last updated 18 Nov 2026

SSL routines: no shared cipher (client and server have no common cipher suite)

The handshake fails because no cipher suite is supported by both sides.

Exact message you may see no shared cipherSSL routines:ssl3_get_client_hello:no shared ciphererror:1408A0C1:SSL routines:ssl3_get_client_hello:no shared cipherno ciphers available
Seen on: SSL OpenSSL Nginx

Meaning

The server's ssl_ciphers/SSLCipherSuite list is too narrow for the client, or the client only offers deprecated ciphers (RC4, 3DES, CBC-only) that the server disabled. Test with openssl s_client -cipher and nmap --script ssl-enum-ciphers, then add compatible modern suites (ECDHE-RSA-AES128-GCM-SHA256).

Common causes

  • Server cipher list too restrictive
  • Client offers only obsolete ciphers
  • Certificate type mismatch (ECDSA vs RSA suites)
  • FIPS mode restrictions
  • Protocol versions limited

⚡ Quick fix

  1. Enable modern ECDHE + AES-GCM suites on the server
  2. Upgrade the client TLS library
  3. Compare lists with nmap --script ssl-enum-ciphers -p 443 host

Detailed fix by platform

Shell

  1. bash
    nmap --script ssl-enum-ciphers -p 443 example.com
    openssl s_client -connect example.com:443 -cipher ECDHE-RSA-AES128-GCM-SHA256

How to diagnose

  1. Ciphers — Overlap?
  2. Cert type — Matches suites?
  3. FIPS — Enabled?

🔧 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):

4-way handshake timeout / Incorrect password — Networking: wlan0: WPA: 4-way handshake failed - pre-shared key may be incorrect / WRONG_KEY (Networking)4-way handshake timeo…530 — 530 5.7.0 Must issue a STARTTLS command first (TLS required before AUTH or sending) (Email / SMTP)530cipher suites — Java: SSLHandshakeException — no cipher suites in common (server side) (SSL / TLS)cipher suitescurl 56 — curl: (56) OpenSSL SSL_read: Connection reset by peer, errno 104 (TLS connection dropped mid-transfer) (SSL / TLS)curl 56curve — TLS handshake failure: no suitable curve / unsupported elliptic curve (ECDH/ECDSA) (SSL / TLS)curveDjango — Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port) (Email / SMTP)DjangoECDSA — ECDSA certificate fails on old clients (no ECC cipher suites): serve an RSA certificate too (SSL / TLS)ECDSAGo TLS — Go: tls: first record does not look like a TLS handshake (HTTP server spoken to with HTTPS) (SSL / TLS)Go TLSno shared…

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.