If the password doesn’t work, there are theoretically three options:
- You typed in the wrong password,
masterkey.cryptomator was damaged
- or the software changed the way it checks your password.
Indeed we change the implementation of the password field a while ago, which caused problems with non-printable characters. There have been a handful of users using such non-printable characters in their password. But since you also tried the “old” version, we can rule out this option.
On any successful login (and only then!) the masterkey file is backed up to
masterkey.cryptomator.bkup. The last modification date of this file should therefore reflect the date of your last successful login. You can try to restore this version (simply be duplicating it and renaming the duplicate back to
Since you’re syncing your vault to Dropbox, you can also take a look at the file version history. Any suspicious modifications? Then restore an older version of this file.
Otherwise this only leaves us with:
If you forgot your password, there is nothing we can do about it.
You have in fact as many attempts to type in your password, as you like. Cryptomator does not limit this other than applying a hard-to-compute password derivation function. This means bruteforcing will take a lot of time. But if you know the general structure of the password and are just unsure about a few characters, thus limiting the possibilities to a few millions, this can indeed work.