Bitwarden behind nginx reverse proxy location isn't used by Bitwardens /api

[Paraidomat]

Hi,

I'm hosting Bitwarden on premise and I've configured an nginx reverse proxy for SSL with Let's Encrypt. I'm using the location /bw/. This nginx is separate from the bitwarden-nginx container. My Bitwarden is listening on nonstandard ports, so 80/443 are available for my internet facing nginx.

If I'm trying to connect to Bitwarden using https://dyn.dns.tld/bw/ I am able to connect to the login page. However if I'm trying to log in I'll get an "Error fetching data"-Error. When analyzing the network traffic I can see that there is a prelogin-Request, that is using https://dyn.dns.tld/api/accounts/prelogin. Whereas I would expect that the prelogin-Request should be using https://dyn.dns.tld/bw/ap/accounts/prelogin.

In my config.yml I also have specified url: https://dyn.dns.tld/bw/. I also changed the settings for baseServiceUri in ./bwdata/env/global.override.env as well, but I have no luck. I already rebuild/restarted using bitwarden.sh.

Any ideas?

[Paraidomat]

This may be related somehow with #345

[Paraidomat]

Okay, so I figured if i add another location to my nginx for /idenitiy and /api I can log in from remote. But in the developer console there still are a few endpoints that are not reachable (/icon, etc.) since I haven't configured the locations in my nginx for it.

Is there a way to move all the Bitwarden endpoints behind a common URI like /bw/ so my reverse proxy configuration is more clean?

I also tried to reinstall bitwarden all together, but the installer doesn't even ask me if I run this behind a proxy.

[Paraidomat]

I just figured that this is the exact same issue as in #277.

I'm very sad that this is not supported.