You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We intend to remove the custom Websocket implementation currently included in Vaultwarden.
This implementation uses a separate port (3012) which you needed to configure correctly into your reverse proxy for Websocket notifications to work.
Thanks to the work of @SergioBenitez and @Mai-Lapyst to add Websocket support to Rocket we can now provide this without custom ports and complex reverse proxy configurations.
Also, the new Login with device feature only works via this new Rocket Websocket implementation, and not via the old implementation.
So, to make full use of Vaultwarden we strongly encourage you to adjust your reverse proxy configuration to work with the new setup, since the old way will be removed from the next stable version.
Please check the wiki's Proxy Examples for the updated versions.
Also, if you see any outdated example and know how to update it, please be so kind to help us and update the wiki example.
If you have any questions regarding this, please check the discussion regarding this change, and place your questions there.
For the PR which includes these changes see: #4001
The text was updated successfully, but these errors were encountered:
Repository owner
locked as too heated and limited conversation to collaborators
Nov 3, 2023
BlackDex
changed the title
⚠️[NOTE] BREAKING CHANGE in upcoming stable version
⚠️[NOTE] BREAKING CHANGE in upcoming v1.30.0 stable version
Nov 3, 2023
BlackDex
changed the title
⚠️[NOTE] BREAKING CHANGE in upcoming v1.30.0 stable version
⚠️[NOTE] BREAKING CHANGE in upcoming v1.31.0 stable version
Nov 5, 2023
BlackDex
changed the title
⚠️[NOTE] BREAKING CHANGE in upcoming v1.31.0 stable version
⚠️[NOTE] BREAKING CHANGE sinces v1.31.0
Oct 13, 2024
Hello,
We intend to remove the custom Websocket implementation currently included in Vaultwarden.
This implementation uses a separate port (
3012
) which you needed to configure correctly into your reverse proxy for Websocket notifications to work.Thanks to the work of @SergioBenitez and @Mai-Lapyst to add Websocket support to Rocket we can now provide this without custom ports and complex reverse proxy configurations.
Also, the new
Login with device
feature only works via this new Rocket Websocket implementation, and not via the old implementation.So, to make full use of Vaultwarden we strongly encourage you to adjust your reverse proxy configuration to work with the new setup, since the old way will be removed from the next stable version.
Please check the wiki's Proxy Examples for the updated versions.
Also, if you see any outdated example and know how to update it, please be so kind to help us and update the wiki example.
If you have any questions regarding this, please check the discussion regarding this change, and place your questions there.
For the PR which includes these changes see: #4001
The text was updated successfully, but these errors were encountered: