Archives
“This archive was signed by a key Vault does not know”
(This archive was signed by a key Vault does not know.) The archive was signed by another installation: Obscura Flow, or Vault on another Mac. It is declared unverifiable, not “altered”: Vault cannot attribute its signature, which says nothing about its state. Import the signing key of the installation that created it in Archives › Archive Keys… (see Keys and security), then verify it again.
“This archive is encrypted and no known key opens it”
(This archive is encrypted and no known key opens it.) You need the encryption key that encrypted it. If it comes from Obscura Flow or another Mac, import that key with Archives › Archive Keys… › Import Encryption Key…. Without this key, the archive cannot be restored.
“Restore refused: the archive did not pass verification”
(Restore refused: the archive failed verification.) Vault never restores an archive that does not verify: it could give you back wrong files. The message gives the reason. Restore from another copy of the archive (another medium, offsite); if the only cause is an unknown key, import it first.
“The project folder cannot be found”
(The project folder cannot be found.) The folder was moved, renamed, or is on a disconnected disk. Connect the disk and try again. If the folder has moved, import it at its new location: Vault recognises a folder by its path, so it will make it a new project.
“Archive created, but the verification failed”
(Archive created, but verification failed.) The written archive does not verify right after its creation. Do not rely on it: check the state of the Mac’s disk and the free space, then create a new archive.
An archive does not appear in the list
The Archives screen lists only the archives stored directly in the archives folder (the library’s, or the one chosen in the settings), whose manifest can be read. For an archive stored elsewhere, use Verify… and Restore… at the top of the screen. Refresh re-reads the folder.
Can I choose where Vault writes the archives?
Yes: Settings › General › Archives Folder, Choose…. By default, archives are written to the library’s Archives folder, on the Mac’s disk; a folder on another disk than the originals makes them a distinct copy. Archives already created stay where they are: move them into the new folder to see them on the Archives screen. Default Folder goes back to the library’s folder. Vault refuses, before starting, an archive the archives disk cannot hold, or when that disk is not plugged in. For one more copy, add an external disk or a NAS as a Remote Folder destination in Offsite and send your archives there: the copy is verified after sending.
“Restore refused: … is an incremental revision, and …”
The revision only holds the files added or changed since its base revision: Vault restores it with its whole chain of revisions, and the message says what prevents it. A revision of the chain missing from the folder: put it back beside the others (in the same folder), for example by downloading it from offsite. A revision damaged, signed by an unknown key or encrypted with a missing key: see Understanding verdicts and the archive keys. For those files only, use Extract Only This Revision’s Files… (see Restore an incremental revision).
The restore says “with differences”
(With discrepancies.) Some restored files do not match the manifest. This is the case in particular if a file with the same name already existed in the restore folder: Vault does not overwrite it, and that file differs from the archive’s. Restore into an empty folder.
Integrity
Many files are “not verifiable”
The disk holding their project was probably disconnected during the audit, or the folder was moved. Reconnect it and rerun the project’s audit. Not verifiable means “nothing could be proven”; see Understand the verdicts.
If the disk is connected and the files are Unreadable, macOS may have refused Vault access to the folder (see the next question): the Integrity screen says so above the list of files.
macOS asks for access to the Desktop, Documents, an external disk or a network volume
Vault re-reads your projects’ folders without you choosing them again: folder watching, the scheduled audit, checks of external disks and NAS. macOS then asks once for permission to access the Desktop, Documents or Downloads folder, a removable volume or a network volume, with a sentence that says why. Allow it: Vault only reads your files to compute and check their fingerprints, archive them and restore them.
If you declined, the files in those folders are Unreadable at every audit (a disconnected disk gives Missing). To give access back:
- Open System Settings › Privacy & Security › Files and Folders (the Integrity screen offers Open Privacy & Security…).
- Expand Obscura Vault and turn on the folder or kind of volume concerned.
- If Vault is not in that list, or a folder stays out of reach, add Obscura Vault in System Settings › Privacy & Security › Full Disk Access.
- Quit and reopen Vault, then rerun the project’s audit.
A file is “altered” although I did not touch it
Its content is no longer the one imported: this is precisely what the audit is there to catch. Restore it from a verified archive or an offsite copy, then rerun the project’s audit to confirm.
I deliberately edited a file
Vault always keeps the fingerprint taken at import: the edited file will remain “altered”. Save the edited version under another name; at the next rescan, it will come in as a new file.
The scheduled audit did not run
The scheduled audit only runs while Vault is open; Vault checks whether it is due at launch and then every hour. Also check that Automatic library audit is not set to Never. A stopped or failed audit stays due and will be run again.
Offsite
“The destination does not respond”
(The destination does not respond.) Check your connection, then the destination’s parameters with Edit… and Test Connection: service address, bucket, region, access keys. For a remote folder, check that the volume is mounted.
An upload was interrupted
Start it again: to S3 storage, it resumes where it stopped.
Licence
“Licence Needs Checking”
(Licence to recheck.) Vault has not been able to confirm the licence for too long. Connect the Mac to the Internet, then Account & Licence › Recheck Licence.
“This licence is already in use on the maximum number of devices”
(This licence is already used on the maximum number of devices.) Remove a Mac in Account & Licence › Devices, then Recheck Licence.
I have an Obscura Flow licence: why does Vault refuse it?
Each Obscura app has its own licence. You need an Obscura Vault licence.
Certificates
“Issuing is blocked”
(Issuance is blocked.) The screen lists what is missing: a signing key, the backup of that key, the issuer’s name, the key publication address. Open Settings… in Certificates; see Preservation certificates.
Issuance fails because of the timestamp
If a timestamp authority is set and does not respond, issuance fails rather than producing a weaker certificate. Try again later, change authority, or empty the field to issue without a timestamp.
The recipient sees “Intact, but signed by an unknown key”
(Intact, but signed by an unrecognised key.) They verified the certificate in their own installation of Obscura Vault, which does not know your key. Point them to the verification page printed on the certificate: it fetches your key at the address you publish.
The verification page says the key file cannot be reached
Check that obscura-certificate-key.json is indeed published at the address written in your settings, over https, and that your server allows it to be read from another origin (CORS). The recipient can also paste the file’s content into the page.
Data
Where is my data?
In ~/Library/Application Support/com.oorun.obscuravault/ (see Install and get started). The keys are in the Mac’s keychain.
What should I back up to be able to rebuild everything?
- your original files and your archives (on your media and offsite);
- a recent database backup, copied off the Mac;
- the exported key files (archives and certificates);
- the
Certificatsfolder andcertificate-settings.json, if you issue certificates.
How do I report a problem?
- Help › Report a Problem…: describe what happened, what you expected and what you got. The report adds the version of Obscura Vault and of macOS; read it over before sending it.
- Copy it or save it: Obscura Vault never sends the report itself.
- Click Contact Support… (in the same window, or in the Help menu): the support contact form, https://vault.obscuraflow.app/contact, opens in your browser. Paste or attach the report there.
Never attach an exported key, a password or a file from your library: support will never ask you for them.