What is the correct WebDav URL to mount in CLI?

[cryptomator]

What is the correct WebDav URL to mount in CLI?

[tobihagemann]

Cryptomator has this "secret prefix path" for various reasons. It's a "vault id" that is randomly set when adding a vault to the list (and is saved in the settings). Cryptomator CLI doesn't have this so this is nothing that you have to think about here.

I've tried your script (well, not exactly because I've tried it on macOS and used a different mount command... but I used shell variables and called Cryptomator CLI like you did) and was able to successfully mount the vault drive. With that, I can at least confirm that your setup should work.

http://localhost:8198/demoVault should be the correct URL. Or maybe add a trailing slash because I'm not sure how important that is: http://localhost:8198/demoVault/

I'm not familiar with davfs2 but I've noticed that you passed a username/password to the WebDAV server. Cryptomator CLI currently doesn't support authentication (see #5). So the username/password should have no effect. If it's asked, you can type anything in there.

If I'm not mistaken, Cryptomator CLI doesn't support logging. Setting cryptomator.logPath should have no effect.

[shaiguitar]

Has there been any testing done on Raspberry Pi setups? The setup above with the vars I ran on was on a RPi3.

# uname
Linux rpi3a 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l GNU/Linux

# java -version
java version "1.8.0_171"
Java(TM) SE Runtime Environment (build 1.8.0_171-b11)
Java HotSpot(TM) Client VM (build 25.171-b11, mixed mode)

# davfs
pi@rpi3a:~ $ sudo apt list --installed |grep dav
davfs2/stable,now 1.5.4-2 armhf [installed]

[tobihagemann]

Personally, no. I've heard about some successful attempts but I believe they all just involved in running Cryptomator CLI and not mounting the vault on the same device. The only public topic I could found is this one (other ones were via email): https://community.cryptomator.org/t/cryptomator-on-raspberry-pi-3-javafx-problem/644

Maybe you could try and make sure that davfs2 works independently. Try to mount a "regular" WebDAV server like this one: https://webdavserver.com