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

nginx: [emerg] SSL_CTX_set_cipher_list("...") failed — invalid ssl_ciphers string

The ssl_ciphers value contains a cipher or syntax OpenSSL doesn't accept, so nginx won't load the config.

Exact message you may see nginx: [emerg] SSL_CTX_set_cipher_list failedSSL_CTX_set_cipher_list("...") failed (SSL: error:1410D0B9:SSL routines:SSL_CTX_set_cipher_list:no cipher match)no cipher match nginx ssl_cipherserror:0A0000B9 no cipher matchnginx ssl_ciphers invalid
Seen on: Nginx SSL OpenSSL

Meaning

Use a valid OpenSSL cipher string (check with openssl ciphers -v 'STRING'), avoid copy-pasting TLS 1.3 suite names into ssl_ciphers (TLS 1.3 suites are configured separately), and remove ciphers removed in OpenSSL 3. Use Mozilla's SSL Configuration Generator as a baseline.

Common causes

  • Typos or unknown cipher names
  • TLS 1.3 suite names in ssl_ciphers
  • Cipher removed in the OpenSSL build
  • Stray whitespace/newlines in the value
  • Config copied from an old guide

⚡ Quick fix

  1. Validate: openssl ciphers -v "ECDHE+AESGCM"
  2. Use a Mozilla-recommended list
  3. Run nginx -t after each change

Detailed fix by platform

Nginx

  1. nginx
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384;
    ssl_prefer_server_ciphers off;

How to diagnose

  1. Cipher string — Valid?
  2. TLS 1.3 — Separate?
  3. Syntax — 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:

Where this error sits

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

405 — 405 Not Allowed when POSTing to a static page or file (nginx) (HTTP)405414 Request-URI Too Large / 400 Request Header Or Cookie Too Large — Nginx: 400 Bad Request — Request Header Or Cookie Too Large / client sent too long header line (Nginx / Apache)414 Request-URI Too L…494 — nginx 494 Request Header Or Cookie Too Large (HTTP)494499 Client Closed Request / client prematurely closed connection — Nginx: [info] client prematurely closed connection while reading response header from upstream / access log status 499 (Nginx / Apache)499 Client Closed Req…accept4() failed (24: Too many open files) — Nginx: [crit] accept4() failed (24: Too many open files) / open() failed (24: Too many open files) (Nginx / Apache)accept4() failed (24:…AH00526: Syntax error on line of apache config — Apache: AH00526: Syntax error on line 12 of /etc/apache2/sites-enabled/site.conf: Invalid command 'Foo', perhaps misspelled or defined by a module not included in the server configuration (Nginx / Apache)AH00526: Syntax error…AH00548: NameVirtualHost has no effect — Apache: [core:warn] AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/ports.conf:5 (Nginx / Apache)AH00548: NameVirtualH…bind() failed (98: Address already in use) — nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) (Linux)bind() failed (98: Ad…ssl_ciphe…

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.