Device-specific

    ERR_SSL_VERSION_OR_CIPHER_MISMATCH on Chrome

    Why it happens on Chrome

    Chrome dropped TLS 1.0 and 1.1 and refuses RC4 and 3DES, so a server that still works in curl or an internal tool fails only in the browser.

    The fix on Chrome

    Run the SSL check below to see the highest protocol the server actually offers. If the answer is TLS 1.1 or lower, no browser fix exists — the server must enable TLS 1.2.

    Is ERR_SSL_VERSION_OR_CIPHER_MISMATCH happening on your domain?

    The SSL check enumerates exactly which protocol versions and suites the server accepts, turning guesswork into a list.

    Free, no signup. Runs from outside your network, which is the only way to tell a server fault from a local one.

    If that didn't fix it

    Chrome has its own failure mode, but ERR_SSL_VERSION_OR_CIPHER_MISMATCH has a wider set of causes that apply everywhere. The most common one overall is: the server only supports tls 1.0 or 1.1.

    All causes and fixes for ERR_SSL_VERSION_OR_CIPHER_MISMATCH

    ERR_SSL_VERSION_OR_CIPHER_MISMATCH on other platforms and devices

    Nginx
    Cloudflare

    Monitor this continuously with LemWatch

    A one-off err_ssl_version_or_cipher_mismatch monitoring shows you today. LemWatch re-runs the same checks around the clock and alerts you the moment something breaks — free for up to 10 sites, no card needed.

    Last verified: by the Lemwatch research team.