Could you attach a NetLog per these instructions? Thanks!
https://dev.chromium.org/for-testers/providing-network-details

Also, what kind of network is this (home? work?). Do you have any antivirus, firewall, proxy, or other networking middleware products configured? If so, do you know which they are?

Will work if I attach the required log when the connection is working or you need it when it does not work? If so I've to wait til I run into the same issue again.

This is a work network. I don't have any AV nor Firewall. Regarding the firewall I think we have one on the middle but that's information I do not know since there is another offshore team handling that part.

Thank you for providing more feedback. Adding requester "davidben@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

The log should be when it's not working. This error happens because something on your network that is interfering with TLS 1.3, which we are currently experimenting with. If it's not currently happening, probably you restarted your browser and got rerolled into a different experiment group.

To reproduce more reliably, go to chrome://flags and:
1. Disable "Experimental QUIC protocol"
2. Set "Maximum TLS version enabled." to TLS 1.3

If you could find out from that team what kind of firewall you're using, that'd also be great.

Thanks!

Hi @david, I was able to reproduce the issue but this time it happened in another different URL: https://cdnjs.cloudflare.com/ajax/libs/free-jqgrid/4.14.1/jquery.jqgrid.src.js. I've attached the logs as requested. TLS 1.3 wasn't disabled for this test.

Deleted: chrome-net-export-log.json 243 KB

chrome-net-export-log.json 243 KB View Download

Thank you for providing more feedback. Adding requester "davidben@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Thanks! That log looks like you have a Watchguard box on your network. Their products have a bug that is interfering with us shipping performance and security improvements to your browser and the rest of Chrome users. ( Issue #733223 .)

Could you check IT folks at your company to confirm you have one of those boxes?

As a workaround, you should have them disable the "Allow only SSL compliant traffic" setting.
http://www.watchguard.com/help/docs/fireware/11/en-US/Content/en-US/proxies/https/https_general_settings_c.html

Any update on the feedback requested in comment #8?

Hi there, sadly I haven't any direct connection with the networking team and they are an offshore team so they aren't here in a daily basis, I can't provide you with the answer regarding the box. Moving back to TLS 1.2 makes everything to work should I switch back to 1.3 and make the changes as you suggested?

Thank you for providing more feedback. Adding requester "davidben@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

davidben@ - Could you please provide any update to the user as per comment #11.

Thanks...!!

Also I was able to reach a networking guy and he told me that in fact they are using a Watchguard box but that's it. He isn't allow to give me or change any kind of setup on that box. (company policies)

I see. Well, here is Watchguard's article on the problem. This is a flaw in their products. The workaround is to disable a (not very useful) setting. If you're not willing to do that, please open a support ticket with Watchguard so they know to prioritize fixing this bug.

https://watchguardsupport.secure.force.com/publicKB?type=KBKnownIssues&SFDCID=kA42A000000HASBSA4&lang=en_US