Web sockets URLs and port forwarding? about addon-bitwarden

[sinclairpaul]

Websockets support was already configured, by the nginx component running in the addon.

If there is an issue, can you share the browser dev tools output showing the failure (the article you linked also shows how to test it).

[silverl]

Oh, that's good news. I'm pretty new to BitWarden and I was trying to figure out why the Windows thick client can authenticate yet fails to load any records. A few rabbit holes led me down the websockets route, and when I didn't see ports being forwarded like in Vaultwarden's documentation, I assumed it hadn't been implemented yet in the HASS Add-On.

Thanks for clearing that up.

[silverl]

FWIW I'm getting 404s when viewing the dev tools pane in the native Windows client (which looks to be Electron-based or some similar chromium-engine-based environment).

For example, requests to /sync?excludeDomains=true return HTTP 404 for some reason.

[silverl]

I may have solved that issue for myself. I was running the Windows Store version of BitWarden. I just downloaded the Dec portable release from here and that seems to be more compatible with the Dec Vaultwarden HASS release.