Docker Duplicacy and Webdav SelfSigned certificate

[Lunik971]

Hello,

I am a new user of duplicacy, i have tried it to replace one concurrent and I really prefer.
more user friendly ase du…ty and better monitoring, also a better ressource management.
I started with an hosted webdav service that was really nice, I have changed to a home hosted backup server with nexcloudPi, and I have an error message i think relate to the self-signed certificate :

Failed to list the directory ‘’: Propfind https://XXX.XXX.XXX.XXX/remote.php/dav/files/backup_user/: x509: cannot validate certificate for XXX.XXX.XXX.XXX because it doesn’t contain any IP SANs

any possibility to connect to this webdav without letsencrypt ? or commercial certificate ?

[saspus]

Is that your server? Can you use any other protocol than WebDAV? SFTP for example.

Webdav is designed for document exchange and is not suited well for bulk storage and you will have performance issues. It’s supported as a last resort when this is the only available protocol. But literally any other will be better.

[87aa841a6fec03dd1ad6]

@saspus

It’s supported as a last resort when this is the only available protocol.

We’ve disagreed about this before (I’m using WebDAV over http) but its only advantage - increased speed when the receiving machine lacks hardware AES - is negated by https.

I wonder how SFTP compares to the soon-to-be-released(?) SMB option.

[saspus]

@87aa841a6fec03dd1ad6

I wonder how SFTP compares to the soon-to-be-released(?) SMB option.

SMB is latency sensitive. For long distances (outside of lan) SFTP will be better.

[Lunik971]

Yes it’s mine, but the server is located on my Grandma home at 900 km from my home so difficult to change to SFTP, i will have to reinstall everything.

[Lunik971]

do you configure the backup via Webdav in http by webui or in CLI ?

[87aa841a6fec03dd1ad6]

In my case:

First CLI:

How to add webdav storage with http only in web edition?

I should have explained: First you init (or add) the storage from the command line with http Then you manually add/edit the storage block in the json file. None of this is done with the web interface. Duplicacy supports http WebDAV but (for some reason) the web interface enforces an unnecessary https requirement. The goal is to set it up with the command line and manual editing, bypassing the web interface. Your storage is encrypted? Mine isn’t, maybe that’s the difference.

Then manually editing the settings file (to change https to http):

How to add webdav storage with http only in web edition?

I use WebDAV over wireguard. If your setup’s CPU-bound (e.g. no hardware AES) performance beats SFTP. Duplicacy works with http WebDAV but you have to edit your settings file directly - the web interface wont accept it. So stop duplicacy, open duplicacy.json and edit the storage entry to look something like this: { "name": "Remote", "url": "webdav-http://duplicacy@odroid-remote/duplicacy/", "encrypted": false, "ras_encrypted": false, …

@Lunik971

but the server is located on my Grandma home

But I wouldn’t send personal data outside your lan unencrypted!
I use http over wireguard (to provide encryption.)

Maybe encrypting the storage is sufficient? Probably not. Hopefully someone who knows will comment.

NOTE: I edited my original post with corrections.

[Droolio]

Regardless of whether you use WebDAV or sftp, consider installing Tailscale on each end and closing the exposed port. Much safer, properly encrypted, and then you could consider plain sftp without the overhead - if that’s all you’re using Nextcloud for.