update bitwarden/vaultwarden templates

Signed-off-by: Eric Nemchik <[email protected]>

Author: nemchik

bitwarden.subdomain.conf.sample

@@ -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;
 

bitwarden.subfolder.conf.sample

@@ -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;
 

vaultwarden.subdomain.conf.sample

@@ -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;
 

vaultwarden.subfolder.conf.sample

@@ -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;