ERR_SSL_VERSION_INTERFERENCE Mail:- thise can't be reached at this time SSL error
Reported by
sa...@canopysedge.com.au,
Oct 17
|
||||||
Issue description
Chrome Version : 69.0.3497.100
OS Version: 10.0
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari:not tried
Firefox:not tried
IE/Edge:ok
What steps will reproduce the problem?
1.reload
2.google search of mail.login
3.
What is the expected result?
This site can't be reached etc.
What happens instead of that?
nothing
Please provide any additional information below. Attach a screenshot if
possible.
This only happened midway through the day. I had been working in wordpress and added a contact page module to a new page.
UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36
,
Oct 18
,
Oct 18
ERR_SSL_VERSION_INTERFERENCE What else do you need to know? I have encountered this error with other sites as well. Same with F/fox but not on IE Bruce. Kind Regards, Sales Centre Canopy's Edge W : www.canopysedge.com.au Address: 2 Ashwood Circuit, Smithfield QLD 4878 T : +61.7.4038 3888 F : +61.7.4038 3777
,
Oct 18
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
,
Oct 18
@Reporter: This is likely due to a buggy antivirus, firewall, or proxy on your machine or network. As mentioned in comment #2 you are running Kasperksy antivirus? 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. 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. CC'ing Dev for further inputs on it.
,
Oct 24
Kaspersky recently released a patch to fix their update. If you are still experiencing the issue, please try updating your Kaspersky AV install. If you aren't using Kaspersky or the problem remains after the update, please let us know the previously requested information. Otherwise, we'll close this bug in a couple days, feel free to file a new bug if you continue experiencing issues after the bug gets closed.
,
Oct 25
Thank you for the follow up. It seems that the error fixed itself. I don't know how. Thanks again. Kind Regards, Sales Centre Canopy's Edge W : www.canopysedge.com.au Address: 2 Ashwood Circuit, Smithfield QLD 4878 T : +61.7.4038 3888 F : +61.7.4038 3777
,
Oct 25
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
,
Oct 25
Probably you all were running Kaspersky and picked up the update. They shipped a bad update a few weeks ago (there was no change in Chrome, this was purely a change on their end). |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dtapu...@chromium.org
, Oct 17Labels: Needs-Feedback