- #Cryptomator mounting failed upgrade
- #Cryptomator mounting failed password
- #Cryptomator mounting failed windows
If you see a message like: Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS. If not, start by setting the default: wsl -set-default-version 2 So let's check each of these: Default version wsl -status # Available on recent Windows/WSL releasesĭoes the status show the default version is 2? If so, good.
#Cryptomator mounting failed upgrade
You originally installed WSL before WSL2 came out, then upgraded to WSL2, but didn't upgrade the distribution.
Your computer doesn't support WSL2, so only WSL1 was installed to begin with (unlikely).It's not uncommon to think you are running WSL2 when you aren't. WSL2 kernels end in -microsoft-standard-WSL2.WSL1 "pseudo-kernels" end in -Microsoft.The kernel you are using shows that you are actually in WSL1, not WSL2 as you think. Probably - I can't say for sure, but I do know that you won't be able to do it as you are currently configured. Is there any way to access the Cryptomator volume with WSL? Is there something missing in order to access the Cryptomator volume with WSL?
#Cryptomator mounting failed password
I get the following output: 14:54:23.878 INFO o.c. - Binding server socket to 127.0.0.1:8080ġ4:54:23.940 INFO o.e. - Started (http/1.1)}ġ4:54:23.950 INFO .Server - jetty-10.0.6 built: T15:28:56.259Z git: 37e7731b4b142a882d73974ff3bec78d621bd674 jvm 17.0.2+8-Ubuntu-120.04ġ4:54:24.091 INFO o.e.j. - Started INFO .Server - Started INFO o.c. - WebDavServer started.ġ4:54:24.112 INFO .WebDav - WebDAV server started: 127.0.0.1:8080ġ4:54:24.144 INFO - Unlocking vault "firstVault" located at /mnt/e/myFolderġ4:54:24.145 INFO o.c.c.p.PasswordFromPropertyStrategy - Vault 'firstVault' password from property.ġ4:54:25.709 INFO o.e.j.s.s.DefaultSessionIdManager - Session workerName=node0ġ4:54:25.731 INFO o.a.j.w.server.AbstractWebdavServlet - authenticate-header = Basic realm="Jackrabbit Webdav Server"ġ4:54:25.733 INFO o.a.j.w.server.AbstractWebdavServlet - csrf-protection = nullġ4:54:25.733 INFO o.a.j.w.server.AbstractWebdavServlet - createAbsoluteURI = trueġ4:54:25.734 INFO o.e.j. - Started INFO o.c.f.w.s.WebDavServletController - WebDavServlet started: /firstVaultġ4:54:25.739 INFO - Press Ctrl+C to terminate.īack in Windows, I open Google Chrome and try to access, however, I get ERR_CONNECTION_REFUSED. Now, on the directory where I have stored cryptomator-cli-0.5.1.jar, I run the java command (obfuscating the password here for obvious reasons): java -jar cryptomator-cli-0.5.1.jar -bind 127.0.0.1 -port 8080 -vault firstVault=/mnt/e/myFolder/ -password firstVault='' sbin/mount.davfs: waiting for /dev/fuse to be createdįuse is supposed to be compiled into WSL 2 ( "modprobe fuse" on WSL?), however, even though I execute the mknod command, I keep getting the same error.ĮDIT: Updating WSL to the latest version on PowerShell solved the above issue: sbin/mount.davfs: loading kernel module fuse failed Modprobe: FATAL: Module fuse not found in directory /lib/modules/4.4.0-19041-Microsoft Unfortunately, when trying to mount the volume, I get: Password: /sbin/mount.davfs: loading kernel module fuse I am thus trying to use the Cryptomator CLI ( ) directly on WSL, where I aim to open the container directly. It seems like this can't be achieved directly: I am trying to open the container on Windows and to mount the volume directly on WSL, which fails, as it seems to only work with Docany, currently not supported by the latest version of Cryptomator. I want to run bash commands on the contents of that mounted volume, thus, I am trying to access its contents with WSL. My PC's OS is Windows 10, where I am hosting a Cryptomator volume on E.
0 kommentar(er)
