Supported File and WebDAV sync configurations

Operating system

Linux

Joplin version

3.4.12

Desktop version info

Joplin 3.4.12 (prod, linux)

Device: linux, 12th Gen Intel(R) Core(TM) i7-1255U
Sync Version: 3
Profile Version: 48
Keychain Supported: No
Alternative instance ID: -

Backup: 1.5.1
Freehand Drawing: 4.2.0

Sync target

File system

What issue do you have?

Just taking my first looks into Joplin, and I'm looking into how best to keep my desktop and mobile synced using my home NAS. I see that WebDAV is an option, however my NAS already comes with a file sync solution, so it'd be great to use that. I can do that in the desktop app using file sync. But there's no option in the Android app to select that sync app as a storage location. I found this old forum post

But was hoping that things have changed since then. Is there any hope of the Android app supporting use of rd party storage providers for the file location?

Trying out the WebDAV option, I'm setting it up for https-only. I have a valid TLS cert deployed on my NAS with wildcard subdomain and then use a reverse proxy on the NAS so that I can use https ://.home. for all my services, and not have to open up all the native service ports in the NAS firewall. Using a URL like https ://:5006/home/Joplin, without the reverse proxy setup, works. But using https ://dav.home./home/Joplin does not.

As a new user I'm limited on number of links, so I had to put some extra spaces in to allow me to port, just pretend there are no extra spaces after https above.

Nope, doing that won’t work on the Android app. Even if it was supported though, it would still require the use of the storage access framework (SAF), which is notoriously slow for directories with a large number of files (as is the case with Joplin data). So I’d suggest you just stick to WebDAV

Hi,

I haven't tried this yet myself but you might be able to do this having Joplin sync to a local folder and then use the Android app folder sync to synchronize the data both ways using SFTP.

Worth a try.

Any idea on not being able to use the reverse proxy port 443 instead of having to go direct to port 5006?

Don’t know, sorry

I had my reverse proxy setup incorrectly, having configured the destination as http on port 5006. Once I fixed that reverse proxy config clients are now ale to connect with https and no port specified.