Chrome browser receiving "unexpectedly closed the connection.ERR_CONNECTION_CLOSED" error only when trying to reach google.com
Reported by
perfetto...@gmail.com,
Feb 21 2017
|
||||
Issue description
<b>Chrome Version : <Copy from: 'about:version'></b>
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: Did not try
Firefox 4.x: OK
IE 7/8/9: OK
What steps will reproduce the problem?
1. Attempt to go to https://google.com
2.
3.
What is the expected result? The google web page will show in my browser
What happens instead of that?
Please provide any additional information below. Attach a screenshot if
possible.
,
Feb 21 2017
Hello, I encounter the same issue when trying to hit https://cert-test.sandbox. google.com Also, this is a corporate office with multiple firewalls and proxy setups. Everything seems to be running correctly in all browsers. Multiple users are having difficulties with chrome specifically. And the only site that chrome seems to choke on is the https://google.com site. Only chrome seems to have the issue going to google. I was hoping that the included net-internals-log.json file would allow for a more specific indication of the issue I could go to my network folks with. Thanks, Jason Perfetto
,
Feb 21 2017
Could one of the users with the problem visit: https://tls.ctf.network/test694553 They should get a 404 error if its working correctly, or else a PROTOCOL_ERROR.
,
Feb 21 2017
I am receiving the same "ERR_CONNECTION_CLOSED" error as when I try to hit google.com. I have attached the log file from the chrome://net-internals application
,
Feb 21 2017
What proxy and firewalls do you use? (Product name/vendor and software version if you have that available.) This is likely caused by a bug in one of those products.
,
Feb 28 2017
,
Mar 9 2017
Network bug triager here. Archiving due to inactivity. perfetto.jason@ if you still have the issue, please file a new bug with the information requested in comment #5. |
||||
►
Sign in to add a comment |
||||
Comment 1 by svaldez@chromium.org
, Feb 21 2017Components: Internals>Network>SSL