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

ERR_SSL_PROTOCOL_ERROR

ERR_SSL_PROTOCOL_ERROR in Google Chrome: secure connection error

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

The secure (TLS) connection between Chrome and the site failed with a protocol error. Try other HTTPS sites and another network, update Chrome and check your firewall or antivirus; if only this site fails, tell its operator.

Safety first

Stop and check this first

  • Do not enter passwords or payment details on that site while the secure connection is failing.

Safe checks you can perform

  • Other HTTPS sites
  • Updated Chrome and Incognito mode
  • Firewall and antivirus
  • The server's TLS negotiation

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Test the TLS configuration
  • Do not attempt this professional task: Review traffic inspection on the device

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. Test the TLS configuration

    What they doThe operator runs a TLS negotiation test against the server and reviews its error logs.

    They must show youthe test result with accepted versions and ciphers.

    In writingthe setting corrected.

  2. Review traffic inspection on the device

    What they doThe administrator checks whether the antivirus or firewall inspects that device's secure connections.

    They must show youthe setting or log involved.

    In writingthe change applied.

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. Other HTTPS sites

    No special tools

    Who:
    you.
    How:
    open several well-known sites that start with https.
    Result that matters:
    whether the error is only on this site.
    If many HTTPS sites fail:
    it points to your device or network; check the security software.
    If only this one fails:
    rule out your device in general and test from another network.
    Evidence to keep:
    sites tried and their result.

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

  2. Updated Chrome and Incognito mode

    No special tools

    Who:
    you.
    How:
    update and restart Chrome; then open the address in Incognito.
    Result that matters:
    whether the error remains with Chrome current and no extensions.
    If it goes away:
    the version or an extension was the cause.
    If it persists:
    rule out the browser.
    Evidence to keep:
    Chrome version and the Incognito result.

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

  3. Firewall and antivirus

    No special tools

    Who:
    you, on your personal device.
    How:
    check whether your antivirus or firewall logs a block or an inspection of the connection to that site.
    Result that matters:
    whether the software steps into that connection.
    If it shows in its log:
    it is the main suspect; review its settings.
    If it does not show and the site also fails on another network:
    it points to the server.
    Evidence to keep:
    a screenshot of the software log with the time.

    On a company device, stop and leave the check to the administrator.

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

  4. The server's TLS negotiation

    Tools required

    Who:
    the site operator.
    How:
    test the TLS negotiation against the server with a diagnostic tool and review the server logs at the time of the failure.
    Result that matters:
    whether the server completes the negotiation with a current client.
    If it fails with any client:
    the server's TLS configuration is the cause.
    If it completes normally:
    the failure is on the visitor's path or device.
    Evidence to keep:
    the TLS test output with the date.

    Only the site operator. If you do not run it, do not tamper with certificates or configuration: report with the time.

    Evidence: Chromium source - net/base/net_error_list.h (network error list) · 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_PROTOCOL_ERROR
  • ERR_SSL_PROTOCOL_ERROR (-107)
  • ERR_SSL_PROTOCOL_ERROR Chrome
  • net::ERR_SSL_PROTOCOL_ERROR

What it means

Chromium defines ERR_SSL_PROTOCOL_ERROR (-107) as an SSL protocol error, SSL being the older name for TLS. TLS 1.3 (RFC 8446) is the protocol that sets up the secure channel between client and server. This code is in the connection error range and does not say which step of the negotiation failed or which side caused it. Chrome's general help for connection errors lists, among other factors, the device firewall or antivirus and problems on the website.

Warnings and stop conditions

  • Mediumeditorial warning

    Do not enter passwords or payment details on that site while the secure connection is failing.

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

Symptoms and causes

Probable causes · in order

  • Server TLS configurationPossible

    If the error appears on several devices and networks with this site only, the problem is at the server.

    Evidence: Chromium source - net/base/net_error_list.h (network error list) · RFC 8446 - The Transport Layer Security (TLS) Protocol Version 1.3

  • Firewall or antivirus stepping inPossible

    If other HTTPS sites also fail on this device but not on another, security software may be involved.

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

  • Extension or outdated browserLess common

    Ruled out with Chrome up to date and a test in Incognito.

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

Virtual technician

Does ERR_SSL_PROTOCOL_ERROR 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 - Fix connection and loading errors 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 - Fix connection and loading errors in Chrome · RFC 8446 - The Transport Layer Security (TLS) Protocol Version 1.3reviewed 2026-10-03 · verified

Was this entry useful?