Install the app
How to install the app on iOS

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature may not be available in some browsers.

BitWarden - self hosted password manager using vaultwarden/server image

Docker BitWarden - self hosted password manager using vaultwarden/server image

As an Amazon Associate, we may earn commissions from qualifying purchases. Learn more...

Last edited:
I would say just backup the value of the environment variable, remove it and restart the container, try to enter in admin panel. If you have a failure you should be able to restore the environnement variable and try again with the Argon2 generation process. The Argon2 ADMIN token has to be stored in the config file so it should be there and not in env variables
 
Last edited:
hmmm, looks like something bad happened :(
1699816994160.png


Of course I am inserting a correct admin token (newly generated Argon2 token). I am putting that one which stored in config.json (I checked, it's there).
All client bitwarden apps (browser plugins, mobile app, PC Windows client app and also web dashboard) are working, but I am not able to login to the admin page.

I tried to restart my vaultwarden container, but it did not help.

What now?

EDIT: Ahhh, so now I figured out - what I need to put there is not the admin token, but the password used during the token generation. Weird...
[automerge]1699818516[/automerge]
but still don't know, what to change to get rid of those red errors from diagnostics>

1699818484934.webp
 
I'm looking to secure the admin token. I had created a test container and was able to do it successfully on the test container, however I do not have the instructions nor remember how I did it. I am looking for the simplest method since running command or compose files is out of my comfort zone. I do recall using container manager and opening a command prompt in that container. From there I copied the string that was generated and then I believe I pasted that into the environment variable for admin token.

I've checked this resource on the 4/15/23 update. Out of all the commands listed, I think I would have to use which of the below ones, to generate the string and copy it out of there and into the environment variable.

Which of the three to use?
1) # Via docker on a running container
docker exec -it vwcontainer /vaultwarden hash

--- What's the difference between these two?

2) # Using the vaultwarden binary directly
./vaultwarden hash

3) # Using the vaultwarden binary directly
./vaultwarden hash --preset owasp
 
I'm looking to secure the admin token. I had created a test container and was able to do it successfully on the test container, however I do not have the instructions nor remember how I did it. I am looking for the simplest method since running command or compose files is out of my comfort zone. I do recall using container manager and opening a command prompt in that container. From there I copied the string that was generated and then I believe I pasted that into the environment variable for admin token.

I've checked this resource on the 4/15/23 update. Out of all the commands listed, I think I would have to use which of the below ones, to generate the string and copy it out of there and into the environment variable.

Which of the three to use?
1) # Via docker on a running container
docker exec -it vwcontainer /vaultwarden hash

--- What's the difference between these two?

2) # Using the vaultwarden binary directly
./vaultwarden hash

3) # Using the vaultwarden binary directly
./vaultwarden hash --preset owasp
Terminal in a running VW container and use option 3.

Once the string has been generated, there is a need to escape all five (5) occurrences of the string sign $ by using double signs instead $$.
 
Last edited:
Terminal in a running VW container and use option 3.

Once the string has been generated, there is a need to escape all five (5) occurrences of the string sign $ by using double signs instead $$.

I was just messing with my test container, took some time and a few tries, but finally figured out how to open bash. What I decided to try was change the existing admin password on the test container, using the option #3 above. However I was able to copy the whole string that was inside the quotes ' ' and went into the admin page to paste into the token field, That worked.

1) therefore why escape all $...what is it doing when left alone vs when escaping them?

2) Looking at production container: I see I have an environment variable of the plain text token. Comparing to my test one where I had converted to argon2 an environment variable does not exist. Confirming the correct method for production container would be in admin page paste in the argon string and save. Then go into container, stop it, and delete out the environment variable which has plain text admin password, turn container back on?
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Thread Tags

Tags Tags
None

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending content in this forum

Back
Top