I was using Cryptomator with no issues, then suddenly I received the message that it “could not find a vault at this path”. I checked the root directory on Dropbox and found that the vault.cryptomator was missing and the masterkey was missing the entire masterkey.cryptomator. I have the Recovery key, masterkey (without the .crytomator) and password. My files appear to still be there in Dropbox, but I need to establish a way gain access to them.
Hi and welcome.
You have the following options:
- try to recover the missing files from your Dropbox recycle bin.
- try to recover the files from the cryptomator backup. If theres a backup (which is created every time you have a successful login), you’ll find files named like “masterkey.cryptomator.ABCD1234.bkup” and "vault.cryptomator.ABCD1234.bkup. If you rename these files to its original name you can restore the files.
- try to recover from your personal backup
- try to create new files based on your recovery key. please look here fore instructions: Recover masterkey file with recovery key? - #4 by tobihagemann
At the end you should also check if you can find any information what caused this renaming and deleting of the files. Cryptomator does’nt do that, so typically theres some malfunktion in backup or sync processes.
I looked in the Dropbox trash and found nothing related to the file. Next, I found a backup of a Cryptomator file from the source file in question that no longer had a vault path. It was saved onto a removable drive. I attempted to copy past the vault.cryptomator and master.cryptomator backup files, like you suggested, to the source file. It would not open. Then I tried to copy the vault.cryptomator file from the removable drive hoping it would renew the path to the vault. No luck there, either. I created a new folder and tried to input the Recovery key. Not possible. My hope is that I did not do something to exacerbate the issue. I am at a loss to figure it out. I have no idea how the root folder was altered. I had not done anything to the Dropbox source file or anything on the laptop regarding the source file.
Did you try Step 4 as written above?