AppImage 1.5.8: Password rejected, can't unlock vault

Help Desktop App
1

Hi everybody,

it was easy enough to install and use Cryptomator on a Windows machine but it seems to be quite a different beast when your OS is Fedora 33 (Gnome). Cryptomator accepts the path to the masterkey within the existing vault without any complaints, but unlocking the vault is impossible. Every time I try, the wheel in the window is spinning for a second, then the password is rejected. And sure, I triple checked the password … Any ideas anybody?

12:55:28.524 [main] INFO  org.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.5.8 on Linux 5.9.8-200.fc33.x86_64 (amd64)
12:55:28.528 [main] DEBUG org.cryptomator.logging.DebugMode - Debug mode enabled
12:55:28.530 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Client] Failed to connect.
12:55:28.530 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Client] Failed to connect.
12:55:28.608 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Server] Wrote IPC port 33447 to /home/woodchuck/.config/Cryptomator/ipcPort.bin
12:55:28.610 [main] DEBUG o.c.launcher.IpcProtocolImpl - Received launch args: 
12:55:28.611 [main] DEBUG org.cryptomator.launcher.Cryptomator - Did not find running application instance. Launching GUI...
12:55:28.623 [main] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 001
12:55:28.624 [App Background Thread 001] DEBUG o.c.ui.launcher.FxApplicationStarter - Starting JavaFX runtime...
12:55:28.638 [main] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 002
12:55:28.930 [JavaFX Application Thread] INFO  o.c.ui.launcher.FxApplicationStarter - JavaFX Runtime started.
12:55:29.883 [JavaFX Application Thread] TRACE o.cryptomator.ui.fxapp.FxApplication - FxApplication.start()
12:55:30.719 [JavaFX Application Thread] DEBUG org.cryptomator.ui.common.FontLoader - Loaded family: Font Awesome 5 Free Solid
12:55:30.871 [JavaFX Application Thread] DEBUG o.c.u.m.MainWindowTitleController - init MainWindowTitleController
12:55:31.138 [JavaFX Application Thread] DEBUG o.c.u.m.MainWindowController - init MainWindowController
12:55:32.133 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.FxApplication - Showing MainWindow
12:56:11.542 [JavaFX Application Thread] WARN  o.c.keychain.KeychainManager - LOAD
12:56:17.524 [JavaFX Application Thread] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 003
12:56:17.528 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.FxApplication - Showing UnlockWindow for Tresor
12:56:17.534 [JavaFX Application Thread] DEBUG o.c.common.vaults.VaultStats - stop recording stats
12:56:17.538 [JavaFX Application Thread] DEBUG o.c.ui.launcher.AppLifecycleListener - Allow quitting without prompt: false
12:56:33.653 [JavaFX Application Thread] TRACE o.c.ui.unlock.UnlockController - UnlockController.unlock()
12:56:37.464 [App Background Thread 003] DEBUG o.cryptomator.cryptofs.ReadonlyFlag - Vault opened for read and write.
12:58:40.359 [JavaFX Application Thread] TRACE o.c.ui.unlock.UnlockController - UnlockController.unlock()
12:58:44.055 [App Background Thread 003] DEBUG o.cryptomator.cryptofs.ReadonlyFlag - Vault opened for read and write.
12:59:18.652 [JavaFX Application Thread] TRACE o.c.ui.unlock.UnlockController - UnlockController.unlock()
12:59:22.380 [App Background Thread 003] DEBUG o.cryptomator.cryptofs.ReadonlyFlag - Vault opened for read and write.
12:59:37.990 [JavaFX Application Thread] DEBUG o.c.ui.unlock.UnlockController - Unlock canceled by user.
12:59:38.006 [JavaFX Application Thread] DEBUG o.c.common.vaults.VaultStats - stop recording stats
12:59:38.010 [JavaFX Application Thread] DEBUG o.c.ui.launcher.AppLifecycleListener - Allow quitting without prompt: true
12:59:39.665 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.FxApplication - Showing Preferences
13:00:01.982 [JavaFX Application Thread] DEBUG org.cryptomator.common.CommonsModule - Starting App Scheduled Executor 01
13:00:02.937 [JavaFX Application Thread] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 004
13:00:02.940 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.UpdateChecker - Checking for updates...
13:00:02.981 [App Scheduled Executor 01] DEBUG o.c.common.settings.SettingsProvider - Attempting to save settings to /home/woodchuck/.config/Cryptomator/settings.json
13:00:02.989 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to /home/woodchuck/.config/Cryptomator/settings.json
13:00:04.055 [JavaFX Application Thread] INFO  o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.5.8, lastest version: 1.5.8
13:00:32.531 [main] INFO  org.cryptomator.launcher.Cryptomator - UI shut down
13:00:32.533 [main] DEBUG org.cryptomator.launcher.IpcFactory - [Server] Shut down
13:00:32.544 [ShutdownTasks] DEBUG org.cryptomator.common.ShutdownHook - Running graceful shutdown tasks...```
2

Does this mean the password window performs a small shake animation? If so, yes, the password is rejected.
And this means that password inside the password field is not the correct one to unlock the masterkey file.

Did you checked the entered password by viewing it? There is an eye symbol which reveals the password:
SecretPassword_hidden

Please check it on both systems, because entering the password by hand has its pitfalls:

3

Yep, there is this shake indicating the rejection. And nope, the password isn’t incorrect, it is exactly the same that works perfectly well, when I use it on my Windows machine. I know for sure, because I extract it from the same KeepassXC database on both computers (and I even compared every single character on both).

4

I solved the problem in a radical way: Deleting the vault itself and the correspondent entries in the Cryptomator Apps, creating a new vault. Now I can access it both from my Windows and my Linux machine.
Some day I’ll find out what I did at first to cause the problem. (Or I won’t.)