<![CDATA[Caveat: Possibly relevant changes with Vaultwarden 1.2.9]]>Are these relevant for us?
See https://github.com/dani-garcia/vaultwarden/releases/tag/1.29.0

Major changes and New Features

  • WebSocket notifications now work via the default HTTP port. No need for WEBSOCKET_ENABLED and a separate port anymore.
    The proxy examples still need to be updated for this. Support for the old websockets port 3012 will remain for the time being.
  • Mobile Client push notification support, see #3304 thanks @GeekCornerGH!
  • Web-Vault updated to v2023.5.0 (v2023.5.1 does not add any improvements for us)
  • The latest Bitwarden Directory Connector can be used now (v2022.11.0)
  • Storing passkeys is supported, though the clients are not yet released. So, it might be we need to make some changes once they are released.
    See: #3593, thanks @GeekCornerGH!
]]>https://forum.cloudron.io/topic/9598/caveat-possibly-relevant-changes-with-vaultwarden-1-2-9RSS for NodeWed, 11 Mar 2026 21:50:59 GMTMon, 10 Jul 2023 09:14:20 GMT60<![CDATA[Reply to Caveat: Possibly relevant changes with Vaultwarden 1.2.9 on Mon, 10 Jul 2023 09:25:21 GMT]]>I noticed that since I was updating the app just now. Turns out, the package never supported websockets to start with. So, looks like websocket will now work on the main port!

]]>https://forum.cloudron.io/post/69916https://forum.cloudron.io/post/69916Mon, 10 Jul 2023 09:25:21 GMT