Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- #BITWARDEN
- # make sure that your domain has dns has a cname or a record set for the subdomain bitwarden
- # This config file will work as is when using a custom docker network the same as letesencrypt (proxynet).
- # However the container name is expected to be "bitwardenrs" as it is by default the template as this name is used to resolve.
- # If you are not using the custom docker network for this container then change the line "server bitwardenrs:80;" to "server [YOUR_SERVER_IP]:8086;" Also remove line 7
- resolver 127.0.0.11 valid=30s;
- upstream bitwarden {
- server bitwardenrs:80;
- }
- server {
- listen 443 ssl;
- server_name bitwarden.*;
- include /config/nginx/ssl.conf;
- client_max_body_size 128M;
- location / {
- proxy_pass http://bitwarden;
- proxy_set_header Host $host;
- proxy_set_header X-Real-IP $remote_addr;
- proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
- proxy_set_header X-Forwarded-Proto $scheme;
- }
- location /notifications/hub {
- proxy_pass http://bitwarden;
- proxy_set_header Upgrade $http_upgrade;
- proxy_set_header Connection "upgrade";
- }
- location /notifications/hub/negotiate {
- proxy_pass http://bitwarden;
- }
- }
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement