ERR_SSL_VERSION_INTERFERENCE
Reported by
iv...@m2north.com,
Aug 28 2017
|
|||||||
Issue description
Chrome Version : 61.0.3163.59
OS Version: OS X 10.12.6
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x: OK
IE 7/8/9:
What steps will reproduce the problem?
1. Not sure
2.
3.
What is the expected result?
Page should open
What happens instead of that?
Error message ERR_SSL_VERSION_INTERFERENCE
Please provide any additional information below. Attach a screenshot if
possible.
UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.59 Safari/537.36
,
Aug 28 2017
Can you collect a net-internals trace? https://dev.chromium.org/for-testers/providing-network-details Do you know if you're running a proxy/firewall product on your network? Some products have known issues that interfere with newer version of TLS. Also, can you go to chrome://flags/#tls13-variant and set it to "Enabled (Experiment)" and see whether your connection works again. If that works and you have time, can you also try the other 'Enabled' settings and see which work? This will help us figure out the best variant of TLS 1.3 to deploy, to deal with middlebox/firewall bugs that are preventing deployment.
,
Aug 28 2017
,
Sep 1 2017
We use a FortiGate 70D: HA Status Standalone Host Name FGT70D3Z14000929 Serial Number FGT70D3Z14000929 Operation Mode NAT [Change] System Time Fri Sep 1 16:17:10 2017 (FortiGuard) Firmware Version v5.2.1,build618 (GA)
,
Sep 1 2017
Setting " chrome://flags/#tls13-variant and set it to "Enabled (Experiment)" worked!! Thanks
,
Sep 1 2017
Thank you for providing more feedback. Adding requester "mmenke@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
,
Sep 1 2017
,
Sep 4 2017
@ ivanj : As per comment#5.Could you please confirm can we close the issue. Thank You!
,
Sep 4 2017
,
Sep 5 2017
According to #5, this is fixed, though if you have a chance to try the other variants and report on which work, that would be useful in preparation of deploying this further. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by pbomm...@chromium.org
, Aug 28 2017Components: Internals>Network>SSL
Labels: M-61