Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
Couldn't Start Dropbox
This is usually because of a permissions error. etc
I moved the sync directory to my 😧 drive for info
I suspect the dropbox_path might be the problem
Text File bn.BUILD_KEY: Dropbox bn.V...
Hi Musicstate,
The issue you are experiencing isn't related to any access or permission troubles. It's just a standard error message for everything (with or without real permission issues). The issue is definitely related to the path you selected for your Dropbox folder. It may be due to change/move in this path, for example, or some other similar change. Don't try to change Dropbox folder name or the path pointed to there after you have selected it!
To solve it, you have to unlink the application from your account and link it anew. Remove your troublesome application/device out from your device list. Scroll down to the desired device if need. Click on trash bin next to the desired list entry. This will make sure your device isn't in link to the Dropbox server, but the application itself can still be unaware of that. Forcibly unlink it using following command in terminal:
rm -rf ~/.dropbox
The above guarantees that no any trace from previous link lefts, able to prevent further application work. Now you can link your Dropbox application to your Dropbox account anew by signing in again. 😉
Hope this helps.
Edit: Oh.. you are on Windows. One of the rule above is related to Mac/Linux only. 🤷 My fault. Instead of the command above remove Dropbox folder residing in "C:\Users\music\AppData\Local" (not the one that keeps your data).
Megan
Dropbox Community Moderator
Dropbox Community ModeratorHi jen1147,
To be honest, I don't use your software and don't know in details what you are seeing. Better read associated documentation; I believe there is detailed enough description what you can do. The most important is that you have found what's the reason. 😉
Good luck.
Megan wrote:Hi jen1147, can you take a look into this Help Center article ...
The article:...
- Allow Dropbox access to ports 80 (HTTP) and 443 (HTTPS), and 17600 and 17603 (to open files in third party applications).
...
Hi Megan,
I haven't noticed before, but in the article you linked to is a mistake. Actual loopback ports in use are NOT 17600 and 17603, but 3 port from 17600 to 17602 inclusive (i.e. ports 17600 and 17601, and 17602)! Dropbox application doesn't use port 17603. Most probably typing mistake. 🙂 I believe you will forward this to the person/people responsible for the pointed help article for corrections.
Have a nice day.
ADD: Megan, One more thing is completely missing! How/where LAN Sync comes through? 🧐 Doesn't some port engage especially for this? There is such port actually. 😜 It's missing in the article too. If Dropbox application can't open port 17500 (both TCP and UDP) LAN Sync will never get up. By the way, all other ports needed are TCP only (something that misses in the description too).
