gpluscas.blogg.se

I would rather not have any http bypass the nginx if at all possibleĪny suggestions would be much appreciated.

I could have nginx bypass the bitwarden domain and reverse proxy it as is to the docker nginx server but again the certificates become prolematic. Is bitwarden.sh able to write global environmental variables in the command line? I believe I could possibly fiddle with the ports in the bitwarden nginx and change the config to effectively bypass the instance of nginx, but that still leaves the problems of the certificates.Īt the moment nginx is working as a reverse proxy as it should. Is there anyway to stop the generation of the nginx in the docker? If I use bitwarden.sh to install I can then add the variable as normal but it is installed with another instance of nginx and (yet another set of certificates) I do not want to have to copy certificates from the default letsencrypt location every time they are renewed or docker is rebuilt etc. I am now unable to provide a token as the method is now to set an environmental variable email address and a token is sent each time admin access is required This works fine BUT the method of providing an admin token has changed. I can manually install bitwarden (without using the bitwarden.sh)

All http traffic is refused and the requesting browser/computer then uses https (if it can).ĭoing it this way I can have several separate domains along with individual certificates (handled by certbot) I am serving several domains with this set up and it works fine. I already have nginx and certbot installed handling the http to https. I am trying to install bitwarden on a Ubuntu 20 server.