github/reverse-proxy-confs
1
0
Fork 0
mirror of https://github.com/linuxserver/reverse-proxy-confs.git synced 2025-07-05 20:41:32 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

update bitwarden/vaultwarden templates

Browse source 
Signed-off-by: Eric Nemchik <eric@nemchik.com>
This commit is contained in:
Eric Nemchik 2023-11-11 13:36:10 -06:00
parent 94e933954e
commit f02608e2cf
No known key found for this signature in database
4 changed files with 8 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

5
bitwarden.subdomain.conf.sample
View file

@ -1,7 +1,6 @@
## Version 2023/05/31
## Version 2023/11/11
# make sure that your bitwarden container is named bitwarden
# make sure that your dns has a cname set for bitwarden
# set the environment variable WEBSOCKET_ENABLED=true on your bitwarden container
server {
listen 443 ssl http2;
@ -82,7 +81,7 @@ server {
include /config/nginx/proxy.conf;
include /config/nginx/resolver.conf;
set $upstream_app bitwarden;
set $upstream_port 3012;
set $upstream_port 80;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;

5
bitwarden.subfolder.conf.sample
View file

@ -1,8 +1,7 @@
## Version 2023/02/13
## Version 2023/11/11
# make sure that your bitwarden container is named bitwarden
# make sure that bitwarden is set to work with the base url /bitwarden/
## Environmental Variable DOMAIN=https://<DOMAIN>/bitwarden must be set in bitwarden container including subfolder.
## This is using ports 80 and 3012
location /bitwarden {
return 301 $scheme://$host/bitwarden/;
@ -68,7 +67,7 @@ location ~ (/bitwarden)?/notifications/hub {
include /config/nginx/proxy.conf;
include /config/nginx/resolver.conf;
set $upstream_app bitwarden;
set $upstream_port 3012;
set $upstream_port 80;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;

5
vaultwarden.subdomain.conf.sample
View file

@ -1,7 +1,6 @@
## Version 2023/05/31
## Version 2023/11/11
# make sure that your vaultwarden container is named vaultwarden
# make sure that your dns has a cname set for vaultwarden
# set the environment variable WEBSOCKET_ENABLED=true on your vaultwarden container
server {
listen 443 ssl http2;
@ -82,7 +81,7 @@ server {
include /config/nginx/proxy.conf;
include /config/nginx/resolver.conf;
set $upstream_app vaultwarden;
set $upstream_port 3012;
set $upstream_port 80;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;

5
vaultwarden.subfolder.conf.sample
View file

@ -1,8 +1,7 @@
## Version 2023/03/27
## Version 2023/11/11
# make sure that your vaultwarden container is named vaultwarden
# make sure that vaultwarden is set to work with the base url /vaultwarden/
## Environmental Variable DOMAIN=https://<DOMAIN>/vaultwarden must be set in vaultwarden container including subfolder.
## This is using ports 80 and 3012
location /vaultwarden {
return 301 $scheme://$host/vaultwarden/;
@ -68,7 +67,7 @@ location ~ (/vaultwarden)?/notifications/hub {
include /config/nginx/proxy.conf;
include /config/nginx/resolver.conf;
set $upstream_app vaultwarden;
set $upstream_port 3012;
set $upstream_port 80;
set $upstream_proto http;
proxy_pass $upstream_proto://$upstream_app:$upstream_port;