Dropboxbackup stopped working

stellan86 · 29 January 2024 14:31

Hi!

I’ve been using Duplicacy Web Edition for around a month. Just recently bought the license since the backup is working fine. Duplicacy is updated. Running Duplicacy Web Edition 1.7.2 as docker on my Unraid server.

As of saturday, I get this error:
Failed to upload the chunk 0c545a6b79a46d30f5cf76659f71dc14f027cb192b0f84c462f1b1f162ab90f6: Error in call to API function “files/upload”: Invalid authorization value in HTTP header “Authorization”: “Bearer”. Expecting "Bearer ".

I’m using Dropbox as my backup destination. My first thought was that the token might have expired but the backup starts and uploads data for arount 40 minutes before I get this error. Can it be the token anyway?

I know how to fetch a new token but how do I change the one thats already added in Duplicacy? I dont want to remove the datastore and add it again.

Didn’t find anyont that has had this exact error before.

Regards.

This is the full backuplog:

Running backup command from /cache/localhost/0 to back up /data
Options: [-log backup -storage Dropbox -threads 30 -stats]
2024-01-29 13:08:58.081 INFO REPOSITORY_SET Repository set to /data
2024-01-29 13:08:58.082 INFO STORAGE_SET Storage set to dropbox://Backup
2024-01-29 13:09:26.282 INFO BACKUP_START Last backup at revision 26 found
2024-01-29 13:09:27.020 INFO BACKUP_INDEXING Indexing /data
2024-01-29 13:09:27.021 INFO SNAPSHOT_FILTER Parsing filter file /cache/localhost/0/.duplicacy/filters
2024-01-29 13:09:27.021 INFO SNAPSHOT_FILTER Loaded 0 include/exclude pattern(s)
2024-01-29 13:39:28.006 INFO UPLOAD_KEEPALIVE Skip chunk cache to keep connection alive
2024-01-29 13:48:20.894 ERROR UPLOAD_CHUNK Failed to upload the chunk 0c545a6b79a46d30f5cf76659f71dc14f027cb192b0f84c462f1b1f162ab90f6: Error in call to API function "files/upload": Invalid authorization value in HTTP header "Authorization": "Bearer".  Expecting "Bearer <oauth2-access-token>".
Failed to upload the chunk 0c545a6b79a46d30f5cf76659f71dc14f027cb192b0f84c462f1b1f162ab90f6: Error in call to API function "files/upload": Invalid authorization value in HTTP header "Authorization": "Bearer".  Expecting "Bearer <oauth2-access-token>".

gchen · 29 January 2024 15:40

I’m not sure if that error was caused by an expired token. But you can remove the existing storage and create a new one with the same storage name (using the new token). All backups or other jobs should work as long as the storage name doesn’t change.

stellan86 · 31 January 2024 12:50

Hi!

Sorry for the late response but since I wrote this topic, the backup has worked fine without me changing anything.

I don’t know if that is good or bad but as of now. Everything works fine.

stellan86 · 26 March 2024 11:11

Hi!

Now I have got this problem again the last few days. I cant find a way to solve it.

Any ideas?

Running backup command from /cache/localhost/0 to back up /data
Options: [-log backup -storage Dropbox -threads 30 -stats]
2024-03-27 08:44:32.567 INFO REPOSITORY_SET Repository set to /data
2024-03-27 08:44:32.567 INFO STORAGE_SET Storage set to dropbox://Backup
2024-03-27 08:45:21.169 INFO BACKUP_START Last backup at revision 79 found
2024-03-27 08:45:22.013 INFO BACKUP_INDEXING Indexing /data
2024-03-27 08:45:22.013 INFO SNAPSHOT_FILTER Parsing filter file /cache/localhost/0/.duplicacy/filters
2024-03-27 08:45:22.014 INFO SNAPSHOT_FILTER Loaded 0 include/exclude pattern(s)
2024-03-27 09:15:23.192 INFO UPLOAD_KEEPALIVE Skip chunk cache to keep connection alive
2024-03-27 09:25:58.848 ERROR UPLOAD_CHUNK Failed to upload the chunk abbdb2d8b1cae9ba091646adfd70548d0a2cf70311b120d4165bfa4944f13cf9: Error in call to API function "files/upload": Invalid authorization value in HTTP header "Authorization": "Bearer".  Expecting "Bearer <oauth2-access-token>".
Failed to upload the chunk abbdb2d8b1cae9ba091646adfd70548d0a2cf70311b120d4165bfa4944f13cf9: Error in call to API function "files/upload": Invalid authorization value in HTTP header "Authorization": "Bearer".  Expecting "Bearer <oauth2-access-token>".

