Is there a way to test Livesync / websockets is working

[coalfield]

as per title, having some issues with updates from desktop to browser only showing one way without manual sync, looking to be able to confirm 100% I have websockets working correctly Anyone know how?

[jjlin]

Need explaining websocket and push notifications

Bitwarden currently doesn’t have a concept of data conflicts or versioning of an entry as a whole (i.e., not just password history). So for example, if you make a change in the browser extension (say, change the password) and then make another change in the mobile app (say, add a URL), then your password change would be lost because the mobile app (when used with bitwarden_rs) wouldn’t have gotten a notification to reload the updated entry. On the other hand, if you made the change in the mobile…

[cksapp]

You can go directly to https://vaultwarden.domain.tld/notifications/hub or wherever your domain is for /notifications/hub if using another subpath and should see a message such as

WebSocket Protocol Error: Unable to parse WebSocket key.

See for more information.

Enabling WebSocket notifications

A good way to “test” and make sure websockets are functioning though, currently this works in the web browser, extension, and desktop app.
You can open either 2/3 of these in the webvault, browser extension, or desktop app. Connect them to your self-hosted URL of the Vaultwarden instance and login to your account. Create an entry (i.e a test secure note) in one application, you should see the change reflected on the others and can be edited and the changes should sync across all.

[coalfield]

@cksapp

WebSocket Protocol Error: Unable to parse WebSocket key.

Is:

WebSocket Protocol Error: Unable to parse WebSocket key.

The correct output if its working correctly?

EDIT: Played with the ports and using the notifications hub its showing that error but looks to be syncing between desktop and brave browser automatically so think its all OK. Thanks