Jump to content
linuxserver.io

[Support] Linuxserver.io - Duplicati

280 posts in this topic Last Reply

Recommended Posts

Since last update, my backups to OneDrive stopped working.

 

Getting this when testing the connection:

"Error

Failed to connect: Only 'http' and 'https' schemes are allowed. Parameter name: requestUri"

mono problem? I saw the bot was updating lots of mono packages. I don't know if the problem is duplicati itself or this container (guess container since only packages got upgraded)

The backup jobs ends with errors:
 

Quote

Failed: Only 'http' and 'https' schemes are allowed.

Parameter name: requestUri

Details: System.ArgumentException: Only 'http' and 'https' schemes are allowed.

Parameter name: requestUri

  at Duplicati.Library.Main.BackendManager.List () [0x00049] in <e2da9713f0974e76879d9f9aa7ce0e36>:0

  at Duplicati.Library.Main.Operation.FilelistProcessor.RemoteListAnalysis (Duplicati.Library.Main.BackendManager backend, Duplicati.Library.Main.Options options, Duplicati.Library.Main.Database.LocalDatabase database, Duplicati.Library.Main.IBackendWriter log, System.String protectedfile) [0x0000d] in <e2da9713f0974e76879d9f9aa7ce0e36>:0

  at Duplicati.Library.Main.Operation.FilelistProcessor.VerifyRemoteList (Duplicati.Library.Main.BackendManager backend, Duplicati.Library.Main.Options options, Duplicati.Library.Main.Database.LocalDatabase database, Duplicati.Library.Main.IBackendWriter log, System.String protectedfile) [0x00000] in <e2da9713f0974e76879d9f9aa7ce0e36>:0

  at Duplicati.Library.Main.Operation.BackupHandler.PreBackupVerify (Duplicati.Library.Main.BackendManager backend, System.String protectedfile) [0x0010d] in <e2da9713f0974e76879d9f9aa7ce0e36>:0

  at Duplicati.Library.Main.Operation.BackupHandler.RunAsync (System.String[] sources, Duplicati.Library.Utility.IFilter filter) [0x01031] in <e2da9713f0974e76879d9f9aa7ce0e36>:0

  at CoCoL.ChannelExtensions.WaitForTaskOrThrow (System.Threading.Tasks.Task task) [0x00050] in <6973ce2780de4b28aaa2c5ffc59993b1>:0

  at Duplicati.Library.Main.Operation.BackupHandler.Run (System.String[] sources, Duplicati.Library.Utility.IFilter filter) [0x00008] in <e2da9713f0974e76879d9f9aa7ce0e36>:0

  at Duplicati.Library.Main.Controller+<>c__DisplayClass13_0.<Backup>b__0 (Duplicati.Library.Main.BackupResults result) [0x00035] in <e2da9713f0974e76879d9f9aa7ce0e36>:0

  at Duplicati.Library.Main.Controller.RunAction[T] (T result, System.String[]& paths, Duplicati.Library.Utility.IFilter& filter, System.Action`1[T] method) [0x0011d] in <e2da9713f0974e76879d9f9aa7ce0e36>:0

 

Log data:

2019-07-26 17:39:42 +02 - [Error-Duplicati.Library.Main.Operation.BackupHandler-FatalError]: Fatal error

System.ArgumentException: Only 'http' and 'https' schemes are allowed.

Parameter name: requestUri

  at Duplicati.Library.Main.BackendManager.List () [0x00049] in <e2da9713f0974e76879d9f9aa7ce0e36>:0

  at Duplicati.Library.Main.Operation.FilelistProcessor.RemoteListAnalysis (Duplicati.Library.Main.BackendManager backend, Duplicati.Library.Main.Options options, Duplicati.Library.Main.Database.LocalDatabase database, Duplicati.Library.Main.IBackendWriter log, System.String protectedfile) [0x0000d] in <e2da9713f0974e76879d9f9aa7ce0e36>:0

  at Duplicati.Library.Main.Operation.FilelistProcessor.VerifyRemoteList (Duplicati.Library.Main.BackendManager backend, Duplicati.Library.Main.Options options, Duplicati.Library.Main.Database.LocalDatabase database, Duplicati.Library.Main.IBackendWriter log, System.String protectedfile) [0x00000] in <e2da9713f0974e76879d9f9aa7ce0e36>:0

  at Duplicati.Library.Main.Operation.BackupHandler.PreBackupVerify (Duplicati.Library.Main.BackendManager backend, System.String protectedfile) [0x0010d] in <e2da9713f0974e76879d9f9aa7ce0e36>:0

  at Duplicati.Library.Main.Operation.BackupHandler.RunAsync (System.String[] sources, Duplicati.Library.Utility.IFilter filter) [0x004fa] in <e2da9713f0974e76879d9f9aa7ce0e36>:0

 

Edited by Niklas

Share this post


Link to post
6 hours ago, Niklas said:

Since last update, my backups to OneDrive stopped working.

 

Getting this when testing the connection:

"Error

Failed to connect: Only 'http' and 'https' schemes are allowed. Parameter name: requestUri"

 

Same problem here. Temporary solution that I came up with is to edit the docker settings and change repository to an older version: "linuxserver/duplicati:v2.0.4.23-2.0.4.23_beta_2019-07-14-ls27"

 

Edited by woocash

Share this post


Link to post
On 7/26/2019 at 6:37 PM, woocash said:

Same problem here. Temporary solution that I came up with is to edit the docker settings and change repository to an older version: "linuxserver/duplicati:v2.0.4.23-2.0.4.23_beta_2019-07-14-ls27"

 

Same problem here too, Failed to connect: Only 'http' and 'https' schemes are allowed. Parameter name: requestUri" when backing up to OneDrive. As woocash suggested rolling back the repository to an older version “linuxserver/duplicati:v2.0.4.23-2.0.4.23_beta_2019-07-14-ls27” resolves. 

 

Share this post


Link to post

Yep. Rolling back works.

The packages upgraded in the latest tag should be reverted or Duplicati needs to update and bring support for the new mono packages. 

For now, this docker will not work for new users using "latest" (if using OneDrive v2, at least) or old user that upgrade soon. People that hasn't configured notifications when stuff go wrong will not know that the backups fail if they don't monitor Duplicati in som way. I have configured mail and got the warning via mail after upgrade on "latest". 

Edited by Niklas

Share this post


Link to post
On 7/27/2019 at 12:37 AM, woocash said:

Same problem here. Temporary solution that I came up with is to edit the docker settings and change repository to an older version: "linuxserver/duplicati:v2.0.4.23-2.0.4.23_beta_2019-07-14-ls27"

 

I performed this and it worked yet again. thx

Share this post


Link to post
9 hours ago, Niklas said:

Yep. Rolling back works.

The packages upgraded in the latest tag should be reverted or Duplicati needs to update and bring support for the new mono packages. 

For now, this docker will not work for new users using "latest" or old user that upgrade soon. People that hasn't configured notifications when stuff go wrong will not know that the backups fail if they don't monitor Duplicati in som way. I have configured mail and got the warning via mail after upgrade on "latest". 

Actually, the issue is due to the upgrade to mono6 and specifically onedrive. Running latest here no problems with backblaze2 so I think it's unfair for you to make the following comment `For now, this docker will not work for new users using "latest" or old user that upgrade soon.`

 

Right now it only seems to affect onedrive uploading and only 1 other user has reported at duplicati. https://forum.duplicati.com/t/mono-update-breaks-onedrive-v2/7569

 

This is an upstream issue, Not an container issue.

Share this post


Link to post
3 hours ago, j0nnymoe said:

Actually, the issue is due to the upgrade to mono6 and specifically onedrive. Running latest here no problems with backblaze2 so I think it's unfair for you to make the following comment `For now, this docker will not work for new users using "latest" or old user that upgrade soon.`

 

Right now it only seems to affect onedrive uploading and only 1 other user has reported at duplicati. https://forum.duplicati.com/t/mono-update-breaks-onedrive-v2/7569

 

This is an upstream issue, Not an container issue.

You're right! Sorry! Added OneDrive to my post. I have not tested all the other providers. At least, OneDrive does not work. 
 

Posted the error log over there.

Edited by Niklas

Share this post


Link to post
13 hours ago, j0nnymoe said:

Actually, the issue is due to the upgrade to mono6 and specifically onedrive. Running latest here no problems with backblaze2 so I think it's unfair for you to make the following comment `For now, this docker will not work for new users using "latest" or old user that upgrade soon.`

 

Right now it only seems to affect onedrive uploading and only 1 other user has reported at duplicati. https://forum.duplicati.com/t/mono-update-breaks-onedrive-v2/7569

 

This is an upstream issue, Not an container issue.

Thanks for the duplicati link.  I am only experiencing the issue with Onedrive.  Backups  to Google Drive are working normally. 

Share this post


Link to post

Same problem here, Duplicati - 2.0.4.23_beta_2019-07-14 and Linuxserver.io version:- v2.0.4.23-2.0.4.23_beta_2019-07-14-ls28 Build-date:- 2019-07-26T10:47:18+00:00

 

Error: Only 'http' and 'https' schemes are allowed. Parameter name: requestUri

Share this post


Link to post
4 hours ago, jfabaf said:

Same problem here, Duplicati - 2.0.4.23_beta_2019-07-14 and Linuxserver.io version:- v2.0.4.23-2.0.4.23_beta_2019-07-14-ls28 Build-date:- 2019-07-26T10:47:18+00:00

 

Error: Only 'http' and 'https' schemes are allowed. Parameter name: requestUri

As mentioned a couple posts back, it's an upstream issue with mono6 and duplicati, not with the container.

Share this post


Link to post

This is for anyone receiving the 401 unauthorized error when trying to backup using Jottacloud. According to https://github.com/rclone/rclone/pull/3436 jottacloud is slowly transitioning to their new API and disabled the usage of the email address as username for JFS API. As a workaround, you can login using your jottacloud username. The username can be found by logining into your jottacloud account via https://www.jottacloud.com/ and viewing the page source code. Do a search for this code:

var user = {username:

 your username will be be inside the single quotes. Use this username in place of your email.  Hope this helps someone. 

Share this post


Link to post

Is anyone having an issue where the tmp dir changes ownership and permissions if the Duplicati app is stopped then started?   This happens to me everytime preventing Duplicati from starting.   Its very bizarre.  Files within the dir are unchanged, but the dir itself is owned by root:root with write for both disabled.

Share this post


Link to post
6 minutes ago, rragu said:

Hi, I'm in the process of setting up Duplicati (following Spaceinvader One's video guide)

I'm having an issue in the configuration of a new backup where there is nothing in the 'Source data' folder dropdown

1843985311_NothinginSourceData-Duplicati.PNG.44a9d02cc52d58508c7f650658a364f5.PNG

 

I checked my volume mappings and they should be fine, I think.

259831638_DuplicatiVolumeMappings.thumb.PNG.6eafaf6ddb608d70f23b767875323a6a.PNG

 

I had set up this Duplicati docker a while ago (I'm in the process of replicating my setup after a hardware failure) and the same mappings worked fine back then. So not sure why nothing is showing up in the dropdown. I did try deleting the container and starting over. But that didn't work

 

Any thoughts would be appreciated

Go to computer and choose /source.

Share this post


Link to post
52 minutes ago, saarg said:

Go to computer and choose /source.

Thanks!

 

I realized what I needed to do literally seconds after I clicked 'Submit Reply' here. So embarrassed I deleted my original post 😳

 

That was certainly a facepalm moment...

Share this post


Link to post
2 hours ago, rragu said:

Thanks!

 

I realized what I needed to do literally seconds after I clicked 'Submit Reply' here. So embarrassed I deleted my original post 😳

 

That was certainly a facepalm moment...

 

Too bad I documented your post for all eternity then... 😁

 

Don't worry about it. We have all done mistakes like this.

Edited by saarg

Share this post


Link to post

Hi all! I'm trying to set up Duplicati on UnRAID. Can anybody verify these mappings?

 

(Container) ----> (Host)

/tmp ----> /tmp/duplicati (RW/Slave)

/backups ----> /mnt/user/backup-duplicati/ (RW/Slave)

/source ----> /mnt/user (RO/Slave)

 

I'm thinking about deleting the /backups mapping since this server will not receive any backups. Is that OK?

Also, is RW/Slave RO/Slave really necessary? I saw in the SpaceInvadersOne video that this supposedly helps improve performance for Docker containers. Is that true or should I set it back to RW/RO?

Share this post


Link to post

Just setup duplicati to do 2 backups.  The first is to a local USB drive (Unassigned Device) and the second is to Backblaze.  I setup both backups and started them and they seemed to be chugging along just fine.  I came back a couple hours later and the interface was not accessible.  I checked the log and saw an error.  I restarted the docker but the interface won't start and I am getting the following error in the log:

 

A serious error occurred in Duplicati: System.TypeLoadException: Could not resolve the signature of a virtual method

 

The entire log text is attached.

 

Does anybody have any ideas on the cause of this?

duplicati.log

Edited by kymnyth
misspelling

Share this post


Link to post

Some updated info.....The Unraid interface became inaccessible as well.  I rebooted by SSHing into the box and can now access the unraid UI and the duplicati UI.  Looks like something in Unraid may of went belly-up.

Share this post


Link to post

After everything came back up and the backup started again, everything stopped and I had to hard-reset the server as I wasn't able to ssh in.  I'm pretty new to duplicati and unraid.  What would be helpful for people to see that could help figure out what the problem is?

Share this post


Link to post
22 minutes ago, kymnyth said:

What would be helpful for people to see that could help figure out what the problem is?

Enable the syslog server in unRaid to mirror to flash (Settings - syslog server).  If it crashes again, post the file created, your diagnostics, and what's detailed here:

 

https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345

 

Share this post


Link to post

I think the original issue is I didn't have the unassigned devices usb drive set to slave in the docker configuration.  I modified that setting and now it doesn't lock up the system but I get a failure doing the backup.....This is the output of the log in duplicati:

 

Nov 5, 2019 6:44 PM: The operation Backup has failed with error: One or more errors occurred. (Object reference not set to an instance of an object (Object reference not set to an instance of an object) (One or more errors occurred. (Access to the path "/backups/duplicati-b85f5d542c06d4844b0dc85c341cbba5f.dblock.zip.aes" is denied.)))

Nov 5, 2019 6:44 PM: Running Backup took 0:00:01:34.255

Nov 5, 2019 6:44 PM: Fatal error

Nov 5, 2019 6:44 PM: BackupMainOperation took 0:00:01:22.765

Nov 5, 2019 6:44 PM: Including path as no filters matched: /source/Videos/Home Movies/Christmas 2008.avi

Nov 5, 2019 6:44 PM: Including path as no filters matched: /source/Videos/Home Movies/2014/

Nov 5, 2019 6:44 PM: Including path as no filters matched: /source/Videos/Home Movies/2013/

Nov 5, 2019 6:44 PM: Including path as no filters matched: /source/Videos/Home Movies/2012/

Nov 5, 2019 6:44 PM: Including path as no filters matched: /source/Videos/Home Movies/2011/

 

 

Any ideas?

Share this post


Link to post

My two cents.  Duplicati is a disaster with Unassigned devices.

However, in my case, I was using SMB. 

 

Edited by eds

Share this post


Link to post

Hi,

 

Thanks for all the hard work that you put in here on the forums.

I have been having some issues recently with my docker install of Duplicati using this docker image through the community apps plugin.

 

The container starts up fine and the backups run fine but at some the container becomes unreachable through the web ui.

 

I have the container mappings setup as follows:


/backups -> /mnt/user/duplicati/backups
/source -> /mnt/user
/config -> /mnt/user/appdata/duplicati
/tmp -> /tmp

 

with the network type set as host.

 

I have successfully accessed the container previously through the local ip address and port, and am trying with the same again.

 

I haven't been able to recover from this state of unreachable web ui, the only way around it I have found is by removing and reinstalling the container (I needed to delete all files in appdata to get this to work).

Not sure what is going on here as seemingly nothing has changed from when it is working to when it stops working (as far as settings etc) but obviously something has. I also tried restarting the container and the server but neither of these seemed to fix the issue.

 

Any help diagnosing and fixing this is would be greatly appreciated.

 

Edit: Have been able to do some more digging, appears to be something with brave as working fine on Firefox.

Edited by Machine4130

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.