Thank you for reporting the problem. This looks like a duplicate of an existing  issue 735028  ( https://crbug.com/735028 ).

To help to resolve it, could you please collect the net-internals log while connecting to the site that cannot be open due to the error 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 are you connected to? (Is this your home network or work?) Are you behind any antivirus, firewall, proxy, or other networking middleware products? If so, which ones?

Thank you!

These shouldn't get merged until we find out the vendor.

punit.npia@ can you please let us know the vendor as requested in comment#2.

Thanks for the report!

Please provide us with more information about your network environment:

* 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.

Hi,

This is work network.

And i am having fortinet firewall as well as quickheal seqrite antivirus.

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

Sorry, I missed this somehow.

Thanks a lot for the information! We'd previously had some issues with Fortinet that we're still trying narrow down. Would you be able to share what model of Fortinet device you have and what version of the software is on it?

Finally, could you attach a NetLog of it happening per these instructions?
https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details

To reproduce the problem, you'll want to go to chrome://flags and set "Maximum TLS version enabled" to "TLS 1.3" and "Experimental QUIC protocol" to "Disabled".

Also, would you be able to test with only the antivirus or only then firewall somehow? That would help narrow down which of the two it is, though I currently suspect the Fortinet device. That's the common thread among many of the reports we've been getting.

Thanks!

punit.npia@, could you provide the information requested in comment #7 please? Thanks!

Closing since we need further information to debug, though we're running some alternative experiments in M61 to better understand these bugs.

If you still experience problems in M61, please re-file a bug (with any details about the middlebox/firewall/network appliances you can find and a net internals log of the problem (https://dev.chromium.org/for-testers/providing-network-details)).