Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
Mac OS Sequoia is arriving. Is DropBox ready?
Hi everyone, who remembers the chaos that happened last year with the Mac OS Sonoma update and all the issues we had with DropBox? There was a particular version that caused syncing to go haywire. I remember it all too well, as it took us almost a month to figure out how to fix the problem.
What will happen with Mac OS Sequoia? I admit, I'm quite anxious and would appreciate some reassurance from the DropBox team.
Thanks.
There is an update, see https://help.dropbox.com/installs/macos-support-for-expected-changes.
If you still have trouble, disable the firewall. https://9to5mac.com/2024/09/19/security-bite-macos-sequoias-filewall-is-disrupting-security-tools-and-more/ says most users should not enable the firewall:
"Details are sparse at the moment, but a possible source of the issues is Sequoia’s current firewall. This is useful for managing connections on untrusted networks. If you’re an everyday user and not a security nut or part of an enterprise team, your firewall is likely already off. This is the default on Mac, as most users are on trusted networks anyway (Apple’s way of balancing usability and security)."
69 Replies
Replies have been turned off for this discussion
- DBX_Pedro
Community Manager
Hi marty39 ,
Thanks for reaching out on this.
Let's get into it straight away, a possible resolution you can follow in the Mac is :
- Look for search bar
- Then type terminal
- When the terminal windows opens:
- Type the following command
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --add /Applications/Dropbox.app
It will ask you for the password of the Mac next after this is introduced can you please see if the issue persists in the dropbox app ?
This was suggested previously by Surething and has helped a couple of people already.
Can you please test this and get back to us?
Hi,
I am able to access Dropbox after disabling firewall, not with firewall enabled.
DBX_Pedro: That command worked for me. It changed Dropbox from block to allow in Firewall.I tried other options to that command, and --remove doesn't seem to work. But --add did work.
This command line fixed the problem. Thank you!
The issue came from the firewall, even after uninstall/reinstall and reboots, Dropbox app was always blocked in the osx firewall options. After the command it's now Enabled.
- DBX_Pedro
Hi everyone,
We've notified our Engineering team that Dropbox is not starting on Sequoia for some users, and we are currently investigating. We may need to reach out to affected users. We'll provide an update here when we have more to share.
We greatly appreciate your understanding and patience over this period. My firewall is turned off. Dropbox would not start after upgrading to Sequoia. Reinstalling the app fixed the problem. Dropbox started and it is now syncing files.
I have a company-issued Macbook and am unable to make changes to our Firewall settings. Surely this isn't the only fix 😤
- DBX_Pedro
Hi mspink ,
Thanks for reaching out. Keep in mind that company issued Laptops in general might be limited to the restrictions set by them.
Can you please try instead the following steps:
- Go to the top left corner of the screen
- click on the apple
- System Settings
- Network
- Firewall
- Options from the Firewall
- Untick block all incoming connections
- Then allow incoming connections from Dropbox
Can you please test and get back to us?
Hi, the settings on the laptop won't allow me to make changes to the firewall.
Hi, I have a similar issue. I have two company Macs and both are not able to sync files. They both can start the desktop application (even though it takes longer than it usually did), but files don't sync. The interface appears to be syncing (i.e. "syncing 12 files"), but nothing really happens. Surprisingly, the firewall (which I cannot change) has Dropbox with "Allow incoming connection". Somehow, the connection is still blocked.
I've tried re-installing a couple of times but this didn't solve the problem.
