Unexpected Error

I cannot log into my vault. I receive the following message and am told to report it to you…
I’ve looked at the other posts on “unexpected errors”, but they are not working for me.

My IP address did change as I was having issues with my internet. That’s the only thing I can think of on my end that has changed.

Please help!

org.cryptomator.common.vaults.Volume$VolumeException: Unable to mount Filesystem
	at org.cryptomator.common.vaults.FuseVolume.mount(FuseVolume.java:54)
	at org.cryptomator.common.vaults.FuseVolume.mount(FuseVolume.java:41)
	at org.cryptomator.common.vaults.Vault.unlock(Vault.java:142)
	at org.cryptomator.ui.unlock.UnlockWorkflow.attemptUnlock(UnlockWorkflow.java:107)
	at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:90)
	at org.cryptomator.ui.unlock.UnlockWorkflow.call(UnlockWorkflow.java:44)
	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.Executors$RunnableAdapter.call(Unknown Source)
	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:51)
	at org.cryptomator.frontend.fuse.mount.Mounter.mount(Mounter.java:10)
	at org.cryptomator.common.vaults.FuseVolume.mount(FuseVolume.java:52)
	... 12 more
Caused by: ru.serce.jnrfuse.FuseException: Unable to mount FS
	at ru.serce.jnrfuse.AbstractFuseFS.mount(AbstractFuseFS.java:293)
	at org.cryptomator.frontend.fuse.mount.MacMounter.mount(MacMounter.java:49)
	... 14 more
Caused by: ru.serce.jnrfuse.FuseException: Unable to mount FS, return code = 1
	at ru.serce.jnrfuse.AbstractFuseFS.mount(AbstractFuseFS.java:289)
	... 15 more

Welcome to the Cryptomator Community :slightly_smiling_face:

do you run Cryptomator on an apple device/macOS and did you recently updated to Big Sur?

If yes, you need to update macFuse to the latest version.

If you do not run Cryptomator on an M1 MacBook, another solution would be to switch to WebDAV as the virtual volume provider in the general preferences. But then you will have lower performance.

1 Like

Perfect! I did just update to Big Sur and have now updated Fuse and solved the issue.
Funny that the app didn’t just ask for Fuse to be updated?!? That would have been helpful.

Thank you for your support!