ERR_CONNECTION_RESET on wired network, but fine on cell
Reported by
ata...@gmail.com,
Jan 27 2018
|
|||||
Issue description
Chrome Version : 63.0.3239.132
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) : en.comparis.ch
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari:
Firefox:
IE/Edge: FAIL
What steps will reproduce the problem?
1. On my home wired network this website doesn't open. On other n
What is the expected result?
See the website
What happens instead of that?
ERR_CONNECTION_RESET
Please provide any additional information below. Attach a screenshot if
possible.
I'm attaching a dump fronm net-internals and wireshark. I guess it's a misconfiguration of web-site or my network, but
a) all the other sites work
b) this site works from cell network
Seems like the problem is somewhere with SSL, but I don't understand details enough to figure out in which direction to dig.
Thank you!
UserAgentString: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
,
Jan 29 2018
,
Jan 29 2018
Nothing stands out from chrome-net-export-log.json. SocketBIOAdapter::BIORead() fails to read from the socket. Could be a network issue, like firewall. What happens if you temporarily disable your antivirus? Can you open the website using another browser?
,
Jan 30 2018
This happens both on Desktop PC as well as mobile chrome connected to the same router. So likely the router is the problem. Disabling firewall on the router didn't fix the problem though. I tried IE it can't display the website as well. It seems like it's not really a Chrome problem, but I was wondering if this is a well known ssl certificates problem that you would recognize. Too bad it isn't =(
,
Jan 30 2018
Thank you for providing more feedback. Adding requester "bnc@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
,
Jan 30 2018
Thank you for your feedback. Since reading from the socket fails, I do not get the impression that this problem is SSL related. I'm closing this issue as WontFix because the root cause does not seem to be in Chrome. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ata...@gmail.com
, Jan 27 2018492 KB
492 KB View Download