Thank you for reporting the issue. Could you please collect the net-internals log while connecting to mail.google.com and attach the log to the bug? The instructions how to do that can be found here: https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details

Also, what kind of network is this? (Is this your home network or work?) Are you behind any antivirus, firewall, proxy, or other networking middleware products? If so, which ones?

Thanks!

 Issue 735104  has been merged into this issue.

 Issue 735337  has been merged into this issue.

antsweepstakes, can you please provide the information requested in #1 and #4? We need your help to make progress on the bug.

I have created another issue with similar problem and attached the logs you were asking for @csharrison

https://bugs.chromium.org/p/chromium/issues/detail?id=738937

Feel free to merge into this one.

etienne.rocheleau: Thanks for the report, and for filing a separate bug! (We'll keep it separate for now. We've been trying to categorize these by what vendors are affected, so we can better understand the problems here.)

Archiving.  antsweepstakes@, please file a new bug with the requested information if you are still having the issue.

Incredibly sorry for the non-responsiveness, I completely forgot that I made this report on an email I barely use. I'll just comment in the thread posted by etienne if I run into the problem again.

No worries. We shut off the experiment sadly due to bugs in networking and are starting a different one in M61. Though the experiment is off in M60, if you could answer the questions about your network in comment #4, that'd still be extremely helpful.

> due to bugs in networking

due to bugs in networking middleboxes

I don't have the problem anymore, is it still worth posting my logs? I don't really remember when it fixed itself but I was on vacation for 2 weeks and by the time I was back I had completely forgotten about the issue.

As for comment #4, this was on a work network behind a Watchguard Firebox M200 firewall.

RE #16, thanks.

http://www.watchguard.com/support/release-notes/fireware/11/en-US/EN_ReleaseNotes_Fireware_11_12_4/Fireware_Release-Notes_v11_12_4.pdf notes

"TLS 1.3 connections now operate correctly when a Firebox HTTPS proxy policy has content inspection disabled and is configured to allow non-compliant SSL connections. [93174]"

Thanks I changed the proxy to an older one and it worked but now I will
changed back the proxy and hope it work

El 11 ago. 2017 2:17 PM, "elawre… via monorail" <
monorail+v2.271331812@chromium.org> escribió: