Like we just discussed, as far as the reason that Google sometimes says “This site can’t provide a secure connection,” it’s almost impossible to pin it down to a single cause.
Heck, I’ve gotten one on here, on our website, and I can assure you our SSL/TLS configuration is up to snuff. The SSL errors can pop up on the most popular sites as well as on the least ones. The frustrating thing about this error (family of errors, really) is that there’s no easily discernible cause behind it a lot of the time. If Google Chrome is your window to the world of the internet, you must have encountered a “This site can’t provide a secure connection” error or an ERR_SSL_PROTOCOL_ERROR message at least once. But, from looking at the Dropbox forum, it appears that the Dropbox version 111 was the problem.In Everything Encryption A quick guide on how to fix Chrome’s ‘This site can’t provide a secure connection’ or ‘ERR_SSL_PROTOCOL_ERROR.’ So thought it might be an Microsoft interaction. I could not find release notes for Dropbox's desktop version 112.īut, the Dropbox users in the Dropbox forum that Rjanata linked to (in quote above) believed that it was the install of Dropbox v111 that was the cause.įYI-I'm running Eset 14.0.22.0 and Win10 圆4 and had just completed Microsoft Win10 update KB4592428 the night before I had the problem. Installing Dropbox desktop version 112 worked for me, too. If you cannot update to Dropbox version 112, you can temporarily set Dropbox client to ignore in SSL/TLS filter. It's apparently a problem on Dropbox side since they have release the version 112 fixing this issue:
On the second computer, no problem with Dropbox v112 (early updates enabled). Same problem here (Dropbox v111 - the lastest stable to the date).
0 kommentar(er)
