Outdated Documentation for Apache in Sublocation Config #1375

New Issue

MrUnknownDE · 2026-04-06T01:51:34+02:00

MrUnknownDE commented

2026-04-06 01:51:34 +02:00

Originally created by @vollkorn1982 on 11/6/2023

Subject of the issue

The documentation explains a deprecated setup for the websocket.

Steps to reproduce

According to https://github.com/dani-garcia/vaultwarden/releases/tag/1.30.0 the websocket setup on port 3012 is deprecated.
The section "Apache in a sub-location (by ss89)" on https://github.com/dani-garcia/vaultwarden/wiki/Proxy-examples still shows an example setup with the deprecated setup for a websocket on port 3012:

        RewriteCond %{HTTP:Upgrade} =websocket [NC]
        RewriteRule /notifications/hub(.*) ws://<SERVER>:3012/$1 [P,L]
        ProxyPass http://<SERVER>:80/$sublocation/

Expected behaviour

The documentation on Apache with a sublocation reflects the currently supported setup mode.

*Originally created by @vollkorn1982 on 11/6/2023* ### Subject of the issue The documentation explains a deprecated setup for the websocket. ### Steps to reproduce According to https://github.com/dani-garcia/vaultwarden/releases/tag/1.30.0 the websocket setup on port 3012 is deprecated. The section "Apache in a sub-location (by ss89)" on https://github.com/dani-garcia/vaultwarden/wiki/Proxy-examples still shows an example setup with the deprecated setup for a websocket on port 3012: ``` RewriteCond %{HTTP:Upgrade} =websocket [NC] RewriteRule /notifications/hub(.*) ws://<SERVER>:3012/$1 [P,L] ProxyPass http://<SERVER>:80/$sublocation/ ``` ### Expected behaviour The documentation on Apache with a sublocation reflects the currently supported setup mode.

MrUnknownDE closed this issue

2026-04-06 01:51:34 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#1375