VaultWarden management - stopping the server being abused

Installation
2

Did you do all the installation steps in the doc here? Specifically these ones:

  1. Check the logs of the “Vaultwarden (Bitwarden)” add-on to see if everything went well and to get the admin token/password.
  2. Click the “OPEN WEB UI” button to open Vaultwarden.
  3. Add /admin to the URL to access the admin panel, e.g., http://hassio.local:7277/admin. Log in using the admin token you got in step 3.

If you did then go to that admin page. That’s where you can do all the access control stuff. I have mine set so that no one can sign up unless they receive an invite link from the admin.

If you did not do those steps then things could get tricky. I don’t believe it will show the admin token ever again after initial startup by design. You might be able to find it by reviewing logs in the past by entering this in the CLI:

ha host logs -t addon_a0d7b954_bitwarden -n 500

-n specifies the number of lines to see. Increase that number to go further into the past. If its too far into the past and the number of lines is getting too huge then can try using this guide:

The syslog identifier you want is addon_a0d7b954_bitwarden. journalctl has options to see logs for a given syslog identifier for a particular date range, probably your best option.

If its still too far into the past or that’s too much work then the alternative is a reinstall of the addon. Export your vault and ask your friend to do the same, uninstall the addon, reinstall it, recreate the users and then have them re-import. And this time save the admin token.

1 Like