forked from linuxserver/reverse-proxy-confs
-
Notifications
You must be signed in to change notification settings - Fork 0
/
bitwarden.subdomain.conf.sample
47 lines (36 loc) · 1.33 KB
/
bitwarden.subdomain.conf.sample
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
# make sure that your dns has a cname set for bitwarden and that your bitwarden container is not using a base url
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;
}
}