ก็ดีครับ

Thanks for filing the issue.

@reporter: Could you please mention what is the error being displayed and also let us know which antivirus is being used on your system so that it would be really helpful for further triaging of the issue. 
Thanks.!

HI
  Error is :  ERR_SSL_VERSION_INTERFERENCE
 antivrus: Kaspersky internet security
 I have also attached the screenshort
 only when tsl 1.3 is disabled. gmail is working otherwise its not.
please I need gmail to work on chrome without disabling my antivrus and tsl
1.3, please revert with a solution

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

Thanks for the info!

We haven't changed anything with TLS 1.3 for Chrome 69 so there's nothing to revert. Rather, it seems that Kaspersky have shipped a bad update and broke something. We're going to find some contacts on their end to see if they can revert the mistake on their end.

Does it work if you disable "Scan encrypted connections"? That may let you disable a smaller portion of the broken software in the meantime.

By the way, your screenshot didn't get attached. You need to go to the web interface at https://bugs.chromium.org/p/chromium/issues/detail?id=895140 and attach it there.

Gmail is working when I disabled the scan encrypted connection,
Is the fault is from Kaspersky internet security or from chrome.
But, Is it safe to disable "scan encrypted connection"

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

(Duping this into the tracking bug since this is Kaspersky related).

Unfortunately it looks like a recent Kaspersky update (19.0.0.1088(c)) caused connections using TLS 1.3 to break, affecting both Chrome and some Firefox versions. We've reached out to our contacts at Kaspersky to try getting a timeline on when they'll release a fix. For now it seems like disabling the "scan encrypted connection" setting is the best short-term fix until Kaspersky releases a patch. We'll update the tracking bug ( crbug.com/895476 ) once we've heard back from Kaspersky.

Thanks for the information