Troubleshooting
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.
- Try to uninstall and reinstall: This performs a full reset.
- Try a different browser: 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 master key is not accepted. Tusk's Argon2 implementation may be out of date, I'm looking into this now.
- 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.
Are you having problems with Google Drive? Try this first.
-
Important: Reauthorize Google Drive
- Go to https://myaccount.google.com/connections
- Click
Delete all connections you have with Keepass Tusk - Re-authorize Google Drive with Tusk on the
Manage Databasespage
If either of these pages says anything other than "See, edit, create, and delete only the specific Google Drive files you use with this app" or has more than 1 permission, you must do this reauthorization.
| Access page | Details page |
|---|---|
 |
 |
- Make sure the file extension is
.kdbx -
Firefox only: You must allow a popup on Firefox after you click
Choose database file. Sometimes, you might need to allow the popup and then clickChoose database fileagain
During normal usage, Google Drive may lose its authorization and ask you to reauthorize.
The Problem: You have more than 1 account enabled in your browser, and the account used for accessing Google Drive is not the primary account. When your access token expires (this happens at regular intervals), the browser attempts to refresh it in the background. It automatically chooses the primary account on your browser for the refresh, which is the wrong account for the file you need, so the request fails and this screen is presented.
The new solution: Use profiles in chrome rather than signing into multiple accounts under one profile.
The older solution: Make the Google account you need for tusk your primary account. The primary account is the one at the top of the list on Google's Account Page.
- Remove all accounts except for the one Tusk needs on the Google Logout Page
- With your Tusk Google account now at the top of the list, add the others back as non-primary.
Disclaimer This solution doesn't always work. There appear to be other problems lurking in the shadows that cause your token to become revoked. If you have any insights about what might cause this, please open an issue.
- Make sure the file extension is
.kdbx - Reauthorize the provider.
- 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.