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 also 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

Further to my gmail SSL problem on my desktop, all is working correctly on
my wifi-connected laptop, as opposed to direct internet connection to the
router  (BT Homehub 3)
Have sent a log to this bug id number.

Thanks,

Don Scott

[image: Mailtrack]
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality6&>
Sender
notified by
Mailtrack
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality6&>
13/10/18,
11:46:28

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The log didn't get attached. Could you go to the webpage at https://bugs.chromium.org/p/chromium/issues/detail?id=894778 and attach it there? Thanks!

Also, are you running Kaspersky antivirus on your machine? We've got some reports that they may have shipped a bad update recently and broke some stuff.

The reported responded to me privately with a NetLog and confirmed they were running Kaspersky 2018. The NetLog says Kaspersky is resetting the connection on us.

I'll go ahead and merge this with the other Kaspersky bugs.