reverse-proxy-confs/bitwarden.subdomain.conf.sample
2019-12-30 11:40:02 -05:00

48 lines
1.4 KiB
Text

# make sure that your dns has a cname set for bitwarden and that your bitwarden container is not using a base url
# make sure your bitwarden container is named "bitwarden"
server {
listen 443 ssl;
listen [::]:443 ssl;
server_name bitwarden.*;
include /config/nginx/ssl.conf;
client_max_body_size 128M;
# enable for ldap auth, fill in ldap details in ldap.conf
#include /config/nginx/ldap.conf;
location / {
# enable the next two lines for http auth
#auth_basic "Restricted";
#auth_basic_user_file /config/nginx/.htpasswd;
# enable the next two lines for ldap auth
#auth_request /auth;
#error_page 401 =200 /login;
include /config/nginx/proxy.conf;
resolver 127.0.0.11 valid=30s;
set $upstream_bitwarden bitwarden;
proxy_pass http://$upstream_bitwarden:80;
}
location /notifications/hub {
include /config/nginx/proxy.conf;
resolver 127.0.0.11 valid=30s;
set $upstream_bitwarden bitwarden;
proxy_pass http://$upstream_bitwarden:80;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
}
location /notifications/hub/negotiate {
include /config/nginx/proxy.conf;
resolver 127.0.0.11 valid=30s;
set $upstream_bitwarden bitwarden;
proxy_pass http://$upstream_bitwarden:80;
}
}