Skip to content

Troubleshooting

When something goes wrong, preserve evidence and avoid destructive cleanup. Most recovery work is easier if you still have the original local data and backup files.

Before you start

Do not delete the local Onnoir data folder while troubleshooting. Keep failed .onbk files, error text, and any rollback path Onnoir reports. If you can still open the app, create and verify a fresh backup before trying risky fixes.

Step-by-step

  1. Identify the symptom: unlock, install, backup, restore, preview, search, export, or app launch.
  2. Write down the exact error text.
  3. Check the related doc page for that workflow.
  4. If the app still opens, create a verified .onbk backup.
  5. Try the narrowest safe fix first.
  6. If reporting a bug, include platform, Onnoir version, workflow, expected result, actual result, and whether important data is at risk.

What to expect

Common issues have different responses. A failed unlock may need the recovery key. A failed backup verification means the backup should not be trusted. A failed restore should not be retried blindly without keeping the original backup and any rollback information. A missing document preview may be a file-type or file-size limit, not data loss.

Safety notes

Never send recovery keys, passphrases, full backups, private note text, or sensitive exported files unless you intentionally choose to share them. Bug reports should describe the problem without exposing secrets.

Troubleshooting

  • Cannot unlock: try the saved recovery key exactly as stored.
  • Lost recovery material: look for password-manager entries, printed copies, or downloaded onnoir-recovery-key.txt files.
  • Backup verification failed: create a new backup and verify the new file.
  • Restore failed: preserve the backup and rollback path, then report the exact error.
  • Search missing results: check indexing status, filters, Trash, and document type.
  • Preview unavailable: check file type and size; some previews require Load preview.
  • Install warning: confirm the file came from the official download page.