Documentation insondistency concerning websocket notifications #1561

New Issue

MrUnknownDE · 2026-04-06T02:00:30+02:00

MrUnknownDE commented

2026-04-06 02:00:30 +02:00

Originally created by @sheerun on 7/1/2023

https://github.com/dani-garcia/vaultwarden/wiki/Enabling-WebSocket-notifications

It says "Note: The reason for this workaround is the lack of support for WebSockets from Rocket (though it's a planned feature), which forces us to launch a secondary server on a separate port."

I think it is not up do date because "it's a planned feature" links to https://github.com/SergioBenitez/Rocket/issues/90 which is closed

*Originally created by @sheerun on 7/1/2023* https://github.com/dani-garcia/vaultwarden/wiki/Enabling-WebSocket-notifications It says "Note: The reason for this workaround is the lack of support for WebSockets from Rocket (though it's a planned feature), which forces us to launch a secondary server on a separate port." I think it is not up do date because "it's a planned feature" links to https://github.com/SergioBenitez/Rocket/issues/90 which is closed

MrUnknownDE closed this issue

2026-04-06 02:00:30 +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#1561