After unlocking, “Copy URI” appears instead of “Show drive”.
What am I doing wrong?
Hi,
Which version of cryptomator are you running? Mint has the flat pack version in its software repository which is not the officially supported version and there is the app image version which you get from the software website.
I’ve traded both ways and they both work for me.
The question I have is where is your Vault located? Is it in the home folder for the user or is it located somewhere else?
The flat pack version is installed. The vault is located locally and also in the self-hosted nextcloud.
cryptomatoro.log:
07:59:59.265 [main] INFO o.c.common.settings.SettingsProvider - Settings loaded from /home/truk/.config/Cryptomator/settings.json
07:59:59.577 [main] INFO org.cryptomator.common.Environment - user.home: /home/truk
07:59:59.578 [main] INFO org.cryptomator.common.Environment - java.library.path: :/app/Cryptomator/lib/app:/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib
07:59:59.578 [main] INFO org.cryptomator.common.Environment - user.language: de
07:59:59.578 [main] INFO org.cryptomator.common.Environment - user.region: null
07:59:59.578 [main] INFO org.cryptomator.common.Environment - logback.configurationFile: null
07:59:59.579 [main] INFO org.cryptomator.common.Environment - cryptomator.settingsPath: /home/truk/.config/Cryptomator/settings.json:~/.Cryptomator/settings.json
07:59:59.579 [main] INFO org.cryptomator.common.Environment - cryptomator.ipcSocketPath: /home/truk/.config/Cryptomator/ipc.socket
07:59:59.579 [main] INFO org.cryptomator.common.Environment - cryptomator.integrationsWin.keychainPaths: null
07:59:59.580 [main] INFO org.cryptomator.common.Environment - cryptomator.p12Path: /home/truk/.config/Cryptomator/key.p12
07:59:59.580 [main] INFO org.cryptomator.common.Environment - cryptomator.logDir: /home/truk/.local/share/Cryptomator/logs
07:59:59.580 [main] INFO org.cryptomator.common.Environment - cryptomator.loopbackAlias: null
07:59:59.580 [main] INFO org.cryptomator.common.Environment - cryptomator.mountPointsDir: /home/truk/.local/share/Cryptomator/mnt
07:59:59.581 [main] INFO org.cryptomator.common.Environment - cryptomator.minPwLength: null
07:59:59.581 [main] INFO org.cryptomator.common.Environment - cryptomator.appVersion: 1.16.0
07:59:59.581 [main] INFO org.cryptomator.common.Environment - cryptomator.buildNumber: flatpak-1
07:59:59.581 [main] INFO org.cryptomator.common.Environment - cryptomator.pluginDir: /home/truk/.local/share/Cryptomator/plugins
07:59:59.582 [main] INFO org.cryptomator.common.Environment - cryptomator.showTrayIcon: true
07:59:59.582 [main] INFO org.cryptomator.common.Environment - cryptomator.disableUpdateCheck: true
07:59:59.582 [main] INFO o.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.16.0 on Linux 5.15.0-139-generic (amd64)
07:59:59.653 [main] INFO org.cryptomator.ipc.Server - Spawning IPC server listening on socket /home/truk/.config/Cryptomator/ipc.socket
08:00:01.266 [JavaFX Application Thread] INFO o.cryptomator.launcher.Cryptomator - JavaFX runtime started after 3101ms
08:00:02.102 [JavaFX Application Thread] ERROR o.purejava.appindicator.AppIndicator - Directory ‘/etc/ld.so.conf.d/’ does not exist
08:00:02.115 [JavaFX Application Thread] INFO o.purejava.appindicator.AppIndicator - Native code library libayatana-appindicator3.so.1 failed to load
08:00:02.116 [JavaFX Application Thread] INFO o.purejava.appindicator.AppIndicator - Native code library libappindicator3 successfully loaded
08:00:03.607 [JavaFX Application Thread] INFO o.f.d.c.transports.TransportBuilder - Using transport dbus-java-transport-native-unixsocket for address unix:path=/run/flatpak/bus
08:00:03.914 [JavaFX Application Thread] INFO o.f.d.c.transports.TransportBuilder - Using transport dbus-java-transport-native-unixsocket for address unix:path=/run/flatpak/bus
08:00:03.935 [JavaFX Application Thread] INFO o.f.d.c.transports.TransportBuilder - Using transport dbus-java-transport-native-unixsocket for address unix:path=/run/flatpak/bus
08:00:05.986 [App Scheduled Executor 01] INFO o.c.common.settings.SettingsProvider - Settings saved to /home/truk/.config/Cryptomator/settings.json
08:00:06.940 [App Scheduled Executor 02] INFO o.c.common.settings.SettingsProvider - Settings saved to /home/truk/.config/Cryptomator/settings.json
08:00:18.060 [App Background Thread 002] INFO org.eclipse.jetty.server.Server - jetty-10.0.25; built: 2025-03-13T00:02:39.342Z; git: 96cc25d2f26c3fb61444b801be87640e59cf380e; jvm 23.0.2+7
08:00:18.132 [App Background Thread 002] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@2059bf1d{/,null,AVAILABLE}
08:00:18.151 [App Background Thread 002] INFO o.e.jetty.server.AbstractConnector - Started ServerConnector@461d8f22{HTTP/1.1, (http/1.1)}{localhost:42427}
08:00:18.195 [App Background Thread 002] INFO org.eclipse.jetty.server.Server - Started Server@4e23f986{STARTING}[10.0.25,sto=0] @20810ms
08:00:18.195 [App Background Thread 002] INFO o.c.frontend.webdav.WebDavServer - WebDavServer started.
08:00:18.301 [App Background Thread 002] INFO o.e.j.s.s.DefaultSessionIdManager - Session workerName=node0
08:00:18.314 [App Background Thread 002] INFO o.a.j.w.server.AbstractWebdavServlet - authenticate-header = Basic realm=“Jackrabbit Webdav Server”
08:00:18.317 [App Background Thread 002] INFO o.a.j.w.server.AbstractWebdavServlet - csrf-protection = null
08:00:18.318 [App Background Thread 002] INFO o.a.j.w.server.AbstractWebdavServlet - createAbsoluteURI = true
08:00:18.318 [App Background Thread 002] INFO o.e.j.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@48e04364{/d9a4iykYDhB_,null,AVAILABLE}
08:00:18.319 [App Background Thread 002] INFO o.c.f.w.s.WebDavServletController - WebDavServlet started: /d9a4iykYDhB_
08:00:18.320 [App Background Thread 002] INFO o.c.f.w.mount.AbstractMountBuilder - Mounting http://localhost:42427/d9a4iykYDhB_…
08:00:18.446 [App Background Thread 002] WARN org.cryptomator.common.vaults.Vault - Unable to add vault to quick access area: Vault is not mounted to local system path.
08:00:18.447 [JavaFX Application Thread] INFO o.c.ui.unlock.UnlockWorkflow - Unlock of ‘tresor’ succeeded.
08:00:20.519 [App Background Thread 005] INFO o.cryptomator.ui.common.VaultService - Vault mounted at http://localhost:42427/d9a4iykYDhB_
Hi,
I don’t have access to next cloud but I’m guessing that the URI is got something to do with that portion of your setup. Perhaps somebody that knows more about the cloud service than I do can assist you further.
If you were to create a sample vault as a test just in your home directory it would probably open fine.
In the log:
08:00:02.102 [JavaFX Application Thread] ERROR o.purejava.appindicator.AppIndicator - Directory ‘/etc/ld.so.conf.d/’ does not exist
08:00:02.115 [JavaFX Application Thread] INFO o.purejava.appindicator.AppIndicator - Native code library libayatana-appindicator3.so.1 failed to load
08:00:02.116 [JavaFX Application Thread] INFO o.purejava.appindicator.AppIndicator - Native code library libappindicator3 successfully loaded
The directory /etc/ld.so.conf.d exists !
Ok,
Please give this a try.
It looks like there might be something wrong with the way the flat pack was packed.
Please try using the official version from the project website.
Its an appimage.
This is the official distribution installation file.
That’s about the only thing I can recommend because it looks like you’re getting a Java error.
This is not true. The flatpak published on flathub is maintained and released by the Cryptomator team.
You are using the wrong volume type, namely WebDAV (HTTP address). Open the cryptomator settings, tab virtual volume, and change either to automatic or FUSE.
Also ensure that in the vault specific options the volume type is not changed.
1 Like
My apologies I was merely looking at the homepage for the software I stand corrected and will note this for the future.
Why is it that there is no link on the homepage for downloads of the flatpak version?
I saw the HTTP errors and it did not occur to me to check the settings that you just referred to. Sorry for my laps in troubleshooting.
I have tried both drive types with the flatpack version. Same error in the log.
Reinstallation with the cryptomator app image ran without error.
Unfortunately, the question remains - what was the error?
Thanks for the help
1 Like
I don’t understand why you had the problem before but thankfully you’re up and running.
Hi, I had the same problem running Sequoia and Fuse-t on a new M4 Macbook Air. What worked was - I went to the file itself that I was trying to unlock, setting it for fuse T. Under “vault options” in the file itself, rather than settings in Cryptomator, it lets you choose the virtual drive, and when I selected fuse-T from that, it DID open a fuse-T location In Finder with the files in it. I have been used to setting the virtual drive in settings, rather than in an individual file itself under vault options