We're making changes to the Community, so you may have received some notifications - thanks for your patience and welcome back. Learn more here.
Forum Discussion
Cannot establish a secure connection after dropbox update to 111.4.472
After the dropbox app (Window 10) updates itself to the latest 111.4.472 version, I'm getting this 'Cannot establish a secure connection'.
I've checked my time on my laptop, router. It's fine. I've...
I've just received some news that I'd like to share with you all here!
It appears that ESET has fixed the problem that was causing this error.
For anyone running ESET on their device, please update to the most recent version of ESET to update to the software.
Once you've done this, you should be fine to revert back to the latest stable version of the Dropbox desktop app. You can install this from here.
Otherwise, you can just allow the app to auto-update to the latest stable when a new version is released.
Let me know how it goes!
I contacted Dropbox via messenger and received the answer within a few minutes. this is for all who use ESET and have the same problem "Cannot establish secure internet connection":
1. Open the main program window of your Windows ESET product
2. Press F5 to access Advanced setup
3. Click Web and Email
4. expand Protocol Filtering and then click the slider bar next to Enable application protocol content filtering to enable or disable this feature
5. Look for "Excluded applications" and click on Edit Add Dropbox and Dropbox Update
6. Click OK
Keep in mind that you may need to reboot your device, or quit / relaunch the app, for this to take effect.
In reply to Fran20201 Fran20201 (dropboxforum.com)
I arrived at the same solution via The Dropbox folder on your computer: errors and other messages | Dropbox Help
"
- Known issues with ESET Endpoint Security Solutions: This product may conflict with Dropbox when SSL scanning is enabled. Possible workarounds are to exclude the Dropbox certificate within the "Ask about non-visited sites" mode, as well as to exclude dropbox.exe from protocol filtering. "
Feel safer to learn that at least one other person has applied the same workaround! :-) I just applied the 'exclude from protocol' part.
Not clear why this error occurred now, as the last change I can find was the service module on the 6th December which appears to coincide with the initial reports on this forum.
Given that the latest beta is reported to also solve the issue, I would suggest backing out the above ESET workaround following the next production version update.
Chris
