-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working #598
Comments
I can also confirm that the script is not working anymore. Did you properly configure the permissions in the dropbox developer page? if you do not check this permission files.metadata.read and files.metadata.write you will get this error. I'm hoping that this project is not abandoned. |
Ok. I figure it out. It is working now. I was getting a 400 error from the dropbox API. But I couldn't see the additional description until I ran the curl command generated by the script and it the reponse (the output) There was the following: So I went again to set some more permissions because I was missing permissions. One thing I noticed (one my linux machine): once you change the permission you have to delete your dropbox-uploader configuration file and do the process again for the permission changes to take effect. It is now working as expected. I hope this helps you @skorzennik |
I have checked files.metadata.read and files.content.read, yet 'list' fails. After removing ~/.dropbox_uploader (renaming it) I'm unable to get anything done. We're switching to rclone, that is setup w/out any fuss and works, Sorry, |
I downloaded the version avail as of today, configured it and I can run
and
but the following fails
I modified the script to dump the $RESPONSE_FILE and it says
any idea what is going on?
PS: here is the diff for my 'hack'
1- make RESPONSE_FILE unique per user (avoid perm denied if $TMP_DIR/du_resp_debug exists and own by diff user
2- cat its content when FAILED, to avoid -d that is way too verbose IM(H)O
The text was updated successfully, but these errors were encountered: