Trying to access the web-vault results in Error 502 Bad Gateway #3311

New Issue

MrUnknownDE · 2026-04-06T04:42:27+02:00

MrUnknownDE commented

2026-04-06 04:42:27 +02:00

Originally created by @ProudlyTM on 9/23/2019

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 9/23/2019* 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.

MrUnknownDE closed this issue

2026-04-06 04:42:27 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#3311