-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR [Vault:144] Unable to mount filesystem #7
Comments
Thanks for reporting! This command fails:
Could you try invoking it manually (with alternate schemes like |
I have tried several things: dav, sh + gvfs-mount fails silently, does not appear mounted in
dav, success (behaves as expected and appears and disappears in the file explorer)
http, fails
webdav, fails
davs, fails, triggers an ubuntu error report
https, fails
webdavs, fails
|
davs, https, webdavs is not yet supported, see issue #5. problem is that we can only get self-signed certs for localhost, as no trustworthy CA will issue a certificate for localhost. As dav works, you should change your settings from Can you confirm, that |
Yes, dav works with Cryptomator. |
I'll close this in favour of #8. |
Hello, I'm having a similar issue on an up-to-date arch linux installation and Cryptomator 1.3.2
Is the code using a deprecated tool to mount? Any way I can fix this, or automate the mounting at least?
P.S: Thanks for building this amazing product! |
It is possible that some distributions prefer As we're currently working on FUSE instead of WebDAV, mounting WebDAV should no longer be necessary on Linux from Cryptomator 1.4.0 onwards. That said, |
Hello,
Due to the things discussed here, I installed gvfs2 via apt get (gvfs is not in the repos). PS: I am running Ubuntu 17.10 |
I have encountered the following problem with the release candidate
Cryptomator 1.3.0-rc3 on Linux 4.8.0-49-generic (amd64)
under Ubuntu 16.04 (64 Bit) with using thewebdav
schema option instead ofdav
.The Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy is installed/enabled.
The problem seems to be reproducible on my machine also with a new session.
The text was updated successfully, but these errors were encountered: