Bitwarden – Setting Up Bitwarden Docker with Apache Reverse Proxy

apache-2.4dockernginxreverse-proxy

I have an Apache2 server for my cloud and Collabora_online(with Apache reverse proxy) and now I've tried to install Bitwarden on my server(self-hosted) but there is one problem, in the Bitwarden docker is already Nginx as webserver and if I will start Bitwarden, Nginx failed to start on port 0.0.0.0:443, cause my Apache server already listing on this port. Is there a way to start Nginx with Apache and redirect from Apache to my Bitwarden-docker with Nginx?

My install way:

curl -Lso bitwarden.sh https://go.btwrdn.co/bw-sh && chmod +x bitwarden.sh

sudo ./bitwarden.sh install

source https://help.bitwarden.com/article/install-on-premise/#install-bitwarden

I hope anyone can help me.

Best Answer

As you are already using Apache as your "frontend" (reverse) proxy, just change the listening port of your nginx and tell apache to fetch content there. This is done by changing the listen parameter in your nginx config, for example to 8443.

Debian based: /etc/nginx/sites-enabled/default
Most others: /etc/nginx/nginx.conf

Then just add another vhost or path directive to your Apache (and SSL offload if you wish to do so).

Most people tend to SSL Offload on their frontend proxy and make direct http request to their backends, but this is up to you.

Related Solutions

NGINX Reverse Proxy – URL Rewrite

Any redirect to localhost doesn't make sense from a remote system (e.g. client's Web browser). So the rewrite flags permanent (301) or redirect (302) are not usable in your case.

Please try following setup using a transparent rewrite rule:

location  /foo {
  rewrite /foo/(.*) /$1  break;
  proxy_pass         http://localhost:3200;
  proxy_redirect     off;
  proxy_set_header   Host $host;
}

Use curl -i to test your rewrites. A very subtle change to the rule can cause nginx to perform a redirect.

Nginx – Docker containers behind reverse proxy – rewrite issues with CMS’s

That is common issue for who want to work on sandbox envoriment. If i got your problem correctly, you are looking for wrong part of the system for solution.

You need to change your cms paths. I think you can use environment variables maybe called root_path and then we can pass proxy value or something else at initial time to the container.

Best Answer

Related Solutions

NGINX Reverse Proxy – URL Rewrite

Nginx – Docker containers behind reverse proxy – rewrite issues with CMS’s

Related Topic