lasers/bitwarden_rs
1
0
Fork 0
mirror of https://github.com/dani-garcia/bitwarden_rs synced 2024-11-22 09:55:57 +01:00
Code Issues Projects Releases Wiki Activity

Update caddy example for websockets over port 80 (v1.29.0)

Felix E 2023-07-09 17:52:32 +02:00
parent dfd9a21363
commit 4ad39c1424
1 changed files with 1 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
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 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: If you'd like to make Caddy drop all connections besides for vaultwarden
```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
```Caddyfile ```Caddyfile
mysubdomain.example.com { mysubdomain.example.com {
route { route {
reverse_proxy /my-custom-path/notifications/hub 10.0.0.150:3012
reverse_proxy /my-custom-path/* 10.0.0.150:8083 { reverse_proxy /my-custom-path/* 10.0.0.150:8083 {
header_up X-Real-IP {remote_host} header_up X-Real-IP {remote_host}
} }