Multiple websites fail to load until after refreshing the page multiple times. Maybe not Chrome issue, seeking assistance regardless.
Reported by
fluter...@gmail.com,
Apr 8 2018
|
|||||||
Issue descriptionChrome Version : 65.0.3325.181 OS Version: 10.0 URLs (if applicable) :https://mspfa.com/, https://armorgames.com/, http://invisiblebread.com/, others probably. Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari: Do not have; using Windows system Firefox: Do not have IE/Edge: FAIL What steps will reproduce the problem? 1. Visiting these websites What is the expected result? Accessing the website What happens instead of that? I am informed that I can not access the website, wither because it is unreachable (ERR_SSL_VERSION_INTERFERENCE on chrome, INET_E_DOWNLOAD_FAILURE on Edge) or because the connection was reset if on chrome/it can't connect securely if on Edge. UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
,
Apr 9 2018
,
Apr 9 2018
Can you include a NetLog dump, as per https://www.chromium.org/for-testers/providing-network-details Are you using any Antivirus products? Are you on a corporate network that may have additional enterprise network devices?
,
Apr 9 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 9 2018
mspfa.com and invisiblebread.com are Cloudflare TLS 1.3 sites. I don't think we've had reports of AVG causing problems with TLS 1.3, however, and other parts of your report don't match a TLS 1.3 issue: - armorgames.com does not speak TLS 1.3 (though it does appear to be Cloudflare). - You're seeing issues in Edge too, right? Edge has not deployed TLS 1.3 yet. - While invisiblebread.com is a Cloudflare TLS 1.3 site, you're not connecting to it over HTTPS in the first place, just plain HTTP. - id:1251332 shows a working TLS 1.3 connection to www.facebook.com. Thus this doesn't appear TLS-1.3-related or even TLS-related in general. ERR_SSL_VERSION_INTERFERENCE appears to just a false positive. That it's also broken in Edge indeed suggests it's not a Chrome problem. We often see issues with anti-virus, so my immediate suggestion is to try disabling AVG and see if that improves things.
,
Apr 9 2018
Turning off AVG doesn't seem to improve things, and neither does turning off Windows Defender. And yes, I'm having issues with Edge too.
,
Apr 9 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 11 2018
I don't think there's anything we can do here. We establish a connection, send some data a couple milliseconds later, and soon after the connection is reset. It happens for HTTP and HTTPS requests, so it's not SSL. It's a reset, so it's not an error we produce directly, or have any real control over. flutercat: I'm sorry, but I think this is either a local configuration issue, or an issue with something directly upstream of you. I don't see any way Chrome could be modified to not get a reset on your network, seeing as this happens for both HTTPS and HTTP requests, it seems unlikely to be caused by anything we're doing. So I'm going to go ahead and close this issue. Wish I could do something to help - something clearly is amiss. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by krajshree@chromium.org
, Apr 8 2018