New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 761821 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

ERR_SSL_VERSION_INTERFERENCE with Chromium 60.0.3112.113

Reported by denc...@gmail.com, Sep 4 2017

Issue description

Chrome Version       : 60.0.3112.113
OS Version: 6.1 (Windows 7 SP1)
URLs (if applicable) : https://mail.google.com/
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 55.0.2 (32-bit): OK
     IE 11.0.9600.18762: OK

What steps will reproduce the problem?
1. Go to https://mail.google.com/ and press enter

What is the expected result?
The Google Mail page should be loaded

What happens instead of that?
The following error message is displayed:

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.

I'm using Chromium v60.0.3112.113 (64-bit)
 
UserAgentString: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36



 
mail.google.com error.png
65.8 KB View Download
Cc: sc00335...@techmahindra.com
Components: Internals>Network>SSL
Labels: Needs-Triage-M60 Needs-Feedback Triaged-ET
Tested the issue on 60.0.3112.113 with steps mentioned below on Windows7, Ubuntu 14.04 and Mac 10.12.6 and is not reproducible.

1.Navigated to https://mail.google.com/ and press enter
2.Successfully navigated to Gmail Sign in page

@dence81: This probably routed to network connection,so requesting you to please attach a NetLog per these instructions for further investigation.
https://dev.chromium.org/for-testers/providing-network-details

Adding appropriate component for respective team to triage this further.

Thanks!
Status: Untriaged (was: Unconfirmed)
-> Untriaged (which we weirdly use for things that have gotten initial triage).

Owner: svaldez@chromium.org
Status: Assigned (was: Untriaged)
In addition to collecting a net-internals trace, can you go to chrome://flags/#tls13-variant and set it to "Enabled (Experiment)" and see whether that fixes your issue. If you have time, can you also try setting it to the other values of Enabled (RecordType, NoSessionID, Draft), and see which of those fix your issue.

Comment 4 by denc...@gmail.com, Sep 5 2017

Please refer to the attached chrome-net-export-log.json file for the NetLog dump. I also tried accessing chrome://flags/#tls13-variant but it's just showing the same contents when browsing chrome://flags/. The "tls13-variant" flag is not available in my Chromium 60.0.3112.113 (64-bit).
chrome-net-export-log.json
1.6 MB View Download
Status: WontFix (was: Assigned)
You appear to be running an unofficial Chromium build with all experiments enabled. In particular, you've got the TLS 1.3 experiment enabled which we had to roll back in M60 due to buggy middleboxes. I'm guessing you've got one such middlebox. (If you could answer the question on what you've got, it would be helpful.)

You can work around this by disabling TLS 1.3 in chrome://flags (look for "TLS version" in there), but running an official build is more likely to be stable.

Comment 6 by denc...@gmail.com, Sep 6 2017

Thanks to all of you for helping me with this issue. I disabled TLS 1.3 as suggested by Ben and can now access https sites.

By the way, I'm using a portable launcher for Chromium that has a built-in updater (from this GitHub page: https://github.com/henrypp/chrlauncher).

I will also try to disable some of the experimental features when I have some spare time.

Sign in to add a comment