mail.google.com can't be reached
Reported by
nicholas...@gmail.com,
Mar 21 2018
|
|||||||
Issue descriptionChrome Version : 65.0.3325.162 OS Version: 6.1 (Windows 7, Windows Server 2008 R2) URLs (if applicable) : mail.google.com Other browsers tested: internet explorer Add OK or FAIL after other browsers where you have tested this issue: Safari: Firefox: IE/Edge: ok What steps will reproduce the problem? 1. trying to access mail.google.com 2. 3. What is the expected result? Load my gmail home page What happens instead of that? A blank page with the following message This site can’t be reached mail.google.com is currently unreachable. Try: Checking the connection Checking the proxy and the firewall ERR_SSL_VERSION_INTERFERENCE Please provide any additional information below. Attach a screenshot if possible. UserAgentString: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36
,
Mar 21 2018
,
Mar 21 2018
What firewall are you using? We've seen a number of buggy firewalls, and while most have distributed fixes, there are a couple that need manual adjustment (until they get a patch out). It would also be helpful to get a net-internals log when you reproduce the issue, see details here: https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details
,
Mar 21 2018
Thanks for the report! To help us diagnose this, could you attach a NetLog per these instructions? https://dev.chromium.org/for-testers/providing-network-details Additionally, do you have some kind of firewall, antivirus, etc. on your machine network? If so, which is it? This is typically caused by a defective middleware product of that sort.
,
Mar 23 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 23 2018
We've had some reports of issues with Avast that got fixed when updating to the latest version or reinstalling somehow. Does that work? Ultimately, this is caused by a bug in some firewall, antivirus, etc., that got triggered when we started to deploy a newer, faster, and more secure version of TLS.
,
Apr 26 2018
nicholas.salnikoff@, please let us know if updating Avast solved the issue. Thank you!
,
Apr 30 2018
Deleting it did solve the issue! Thank you.
,
Apr 30 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 30 2018
Cool, thanks for verifying. Closing this bug. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by krajshree@chromium.org
, Mar 21 2018