ERR_SSL_VERSION_OR_CIPHER_MISMATCH — Fix Guide 2026

Enterno.io Editorial Team

ERR_SSL_VERSION_OR_CIPHER_MISMATCH: Causes & Fix

By Anatoly Oshmanovsky · Updated Apr 17, 2026

Key idea:

ERR_SSL_VERSION_OR_CIPHER_MISMATCH means the browser could not negotiate a TLS version or cipher with the server. Causes: server on outdated TLS 1.0/1.1 (Chrome 84+ disabled them), weak ciphers (RC4, 3DES), or SHA-1-signed certificate. Fix: enable TLS 1.2/1.3 and modern ciphers (ECDHE-ECDSA-AES128-GCM-SHA256).

This error blocks HTTPS access. Below: causes, fixes, working config, FAQ.

Try it now — free →

Common Causes

Server only supports TLS 1.0/1.1 (Chrome 84+ disabled them)
Weak ciphers in config: RC4, 3DES, EXPORT
Certificate signed with SHA-1 (Chrome rejects since 2017)
SNI mismatch (server returned a cert for a different domain)
Incompatible ECC curves (P-256/P-384 required)

Step-by-Step Fix

Upgrade nginx/Apache and enable TLS 1.2+1.3: ssl_protocols TLSv1.2 TLSv1.3;
Replace ciphers with modern ones: ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256;
If cert is SHA-1 — reissue with SHA-256 via Let's Encrypt for free
Inspect the TLS via Enterno.io SSL Checker to see TLS, ciphers, signature
After edits: nginx -t && systemctl reload nginx

Check SSL Certificate →

Example: Proper nginx TLS config

server {
    listen 443 ssl http2;
    server_name example.com;

    ssl_certificate     /etc/letsencrypt/live/example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;

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

    ssl_stapling        on;
    ssl_stapling_verify on;
}

Related SSL Errors

CertificateExpiry, issuer, domains (SAN)

ChainIntermediate and root CA validation

TLS ProtocolTLS version and cipher suite

VulnerabilitiesHeartbleed, POODLE, weak ciphers

Why teams trust us

TLS 1.3

supported

Full

CA chain check

<2s

result

30/14/7

days-to-expiry alerts

How it works

Enter domain

TLS chain verified

Expiry date & vulnerabilities

What Does the SSL Check Cover?

SSL/TLS is the encryption protocol that protects data between the browser and server. Our tool analyzes the certificate, chain of trust, TLS version, and knownvulnerabilities.

Certificate Details

Issuer, validity period, signature algorithm, covered domains (SAN), and validation type (DV/OV/EV).

Chain of Trust

Full chain verification: from leaf certificate through intermediates to root CA.

TLS Analysis

Protocol version (TLS 1.2/1.3), cipher suites, Perfect Forward Secrecy (PFS) support.

Expiry Alerts

Set up a monitor — get Telegram and email alerts 30/14/7 days before expiration.

DV vs OV vs EV Certificates

DV (Domain Validation)

Confirms domain ownership only
Issued in minutes automatically
Free via Let's Encrypt
Suitable for most websites
Most common certificate type

OV / EV

Organization (OV) or Extended Validation (EV)
Issued in 1-5 business days
Costs $50 to $500/year
For finance, e-commerce, government sites
Increases user trust

Who uses this

DevOps

SSL certificate monitoring

Security

TLS config audit

SEO

HTTPS as ranking factor

E-commerce

customer trust

Common Mistakes

❌

Expired certificateBrowsers block sites with expired SSL. Set up auto-renewal or monitoring.

❌

Incomplete certificate chainWithout intermediate CA, some browsers and bots cannot verify the certificate.

❌

Mixed content on HTTPS siteHTTP resources on an HTTPS page — the browser lock icon disappears, reducing trust.

❌

Using TLS 1.0/1.1Legacy TLS versions have known vulnerabilities. Use TLS 1.2+ or 1.3.

❌

Domain mismatch in certificateThe certificate must cover all site domains, including www and subdomains.

Best Practices

✓

Set up auto-renewalLet's Encrypt + certbot with cron — certificate renews automatically every 60-90 days.

✓

Enable HSTSStrict-Transport-Security header forces browsers to always use HTTPS.

✓

Use TLS 1.3TLS 1.3 is faster (1-RTT handshake) and safer — legacy ciphers removed.

✓

Monitor expiration datesCreate a monitor on Enterno.io — get notified well before expiration.

✓

Verify chain after renewalAfter certificate renewal, confirm that intermediate certificates are installed.

Get more with a free account

SSL certificate monitoring, check history and alerts 30 days before expiry.

Learn more

How-to

Glossary

Research

TLS Cipher Suites 2026: Distribution Report

Errors

Alternatives

Frequently Asked Questions

How do I check what TLS the server supports?

Use <a href="/en/ssl">Enterno.io SSL Checker</a> or on the shell: <code>openssl s_client -connect example.com:443 -tls1_2</code>. If it errors — TLS 1.2 is not supported.

Can I bypass the error via Chrome flags?

No safe way. Enabling TLS 1.0/1.1 in Chrome is not supported since 2020. Fix the server.

What if the server is managed by the hosting provider?

Contact hosting support — ask them to enable TLS 1.2+1.3 and disable SSLv3/TLS 1.0/1.1. Serious hosts do it in 1–2 hours.

Why does SNI matter here?

SNI (Server Name Indication) tells the server which domain was requested so it returns the right certificate. Without SNI the server sends the default cert, often with the wrong name → mismatch.