Just my 2 cents, I recently installed BW on my Windows machine with Docker and it went perfectly. Other than an issue getting the email confirmation (which was probably due to my email provider and has been solved), all went well and it works fine.
One thing I had to do is make sure the vEthernet interfaces Docker creates were set to “Home” and allowed in my BitDefender firewall.
I’d like to set it up on a Linux server but the only one I have access to doesn’t give me root - is it at all possible to install without root access?
I’m getting this action too and can’t figure out how to move past it.
I don’t expect support from this outfit but I do have a serious question: why docker? Why an additional layer of complexity surrounding a project with scope as important as this?
The self-hosted option is what almost convinced me to switch from LP after damn near a decade. You’ve got some work to do…stop trying to be fancy.
2 Likes
I know this issue is almost 5 years old but I’m struggling with a fresh self hosted install of Bitwarden. I even removed all install data from ~/bwdata and deleted all containers as suggested above but the error persists. I am able to register a user but then once i try to log in i get a toast on the top right saying " An error has occurred. Username or password is incorrect. Try again. "
I am running Docker version 23.0.1, build a5ee5b1
I also tried running the commands below but it didnt change anything.
228 ./bitwarden.sh stop
229 ./bitwarden.sh updateself
230 ./bitwarden.sh update
231 ./bitwarden.sh updatedb
232 ./bitwarden.sh start
identity logs:
https://generic-f1492f08-f236-4a55-afb7-70ded209cb29.s3.eu-west-2.amazonaws.com/bitwarden/identity+logs.png
I’ll try to downgrade bitwarden/web to see if it solves anything
Hi again,
I took a wild guess and pulled an earlier version of the web container and now it works ! Just run: docker pull bitwarden/web:2022.11.2 and restart the bitwarden instance
Cheers
I ran into this issue as well. The cause for me was that I was trying to run it for testing without using HTTPS, only HTTP. The FrontEnd does not like that. There’s a library called Crypto.subtle used here which is only available in secure contexts.
Found my solution here: Reddit - Dive into anything