ErrorBase
Independent technical referenceOfficial site
  • Software and digital services
  • Web browsers

ERR_SSL_VERSION_OR_CIPHER_MISMATCH

ERR_SSL_VERSION_OR_CIPHER_MISMATCH in Google Chrome: outdated site security

Verified with sources3 sourcesReviewed Oct 3, 2026
Technician coming? See the 2 steps they must show you

Risk level

Low

Usually safe to check without specialist tools.

Urgency

Medium

Quick answer

Chrome and the server share no TLS version or cipher, and Chrome blocks the connection to protect your privacy. You cannot fix it from the browser: tell the website owner.

Safety first

Stop and check this first

  • Do not use old browsers or insecure settings to reach a site that Chrome blocks for outdated security; your data would travel less protected.

Safe checks you can perform

  • Updated Chrome
  • The site from another network
  • Telling the website owner
  • Versions and ciphers the server offers

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Update the TLS configuration
  • Do not attempt this professional task: Verify the negotiation after the change

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Update the TLS configuration

    What they doThe operator sets the server to TLS 1.3 and TLS_AES_128_GCM_SHA256, as Chrome Help recommends, and can keep TLS 1.2 for older clients.

    They must show youthe TLS test before and after.

    In writingversions and ciphers enabled.

  2. Verify the negotiation after the change

    What they doThe operator repeats the connection with an updated Chrome and with the diagnostic tool.

    They must show youthe successful connection and the negotiated version.

    In writingdate of the test.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. Updated Chrome

    No special tools

    Who:
    you.
    How:
    update Chrome and restart it.
    Result that matters:
    whether the error remains with the latest version.
    If it goes away:
    it was the browser version.
    If it remains:
    rule out the browser; the problem is at the site or in the network.
    Evidence to keep:
    Chrome version.

    Evidence: Google Chrome Help - Fix connection and loading errors in Chrome

  2. The site from another network

    No special tools

    Who:
    you.
    How:
    open the address on mobile data or from another connection.
    Result that matters:
    whether the error depends on the network.
    If it works on another network:
    it points to a proxy or filter on your network; tell its administrator.
    If it fails everywhere:
    it confirms the server does not offer a compatible configuration.
    Evidence to keep:
    networks tried and result.

    Evidence: Chromium source - net/base/net_error_list.h (network error list)

  3. Telling the website owner

    No special tools

    Who:
    you.
    How:
    contact the site through another channel (email or phone) giving the exact code, the address and your Chrome version.
    Result that matters:
    that the owner gets the details needed to fix the server.
    If they reply they will fix it:
    wait for the fix; there is no safe step in your browser.
    If there is no contact channel:
    do not force the connection with other programs to enter data.
    Evidence to keep:
    a copy of the message sent.

    Evidence: Google Chrome Help - Get help with common error messages in Chrome

  4. Versions and ciphers the server offers

    Tools required

    Who:
    the server operator.
    How:
    check with a TLS diagnostic tool which versions and ciphers the server accepts.
    Result that matters:
    whether it offers TLS 1.3 with TLS_AES_128_GCM_SHA256 or at least TLS 1.2 with current ciphers.
    If it only offers old versions:
    that is the cause; update the configuration.
    If it already offers TLS 1.3:
    the failure is at an intermediary on the visitor's network.
    Evidence to keep:
    the test report with versions and ciphers.

    Only the server owner or operator. If you do not run it, do not do it.

    Evidence: Google Chrome Help - Get help with common error messages in Chrome · RFC 8446 - The Transport Layer Security (TLS) Protocol Version 1.3

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
Google Chrome
Product type
Web browsers

Known code variants

  • ERR_SSL_VERSION_OR_CIPHER_MISMATCH
  • ERR_SSL_VERSION_OR_CIPHER_MISMATCH (-113)
  • ERR_SSL_VERSION_OR_CIPHER_MISMATCH Chrome
  • net::ERR_SSL_VERSION_OR_CIPHER_MISMATCH

What it means

Chromium defines ERR_SSL_VERSION_OR_CIPHER_MISMATCH (-113) as the client and server not supporting a common SSL protocol version or cipher suite. Chrome Help explains that it appears with websites using outdated security code and that Chrome does not let you connect to them. In TLS 1.3 (RFC 8446), a failed negotiation is signalled with the handshake_failure alert. The fix is in the server's TLS configuration.

Warnings and stop conditions

  • Mediumeditorial warning

    Do not use old browsers or insecure settings to reach a site that Chrome blocks for outdated security; your data would travel less protected.

    Evidence: Google Chrome Help - Get help with common error messages in Chrome

Symptoms and causes

Probable causes · in order

  • Server with outdated versions or ciphersCommon

    This is what Chrome Help describes. Confirmed if the site fails on any device with an updated Chrome.

    Evidence: Chromium source - net/base/net_error_list.h (network error list) · Google Chrome Help - Get help with common error messages in Chrome

  • A device in between negotiating the connectionLess common

    If the site only fails on one particular network, a proxy or filter on that network may be negotiating for you with different parameters.

    Evidence: Chromium source - net/base/net_error_list.h (network error list)

Virtual technician

Does ERR_SSL_VERSION_OR_CIPHER_MISMATCH still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Start diagnosis

Sources and technical references

  1. 1

    Chromium source - net/base/net_error_list.h (network error list)

    The Chromium Authors · 2026 · official_doc

  2. 2

    Google Chrome Help - Get help with common error messages in Chrome

    Google · 2026 · official_doc

  3. 3

    RFC 8446 - The Transport Layer Security (TLS) Protocol Version 1.3

    IETF / RFC Editor · 2018 · standard

Sources: Chromium source - net/base/net_error_list.h (network error list) · Google Chrome Help - Get help with common error messages in Chrome · RFC 8446 - The Transport Layer Security (TLS) Protocol Version 1.3reviewed 2026-10-03 · verified

Was this entry useful?