Assigning the issue to svaldez@ owner from similar bugs    819598   ,  823165  and   820297 .

svaldez@: Requesting to please have a look into the issue and help further.

Thanks...!!

This is likely due to a buggy middle-box on your network blocking newer versions of TLS (TLS 1.3). Do you know if you have any anti-virus/proxy/firewall products installed that might be causing issues?

It may help us to get a net-internals log of what occurred if you can reproduce it, see details here:
https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details

Ping reporter, can you respond to comment #3?

This is not occurring anymore, therefore I cannot test it.

At the time it happened, I was accessing the website from a Mac in the UK and a friend was accessing it from a Windows in Brazil and we were having the same issue. And only on Chrome and Safari.

Archiving as the issue cannot be reproduced any more per comment #5. Please feel free to reopen if you can answer the questions in #3.

I am having this issue all the time, just started out of the blue today! Was using tls 1.3 with no issues for months. I think there is a middle box attempting to depreciate TLS.

ERR_SSL_VERSION_INTERFERENCE errors began occuring in Chrome and Firefox. 7 out of 10 attepts to connect to HTTPS servers results in this error. Though I have enabled only TLS 1.2 and up, ssllabs test confirms TLS 1.1, 1.0, and SSL3 are all in use. The test does not always use the same results, other times it shows only TLS 1.2, and 1.3.

Wireshark data: Note TLSV1 Record Layer, TLS 1.0, contains TLS 1.2 version within the handshake protocol. What is going on here? I disabled TLS 1.0 in Chrome yet this still gets through. Interestingly "Pale Moon" doesn't result in cipher depreciation.

Frame 23482: 571 bytes on wire (4568 bits), 571 bytes captured (4568 bits) on interface 0
Internet Protocol Version 4, Src: 192.168.50.241 (192.168.50.241), Dst: 173.194.152.121 (173.194.152.121)
Transmission Control Protocol, Src Port: 50941 (50941), Dst Port: https (443), Seq: 1, Ack: 1, Len: 517
Secure Sockets Layer
    TLSv1 Record Layer: Handshake Protocol: Client Hello
        Content Type: Handshake (22)
        Version: TLS 1.0 (0x0301)
        Length: 512
        Handshake Protocol: Client Hello
            Handshake Type: Client Hello (1)
            Length: 508
            Version: TLS 1.2 (0x0303)
            Random: db373b22e4ed92614a1c8da5cc8a82e96645f383a9fc2c33...
            Session ID Length: 32
            Session ID: 5e189d6737643c7881af28c7725596ca5466ec8f4fdd8140...
            Cipher Suites Length: 24
            Cipher Suites (12 suites)
            Compression Methods Length: 1
            Compression Methods (1 method)
            Extensions Length: 411
            Extension: Reserved (GREASE) (len=0)
            Extension: renegotiation_info (len=1)
            Extension: server_name (len=37)
            Extension: extended_master_secret (len=0)
            Extension: SessionTicket TLS (len=0)
            Extension: signature_algorithms (len=20)
            Extension: status_request (len=5)
            Extension: signed_certificate_timestamp (len=0)
            Extension: application_layer_protocol_negotiation (len=14)
            Extension: ec_point_formats (len=2)
            Extension: key_share (len=43)
            Extension: psk_key_exchange_modes (len=2)
            Extension: supported_versions (len=7)
            Extension: supported_groups (len=10)
            Extension: Unknown type 27 (len=3)
            Extension: Reserved (GREASE) (len=1)
            Extension: padding (len=198)

FYI I am getting the same error on the above link you provided.

Please file a new ticket and provide a NetLog per these instructions:
https://dev.chromium.org/for-testers/providing-network-details

(Wireshark showing TLS 1.0 and 1.2 in there are red herrings. Due to a series of workarounds for buggy servers, there are a lot of frozen version fields in TLS.)