rsync.net is a cloud storage provider of a basic linux filesystem to be accessed over SSH - ideal for my Duplicati backups. Currently Duplicati fails with permission errors on trying to write to it. This is because Duplicati prepends a / to the destination file path. rsync.net explicity forbids this as it refers to their server root dir not the user home dir.
Please add an advanced option on SSH connections to use the destination file path exactly as specified.
Hi @hunterdrayman, welcome to the forum 
What version of Duplicati are you using?
We have been busy in that area, which has been hard due to backwards compatibility, but the latest canary now does not add a leading / for that very reason. You now need to add / if you want to explicitly store things in the root folder.
Is it possbile for you to try the canary build? If it is not fixed in the canary builds, we need to address it again.
Thanks for the quick response. I’m using the latest Linuxserver.io/duplicati container - 2.1.0.5_stable_2025-03-04 which I guess is a little behind the current official release. I’ll attempt an upgrade on it and let you know how that goes.
1 Like
Using 2.1.0.124_canary_2025-07-11 (windows) it appears to be prepending a /
Unable to set folder to /duplicati-backups/zippy/documents/, error message: No such file
There is a bunch of legacy considerations for the SSH backend.
We do not want to break the setup for people upgrading, which is why it does not fix it as I suggested.
You can set --ssh-relative-path=true via the advanced options, and that will remove the leading /.
Thanks. Got it.
In recent days I’ve become rather attached to using my rsync.net drive via SSHFS, both on Windows and Linux. Duplicati works well using it as a locally mounted filesystem/drive and I can also move and copy some work files directly. This is in addition to having the sophistication of Duplicati backup & restore.
2 Likes