ASUSTOR Community Forum

you could try ssh to your nas and then doing a traceroute to www.dropbox.com

if that works I am at a loss.

Wouterj wrote:

snoopy wrote:

Wouterj wrote:Going through the settings again, cannot find the mistake, maybe someone here can help and find a wrong:
Thanks

you may try check the network settings first

http://forum.asustor.com/viewtopic.php?f=29&t=1726

Thanks, i went through these, i do have local weather, download centre acces and all that, checked it anyway, and the Default gateway is there..
reinstalled again, still loading screen...

you may try single Network Interface first rather than LAG mode

Done It!! i tried getting into dropbox through the asportal using chrome.
there i signed in, and then i opened the app for dropbox, this way there was already a connection with dropbox from the NAS...
Now it works.
thanks for the help.

I am using a AS-604T and I can't get the Dropbox app to work. My device is functioning properly, but like others mentioned the Dropbox app hangs during startup. Reinstalling won't help.

Wouterj wrote:Done It!! i tried getting into dropbox through the asportal using chrome.
there i signed in, and then i opened the app for dropbox, this way there was already a connection with dropbox from the NAS...
Now it works.
thanks for the help.

Could you please explain this in more detail?

Hi,

I had the same issue.

In fact i had a lot of issues with the same root cause.

I didn't have the good rights on the app central folders.

Connect via ssh as root (same password as admin)
cd /usr/local
ll

if you have this:
drwx------ 11 root root 4.0K Apr 23 21:58 AppCentral/

You don't have the good rights on this folder!
Just use this command:
chmod 755 /usr/local/AppCentral

exit the terminal.
after that, stop and start all apps in appcentral (eventually a NAS reboot should be done)
And for me it worked!!

renocz - I needed to set up an account for these boards to say: THANK YOU!! That worked for me as well. This has been driving me nuts since I got the NAS a week ago.

Never having done ssh, I did a crash Google search course.....here are the steps I took for anyone that is a noob to ssh....hope they help!

I have a Mac, so used Terminal for the ssh. The commands are slightly different than for Windows you have to put in the user ID and local IP of your NAS on the same line, I think Windows they can be 2 separate commands:

ssh root@<xxx.xxx.x.xxx> where the x's are the NAS IP address on your local network

You probably will get a warning message, just type yes
enter admin password

Tried doing the change directory, but got hung up. The dir command does not work in terminal (my DOS recollections from circa 1990 were of no help). Anyway, finally figured out the proper command.....just one little mistake in renocz's post: instead of "user", the directory is actually "usr", so if you wanted to test access to the directory use: cd /usr/local

Then just same command as shown:

chmod 755 /usr/local/AppCentral

Dropbox almost immediately went from the endless "loading" message to the sign-in screen, but I did the start and stop all apps and reboot anyway. Now it is syncing away. Happy Times

astrodog09 wrote:renocz - I needed to set up an account for these boards to say: THANK YOU!! That worked for me as well. This has been driving me nuts since I got the NAS a week ago.

You're welcome

And thank you for highlighting my little mistake!

ah good i see it allready worked, sorry for the late responce, was on a holiday...

I just noticed that the dropbox app on my AS-204T has stopped working quite some time ago... Now when I try start it, I just get the "Loading" screen and nothing else.

If I let it sit there for a long time it eventually pops out an error message about not being able to connect/start server, can't remember exactly what it says.

Permissions are all ok, that I've checked.

ADM Version: 2.4.0.RFU6
Dropbox app Version: 1.0.1.r100

Any help greatly appreciated.

EDIT: For some unfathomable reason my NAS had lost it's link to my Dropbox account, after NAS reboot and some log trawling I found that out. After relinking all is well again.