towerbr · 29 March 2024 11:32

Weird, it seems that the token is not being sent when trying to upload:

(ref: Dropbox OAuth Guide - Dropbox)

gchen · 31 March 2024 03:11

What is the CLI version you’re running?

stellan86 · 2 April 2024 05:41

Hi!

I’m using Duplicacy Web Edition 1.7.2 running in docker on my Unraid system. No update available.

I got it working for three days by removing the storage and re-adding it with the same name but now its not working again. The same error with bearer.

Log from today:

Running backup command from /cache/localhost/0 to back up /data
Options: [-log backup -storage Dropbox -threads 30 -stats]
2024-04-02 01:00:01.543 INFO REPOSITORY_SET Repository set to /data
2024-04-02 01:00:01.544 INFO STORAGE_SET Storage set to dropbox://Backup
2024-04-02 01:00:46.342 INFO BACKUP_START Last backup at revision 82 found
2024-04-02 01:00:47.060 INFO BACKUP_INDEXING Indexing /data
2024-04-02 01:00:47.061 INFO SNAPSHOT_FILTER Parsing filter file /cache/localhost/0/.duplicacy/filters
2024-04-02 01:00:47.061 INFO SNAPSHOT_FILTER Loaded 0 include/exclude pattern(s)
2024-04-02 01:30:48.030 INFO UPLOAD_KEEPALIVE Skip chunk cache to keep connection alive
2024-04-02 01:45:28.559 ERROR UPLOAD_CHUNK Failed to upload the chunk ac5ccad78291695798d707962b36cb0ec0f7a21119ca5f5bf055c48c0b87a86e: Error in call to API function "files/upload": Invalid authorization value in HTTP header "Authorization": "Bearer".  Expecting "Bearer <oauth2-access-token>".
Failed to upload the chunk ac5ccad78291695798d707962b36cb0ec0f7a21119ca5f5bf055c48c0b87a86e: Error in call to API function "files/upload": Invalid authorization value in HTTP header "Authorization": "Bearer".  Expecting "Bearer <oauth2-access-token>".

I have not tried removing the storage and re-adding it again. I feel that it should be something else that can solve this issue.

stellan86 · 5 April 2024 10:14

This time it does not work removing av readding the storage. The error is till the same.

Anyone?

gchen · 5 April 2024 15:58

You can find the CLI version on the Setting page. If you’re running CLI 2.x.x then you need to upgrade to the latest 3.2.3.

stellan86 · 5 April 2024 17:19

Hi!

I’m already at 3.2.3 unfortunately.

I don’t know much about troubleshooting Duplicacy but I’m out of ideas.
Removing and readding the storage only worked for a few days and now it doesn’t help at all.

gchen · 6 April 2024 02:54

Can you add -d as a global option to the backup job to see if Duplicacy is uploading chunks before the error? Also, 30 threads may be too many. Try to change it to -threads 8 or even -threads 4.

stellan86 · 8 April 2024 08:45

Hi!

I can see that it uploads quite a lot of data before it fails.

I’ll try to change threads. I used to have a low number of threads but the uploadspeed was so slow at that point but I’ll give it a try again.

I’ll come back to you.

stellan86 · 8 April 2024 13:42

Today I got the backup running without changing anything.

I ran the backup again with -d and -threads 8 and it worked as well.

I get a lot of retries in the log. around 1500 lines of logs like the image below.,
Is this normal?

saspus · 8 April 2024 14:05

Use 2 threads at most with Dropbox. Ideally — one.

Error 429 is “too many requests”. Dropbox is throttling you.

Dropbox always was one of the least forgiving *drive type remotes.

Have a look at this thread: Duplicacy should respect 429 responses (Dropbox)

stellan86 · 12 April 2024 05:57

The job seems to be doing okey now even though it takes arunt 3 hours to complete now.

How do I read this? How how much new data is uploaded? It goes incredibly slow but if it works and is reliable i think its ok

saspus · 12 April 2024 07:01

IN the line before last on your screenshot (it’s hard to copy text from a screenshot, it’s much easier to copy text) at the end, is amount of data uploaded.