lasers/bitwarden_rs
1
0
Fork 0
mirror of https://github.com/dani-garcia/bitwarden_rs synced 2024-11-24 18:59:44 +01:00
Code Issues Projects Releases Wiki Activity

added a section explaining how to test the connection based on this comment by BlackDex https://github.com/dani-garcia/vaultwarden/discussions/2951#discussioncomment-4296410

Stefan Melmuk 2022-12-25 01:11:56 +01:00
parent ce579930bf
commit 2f1845aa1d
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Enabling-WebSocket-notifications.md

@ -20,4 +20,12 @@ docker run -d --name vaultwarden \
vaultwarden/server:latest
```
Note: The reason for this workaround is the lack of support for WebSockets from Rocket (though [it's a planned feature](https://github.com/SergioBenitez/Rocket/issues/90)), which forces us to launch a secondary server on a separate port.
Note: The reason for this workaround is the lack of support for WebSockets from Rocket (though [it's a planned feature](https://github.com/SergioBenitez/Rocket/issues/90)), which forces us to launch a secondary server on a separate port.
## Test the WebSockets connection
Testing if a connection is working correctly can be done in two ways:
1. Open the developer tools of your browser, go to the network tab and filter for `WS`/`WebSockets`. Logout or refresh the page and login again and you you should see a 101 response for the upgraded WebSocket connection. If you click on that line you should be able to see the messages. If you do not get the status code 101 on `/notifications/hub` then something is configured incorrectly.
2. Open two different browsers or an incognito/private window. Login into your account on both. Either create a new entry, or rename the cipher in one, and that should instantly change also in the other.