Docker runs, Site appears, Can't Login, Can't Admin, Reverse Proxy ? How / Where?

Hi, thx for reading :slight_smile:

My setup:
Bitwarden in Docker on VM on a machine in intranet using VMWare ESXi. The VM is running Debian 11.
Machine is by purpose not reachable from outside the intranet.

I am:
New to docker, new to VMWare, but willing to learn.
My address is 10.222.2.25

The VMWare VM:
has an intranet-only address playground-keys.inet.company.com / 183.31.82.24

I get an error:
504 Gateway Time-out if I try to Admin-Login to get a secure login link emailed.
Registration is also failing with timeout.

Questions:

  • Is bitwarden runnable in my setup / scenario ?
  • Is my problem a reverse proxy problem ?
    I read about reverse proxy setups, is this the case here ? what to setup how in which file and where ?
2022/02/15 15:11:48 [error] 49#49: *116 upstream timed out (110: Connection timed out) while reading
response header from upstream, client: 10.222.2.25, server: playground-keys.inet.company.com,
request: "POST /admin/login HTTP/2.0", upstream: "http://192.168.224.8:5000/admin/login", host:
"playground-keys.inet.company.com", referrer: "https://playground-keys.inet.company.com/admin/login?returnUrl=%2Fadmin" 
                                                                      
2022/02/15 15:15:38 [error] 49#49: *134 upstream timed out (110: Connection timed out) while reading
response header from upstream, client: 10.222.2.25, server: playground-keys.inet.company.com,
request: "POST /api/accounts/register HTTP/2.0", upstream:
"http://192.168.224.4:5000/accounts/register", host: "playground-keys.inet.company.com", referrer:
"https://playground-keys.inet.company.com/"

Hi @Allisone - welcome! And sorry to hear that you have been experiencing issues with your installation.

Bitwarden server does a pretty good job of self-installing. Did you follow these instructions closely when you installed?

or

Are you an automatic response ? @dh024
Otherwise, yes I think I followed the instructions. But if you think I missed something specifically, could you please ellaborate what ? what I might have missed ?

PLUS I just tried installing again. And the outcome was identical. Bitwarden is there, everything seems fine, until I try to submit one of the forms.

docker rm -f $(docker ps -a -q)
docker rmi -f $(docker images -q)
docker network prune -f

mv bwdata bwdata_old

./bitwarden.sh install

It is really hard to say without knowing more about your setup, but if I had to guess it sounds a simple networking issue between you client device and your server. It looks like you are trying to traverse two private networks, which is going to be tricky depending on how the networking for your server and client machines are setup. It would simplify things a lot if you could put your client device on the same private network as the server while you get Bitwarden server setup.

EDIT: Sorry, I just reread your first post and saw that your server is deployed on a VM, which explains the second private network.