From 4ad39c14244dff608b2d08fac4e9c1e15d226e02 Mon Sep 17 00:00:00 2001 From: Felix E Date: Sun, 9 Jul 2023 17:52:32 +0200 Subject: [PATCH] Update caddy example for websockets over port 80 (v1.29.0) --- Hardening-Guide.md | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/Hardening-Guide.md b/Hardening-Guide.md index e80b6f9..8666612 100644 --- a/Hardening-Guide.md +++ b/Hardening-Guide.md @@ -75,19 +75,10 @@ Traditionally, a Bitwarden instance resides at the root of a subdomain (i.e., `b For general discussion about subpath hosting for security refer to: https://github.com/debops/debops/issues/1233 -If you make this change, you may also have to change the reverse proxy to add this path to /notifications/hub. For example, in Caddy v2: -```Caddyfile -mysubdomain.example.com { - reverse_proxy /my-custom-path/notifications/hub 10.0.0.150:3012 - reverse_proxy 10.0.0.150:8083 -} -``` - -Or if you'd like to make Caddy drop all connections besides for vaultwarden +If you'd like to make Caddy drop all connections besides for vaultwarden ```Caddyfile mysubdomain.example.com { route { - reverse_proxy /my-custom-path/notifications/hub 10.0.0.150:3012 reverse_proxy /my-custom-path/* 10.0.0.150:8083 { header_up X-Real-IP {remote_host} }