We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
Solved
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 disabled firewalls and the whole Eset Security. I've checked my ports. Everything is fine. I've turned off the proxy setting inside app. Scanned my system for viruses, nothing fount. The only solution is to revert back to the older version, but if I do so, the app will update itself so I'm at the beginning.
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!
440 Replies
Replies have been turned off for this discussion
Gonna test it now.. and it seems it kinda work :white_check_mark: Gonna check to see. For does who are here before install don't change anything in firewall settings,router,system date&time of PC, I've checked.
Hope it all stays good :speak_no_evil:Здравствуйте. Удалось устранить проблему? У меня аналогичная ситуация.
Thank you very much. I was banging my head against the wall and dropbox support claimed it was my system time which was off by 1 second max. My god... Thumbs up!
br,
bysaRD
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
Installed the beta version, but unfortianly it didn't work for me. Same problem again.
Lo stesso problema sul mio PC con NOD32 risolto leggendo qui
https://forum.eset.com/topic/26665-issue-after-installing-latest-version-of-dropbox-1114472/
- Daphne
Dropbox Community Moderator
Hey again everyone, glad to see most have resolved the issue with the steps posted here!
For any that are new to this thread, or still having trouble with this, here are the suggested steps:
- Try the beta version of the desktop app, which you can find here.
- If the beta doesn't resolve this, and you're running ESET, please check out Walter's post here.
As always, please don't hesitate to give me a nudge if the issue persists, or you have any questions - thanks!
- Daphne
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!
It works now.
I never installed the beta version and just waited for the fix.
Got a lovely surprise this morning. No little red mark re secure connection and a DB updated!
I'd been holding out. Didn't change any ESET settings or install Beta version DB. Glad now.
Am sure the community's unceasing pressure is responsible for the solution having been found after a very frustrating week. So we all deserve a huge round of applause!
