Just installed Bitwardenrs/server docker image. I cant get past the create account page. When I hit Submit, nothing happens.
I have nothing in my logs other than the start up message
ADMIN_TOKEN is set
SIGNUPS_ALLOWED set to true
EXTENDED_LOGGING set to true
LOG_LEVEL set to warn
LOG_FILE is defined
Anyone have any suggestions? AdBlocker disabled, FF/Chrome have the same behavior, all running on the LAN
Are you using HTTPS? Any errors in the browsers developers console or in the network tab?
HTTP as that’s the default. I was told that I shouldn’t need https at this stage since I am just installing the container. HTTPS would be handled by the RP but that’s a different setup.
Nothing when you hit F12 but then again I dont know what I should be looking for, nothing stuck out and nothing changed as far as I can tell.
Network Tab? I am not sure what this is referring to.
I mean the network tab of the developer tools, like this:
Check if there’s any failing request in there.
Both Chrome and Firefox have started recently to disallow the use of the necessary crypto APIs unless the page is served from a secure context with HTTPS, but usually you’d get an error popup on screen, I’d try to enable HTTPS and then try to register again.
You might also have luck registering from the desktop client or any other of the clients.
OK so does this REQUIRE HTTPS to run within the LAN? I got an error message using a mobile client, failed to fetch, then I installed the desktop client and it said that it requires https but going to the wiki doesn’t really show how to do this within the docker, looks more like it’s generated for full on VM/hosted sites.
Otherwise nothing is showing me whats wrong.
I do not believe so as the port which is exposed by the container is HTTP (80). From the perspective of the container, the traffic it handles is HTTP.
I have the same setup as yours, with the difference that the container is not available to the LAN at all and all traffic must go though the reverse proxy, which in turn only exposes HTTPS (and of course terminates it).
So at least the web interface should be able to handle HTTP.
EDIT: also please see Ver 1.15 requires ssl for web vault
With the latest versions of Chromium based browsers and Firefox you need to access the web-vault via https, else the JavaScript encryption api will not work. There is one except and that is if you can access the web-vault via localhost/127.0.0.1, all other IP’s require https.
The reason bitwarden_rs uses port 80 by default os because the ssl functionality of the webserver can sometimes cause issues, and therefore we recommend using a reverse proxy server which also does the ssl termination.
So, use a ssl certificate like lets encrypt, or use a self-signed one.
With a self-signed one you probably need to import the CA certificate into your browser and mobile devices for bitwarden to work correctly.
I had to get the RP working. I am not sure I ever saw that it was necessary. Maybe make mention of this on the docker page. That IMPORTANT verbiage didn’t seem to reflect what I was seeing which instigated this post.
