Issue when using Cryptomator FUSE

Help Desktop App
,
1

Hey guys. I’ve started using Cryptomator with Seafile (after moving away from NextCloud). I have a selfhosted Seafile instance and I’ve installed Seadrive to mount a FUSE drive on my system (latest macOS Catalina, latest FUSE 3.10.4). All good so far.

I’ve then decided to create a Cryptomator vault on said device, which also happened without any issues. However I can’t unlock and mount the the vault using FUSE, each time I get an error like this:

org.cryptomator.common.vaults.Volume$VolumeException: Unable to mount Filesystem
	at org.cryptomator.common.vaults.FuseVolume.mount(FuseVolume.java:107)
	at org.cryptomator.common.vaults.FuseVolume.mount(FuseVolume.java:58)
	at org.cryptomator.common.vaults.Vault.unlock(Vault.java:129)
	at org.cryptomator.ui.common.VaultService$UnlockVaultTask.call(VaultService.java:299)
	at org.cryptomator.ui.common.VaultService$UnlockVaultTask.call(VaultService.java:278)
	at javafx.concurrent.Task$TaskCallable.call(Task.java:1425)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: org.cryptomator.frontend.fuse.mount.CommandFailedException: ru.serce.jnrfuse.FuseException: Unable to mount FS
	at org.cryptomator.frontend.fuse.mount.MacMounter.mount(MacMounter.java:45)
	at org.cryptomator.common.vaults.FuseVolume.mount(FuseVolume.java:105)
	... 9 more
Caused by: ru.serce.jnrfuse.FuseException: Unable to mount FS
	at ru.serce.jnrfuse.AbstractFuseFS.mount(AbstractFuseFS.java:287)
	at org.cryptomator.frontend.fuse.mount.MacMounter.mount(MacMounter.java:43)
	... 10 more
Caused by: ru.serce.jnrfuse.FuseException: Unable to mount FS, return code = 1
	at ru.serce.jnrfuse.AbstractFuseFS.mount(AbstractFuseFS.java:283)
	... 11 more

This also happens with local vaults, so it’s not isolated to Seafile remotes. I’ve however noticed, Seafile may have updated FUSE installation on it’s own to the latest version (reboot didn’t fix this either, just mentioning it because I restarted after Seafile installation).

WebDAV mount type works just fine, although I’d prefer to stick to FUSE if possible. Any ideas on what might be causing this? Thanks!!!

2

Well even though I didn’t get an answer, I’ll post my solution so it might help someone in the future:

What worked for me is I clicked FUSE in system preferences and then clicked “Remove FUSE”. Although it didn’t ask for reboot, I rebooted just for a good measure. After I restarted, FUSE was installed back (I suspect either SeaDrive or Cryptomator installed it automatically). Now it just works for me with both tools, no errors.

1 Like