This page provides troubleshooting information for common issues with Tusk. If you open an issue for one of the following topics without troubleshooting, don't expect much of a response.n

Tusk exists for Chrome and Firefox. If you have a problem with chrome, try firefox. If you have a problem with firefox, try chrome. If you find that something works in one place and not the other, please open an issue.

This error happens when your password is not accepted.

• Verify that you put in the right password (and optionally keyfile) by opening the database in KeePass or KeePassXC
• Verify that your database works on https://app.keeweb.info - we use the same crypto engine, and if it doesn't work there, it won't work in Tusk. If it won't open there, it might be a bug with keeweb/kdbxweb
• Create a new copy of your database with different crypto functions. Start with AES + AES. Try ChaCha20 + Argon2. If you find a combination that works, open an issue and tell me what combination doesn't work.
• Create a new copy of your database with a different keyfile, or no keyfile. If this works, open an issue and tell me what sort of file your non-working keyfile is. If it is XML, please paste an exact text copy of your keyfile without the sensitive data parts in the github issue.
• If you can create a new sample database with keyfile that produces the bug, upload the sample database, keyfile, and password to a github issue. This is the BEST way to help me debug issues.

• Make sure the file extension is .kdbx
• Create a copy of your database and store it in the cloud provider.
• Reauthorize the provider.
  • For google drive, remove authorization at https://myaccount.google.com/permissions
  • For Dropbox, remove authorization at https://www.dropbox.com/account/connected_apps
• Re-authorize and see if it comes up.
• For dropbox, try a shared link instead.