| This is an *unofficial* Bitwarden implementation, DO NOT use the | Here is the output of docker logs bitwarden after trying to login with my master password. # set to true if you need to setup a new account I was having the same issue before I switched to using mariadb as my database.īelow is my docker-compose.yml config for bitwarden: #bitwarden setup I believe I can get around this by using the admin panel, but unless I am misunderstanding the service should keep working after destroying and rebuilding the container. I am trying to disable registration with the environment variable "SIGNUPS_ALLOWED=false" in my docker-compose.yml, which is what prompts the container to be rebuilt. If I then make any changes to the container via docker-compose.yml then recreate the container with another docker-compose up -d, I am no longer able to authenticate with my master password. ![]() After the initial docker-compose up -d I am able to create an account and everything seems to work. I am running bitwarden_rs via docker-compose with traefik as a reverse proxy, mariadb as my database, and a docker volume is mounted to /data/ in the container. I am getting locked out of my account and am unable to authenticate with my master password after rebuilding the bitwarden_rs container.
0 Comments
Leave a Reply. |