New issue
Advanced search Search tips

Issue 905541 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 5
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Unable to Connect to Gmail, but only in Chrome. Disabling Firewall doesn't fix.

Reported by yajie...@gmail.com, Nov 15

Issue description

Chrome Version       : 70.0.3538.102
OS Version: 10.0
URLs (if applicable) : https://mail.google.com/mail/?authuser=0
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari: OK
    Firefox: OK
    IE/Edge: OK

What steps will reproduce the problem?
1.Attempting to go to gmail.com in Chrome

What is the expected result?

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

What happens instead of that?


Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36



 
Components: Internals>Network>SSL
Cc: phanindra.mandapaka@chromium.org davidben@chromium.org
Labels: Needs-Feedback Triaged-ET Needs-Triage-M70
Thanks for the issue...

This is likely due to a buggy antivirus, firewall, or proxy on your machine or network. Are you running Kaspersky anti-virus? If so, does it work if you disable it, specifically the "Scan encrypted connections" setting? It seems they recently shipped a bad update and broke stuff.

Otherwise, what anti-virus, firewall, proxy, etc., do you run? It would also help us to get a NetLog of what occurred if you can reproduce it, see details here:
https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details.

Note: Reference Issue:    895155   and CC'ing Dev for further inputs on it. 

Thanks..!
[yajie9yu]:  I'm going to close this bug, as it's a likely duplicate of the  issue 895155  (Which Kaspersky has fixed on their end).  If you're still having this issue after updating Kaspersky, or don't have Kaspersky installed, please file a new bug.
Status: WontFix (was: Unconfirmed)

Sign in to add a comment