Learn how to make the most out of the Dropbox Community here 💙.
Forum Discussion
Syncing is interrupted. But why?
Receive "Syncing Is Interrupted" error message. Took the following actions to resolve:
1. Disabled firewall
2. Disabled antivirus
3. Made the Windows user an admin
4. Disabled OneDrive
5. ...
Megan
Dropbox Staff
Dropbox StaffHey jdr2, let's see what we can find together on this!
First of all, you took some amazing troubleshooting steps on your end!
Can you also try signing out of the app, re-starting your device, and then singing back in to see if that changes things?
Keep me posted!
i have the same issue. signed off, restarted mac, still the same
I logged in via browser and I see below. It is therefore not about my storage getting full.
Using 1.32 TB of 2 TB storage
- Mark
Super User II
What version of Dropbox jesus-angeles-from-singapore ?
Are you able to try a different network at all maybe via mobile tethering just to check its not your ISP blocking things?
I saw a 'Sync Issues' option. When I clicked it I see the list in the pic attached. It is saying like 'close the file...'. I dont think it is open. No software is using it.
The same issue here. No way to fix it.
- Megan
Hey jesus-angeles-from-singapore, one last thing to check, are you running any antivirus, firewall, VPN or proxy that could be causing issues?
Can you also check the name and path of the file, to make sure it doesn't have any invalid characters, or doesn't use more than 260 characters? You can see more about this here.
Feel free to also take a look at this Help Center article, and let me know if you have any questions.
Hi,
Thanks for the reply. Attached here is a pic. In the same exact folder, and whole filename are of exact length (and not invalid characters), as you can see, some are synced, some are not. So this does not qualify to a file or filename issue on my side.
I do not have any firewalls.
This seems an issue that dropbox itself can diagnose, instead of asking customers random questions. Dropbox can put logs and send back to your server for your own debugging. That will be more accurate for finding the issue in this case.
