There is no proxy activated.

Tried to create a new profile on chrome without any extensions, same error.

Not the first time it happened, it went away and now came back.

Setting the chrome flag 
Maximum TLS version enabled. Mac, Windows, Linux, Chrome OS, Android
Set maximum enabled TLS version. #ssl-version-max

to TLS 1.2

And it fixes the issue.

Setting the same flag to TLS 1.3 and it fails again.

I know there are other issues similar but they seem like they are a dead-end.

I have tried what the other people suggested in those other issues, and posted the results here.

Also people were asking for the net-export-log, I have attached it here.

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

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

This is a work network, we have Fortigate installed (but it is closed at the moment and error is present).

We are also using Symantec endpoint protection (both enabled and disabled and I have the issue).

I have the creator update of windows 10, which seemed to come with an update on windows security including firewall (just adding to try to push as much details as possible).

Thank For filing the issue! Tested in chrome # 59.0.3071.115, Beta #60.0.3112.50 and Canary #61.0.3147.0 on win 10.0 & 7 and not able to reproduce the issue.Please find the screen shots for your reference.Adding related dev team in 'CC' for further inputs.

@davidben /svaldez : As per your comments in below issues 
https://bugs.chromium.org/p/chromium/issues/detail?id=735104,
https://bugs.chromium.org/p/chromium/issues/detail?id=735337.
not merging this issue.Could you please look in to this issue.

Thank You!

Deleted: 738375.PNG 495 KB

	738375.PNG 495 KB View Download

Thanks for the extremely detailed report!

This is another access_denied alert from a buggy middlebox. We've seen that before from a bug in Fortigate, though it's possible other products have the same failure mode. I'm not aware of issues with Windows' firewall.

- What version of Fortigate's software are you running?

- When you say the Fortigate product is "closed at the moment" do you mean that it's not on your network at all or you've disabled all filtering rules? (It's possible that their bug occurs even when all filtering rules are enabled.)

My fortigate installed on my computer was off.

Don't know what we have on network. I can ask.



Étienne Rocheleau
etienne.rocheleau@gmail.com

Thank you for providing more feedback. Adding requester "rbasuvula@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

Is it critical to have the version of Forti running on the network?

I meant that I had closed off the program on my machine when the problem occured.

When you say the program was closed, do you mean FortiClient? But there is still a FortiGate device on your network, right?

We need details on the FortiGate device. Our previous reports were about a problem in that product.

Yes I meant the FortiClient was off on my machine.

Version for the FortiGate running on our networks: 5.2.8/5.2.10 (says it
depends on location)



Étienne Rocheleau
etienne.rocheleau@gmail.com

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

Does upgrading the device to 5.4.0 or later work? Fortinet previously told us that's where they fixed their bug. (Though we've had other reports which contradict this, so this may not actually be accurate.)

Do you mean FortiClient? or FortiGate?

I don't really think I can get IT to upgrade their whole system for that :(
Sorry.



Étienne Rocheleau
etienne.rocheleau@gmail.com

@davidben-- Could you please respond to the comment #15 and help us in triaging the issue.

Thanks!

@davidben-- Could you please look into this issue.

Thanks!

Um, there is pretty obviously nothing in comment #15 to respond to. There is a problem with the device, but the administrator does not wish to fix it.

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