[GH-ISSUE #632] Trying to access the web-vault results in Error 502 Bad Gateway #426

New issue

Closed

opened 2026-03-03 01:29:00 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 01:29:00 +03:00

Owner

Originally created by @ProudlyTM on GitHub (Sep 23, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/632

I am running a separate docker nginx server and I'm trying to proxy pass to the internal nginx server of the Bitwarden_RS container, except I have apparently configured something wrong, since I keep getting Error 502 when I try to access the web-vault.

This is what my own docker nginx server subdomain config looks like as of now.

Notes worth mentioning:

When I initially ran the image, I exposed internal port 80 to external port 8383, since port 80 is already bound to my own docker nginx server.
I have not changed anything in the docker image's included nginx server.

Any help will be appreciated. Thanks.

Originally created by @ProudlyTM on GitHub (Sep 23, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/632 I am running a _separate_ docker nginx server and I'm trying to proxy pass to the internal nginx server of the Bitwarden_RS container, except I have apparently configured something wrong, since I keep getting Error 502 when I try to access the web-vault. [This is what my own docker nginx server subdomain config looks like as of now](https://hastebin.com/raw/qidopiqeta). Notes worth mentioning: * When I initially ran the image, I exposed internal port 80 to external port 8383, since port 80 is already bound to my own docker nginx server. * I have not changed anything in the docker image's included nginx server. Any help will be appreciated. Thanks.

kerem closed this issue

2026-03-03 01:29:00 +03:00

kerem commented

2026-03-03 01:29:01 +03:00

Author

Owner

@ProudlyTM commented on GitHub (Sep 25, 2019):

I resolved this by changing "http://bitwarden:8383" to "http://bitwarden:80".. I didn't realize I was trying to reach a non-used port to the docker container of bitwarden itself. 🤦‍♂️😄

@ProudlyTM commented on GitHub (Sep 25, 2019): I resolved this by changing "http://bitwarden:8383" to "http://bitwarden:80".. I didn't realize I was trying to reach a non-used port to the docker container of bitwarden itself. 🤦‍♂️😄