Unable to use bitwarden behind reverse proxy using a subfolder

[baku104788]

Despite updating all config variables to utilize a subfolder for bitwarden install the system will not accept it. Nothing works unless you take over the root of the http server which is not desired. my server is used for a few uses and I need to keep each item in its own place / I dont have multiple IPs to use subdomains for everything.

[kspearrin]

Sorry, but I do not understand the issue. What subfolder? I don't understand what HTTP server you are taking over root of. More details are needed to understand this issue.

[baku104788]

I apologize for the confusion. I was just a bit frustrated (mostly thanks to when things dont line up the page just shows blank so it took me a bit to realize it was a url mapping issue) Regardless the install I was going for was something like https:www.example.com/bitwarden/ I had docker set up to listen on 8443 and had apache on the host set to do a reverse proxy for the /bitwarden/ location to port 8443. Everything worked fine certificate wise / etc except the page was always blank. When I did a /admin/ folder and mapped it to the /admin/ folder on docker that of course worked. So it seems that even when you set the env info to include a subdirectory such as /bitwarden/ ahead of the app everything doesn't get adjusted. I hope that is a bit clearer. For now I've just resorted to opening another firewall port and letting bitwarden just run on 8443 directly with no apache reverse proxy

…

On Sat, May 5, 2018 at 6:49 PM, Kyle Spearrin ***@***.***> wrote: Sorry, but I do not understand the issue. What subfolder? I don't understand what HTTP server you are taking over root of. More details are needed to understand this issue. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#277 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AlNRB-fSwNpppngqqY6zm6gwLoA2zw8zks5tvjqjgaJpZM4Tzy_O> .

[kspearrin]

Yes, running Bitwarden under a domain subfolder is not a supported scenario. None of the installer paths are set up for that. It needs to run under a host, as a subdomain or additional port.

[baku104788]

Thanks for the info. One other question- for the premium features I purchased a license by the system on the web/ self hosted install is saying “trialing” and it isn’t letting me use the premium features. Does this just take a bit to update?

…

On Sat, May 5, 2018 at 18:58 Kyle Spearrin ***@***.***> wrote: Yes, running Bitwarden under a domain subfolder is not a supported scenario. None of the installer paths are set up for that. It needs to run under a host, as a subdomain or additional port. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#277 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AlNRB7bBXOe_f8h9F_4m1zT0wRKGpCJ0ks5tvjzAgaJpZM4Tzy_O> .

[kspearrin]

Premium can take a while to propagate to all of your apps. All licenses have a 7 day trial so you will need to generate a new one after your trial ends.

[mustaphazorgati]

Yes, running Bitwarden under a domain subfolder is not a supported scenario. None of the installer paths are set up for that. It needs to run under a host, as a subdomain or additional port.

@kspearrin I am a little confused about the current status. Is it still not supported? Will it be supported someday?

[kcris]

I can run it in a subpath. My nginx proxies all domain.tld/vault requests to my docker container. I followed the instructions here
https://github.com/dani-garcia/bitwarden_rs/wiki/Proxy-examples - section Nginx with sub-path (by BlackDex)

I start the bitwarden_rs docker container like this (I just had to pass the DOMAIN env variable):

sudo docker run -d --name bitwarden -v /srv/docker-containers/bitwardenrs/data/:/data/ -p 19080:80 -p 3012:3012 -e DOMAIN=https://domain.tld/vault/ bitwardenrs/server:latest

[baku104788]

Yes, running Bitwarden under a domain subfolder is not a supported scenario. None of the installer paths are set up for that. It needs to run under a host, as a subdomain or additional port.

@kspearrin I am a little confused about the current status. Is it still not supported? Will it be supported someday?

Another approach is to put bitwarden onto its own IP address and then in your main http hosting (I use apache) have it redirect the subdomain of your choice back to the bitwarden instance as desired. For this I am using an HTTPS site in apache (the outward facing host) and letting it do a reverse proxy to the http instance of bitwarden on the local machine.