5 ms·

My personal problem is that I self host and the updated extension just completely fails to connect to my vaultwarden instance. I probably just need to repull th

by Cieric 2y ago

My personal problem is that I self host and the updated extension just completely fails to connect to my vaultwarden instance. I probably just need to repull the updated docker container, but it's something I would have rather not thought about. But since the extension auto updated I'm forced to think about it.

erdii 2y ago
Be careful about using newer clients with an outdated version of the vaultwarden server. I lost a couple days of new accounts/passwords because this[1] probably happened. [1] https://github.com/dani-garcia/vaultwarden/discussions/4921 https://github.com/dani-garcia/vaultwarden/discussions/4921
horsawlarway 2y ago
Interesting - I'm also running self-hosted and didn't have this problem (I think my last image pull was about a month ago, though - so somewhat recent). If you want, I believe you can override the update url in chrome to stop the auto-update process in the future: https://chromeenterprise.google/policies/?policy=ExtensionSettings https://chromeenterprise.google/policies/?policy=ExtensionSe... Alternatively, at least for chromium browsers - you can download the .crx directly, unzip it (p7zip will do it), and sideload it using the "Developer mode" checkbox on chrome://extensions. Firefox sadly doesn't support this - they'll remove any sideloaded extensions on browser close.
- Macha 2y ago
  Yeah, the problem is with clients from January or newer, and vaultwarden versions from before October. It did lead me to discover my automatic update process wasn't actually rebooting the vaultwarden server.
infogulch 2y ago
You can enable the new extension UI when you're using vaultwarden by setting the EXPERIMENTAL_CLIENT_FEATURE_FLAGS=extension-refresh env var. I wrote more about it here: https://forum.cloudron.io/topic/13001/bitwarden-extension-ui-refresh https://forum.cloudron.io/topic/13001/bitwarden-extension-ui...
sofixa 2y ago
> something I would have rather not thought about I mean, you're explicitly choosing to self-host an alternative backend server which isn't affiliated with Bitwarden. You could have used their SaaS, or self-hosted their official backend they provide on GitHub, for free, and which is almost entirely open source (AGPL, they have some small enterprise specific bits such as SSO which are under a commercial license which is still free, just not open source). But you choose to self-host a random person's project that tries to keep track with Bitwarden APIs and various frontends, on a best effort basis. That's a ton of risk I really wouldn't take with something as sensitive as passwords to everything.
- gunalx 2y ago
  Its pretty ok as the offical client caches most stuff, everything is still encrypted, and most of all vaultvarden is miles easier to self host than the offical bitwarden stuff.

by Cieric 2y ago

erdii 2y ago

Be careful about using newer clients with an outdated version of the vaultwarden server. I lost a couple days of new accounts/passwords because this[1] probably happened. [1] https://github.com/dani-garcia/vaultwarden/discussions/4921 https://github.com/dani-garcia/vaultwarden/discussions/4921

horsawlarway 2y ago

Interesting - I'm also running self-hosted and didn't have this problem (I think my last image pull was about a month ago, though - so somewhat recent). If you want, I believe you can override the update url in chrome to stop the auto-update process in the future: https://chromeenterprise.google/policies/?policy=ExtensionSettings https://chromeenterprise.google/policies/?policy=ExtensionSe... Alternatively, at least for chromium browsers - you can download the .crx directly, unzip it (p7zip will do it), and sideload it using the "Developer mode" checkbox on chrome://extensions. Firefox sadly doesn't support this - they'll remove any sideloaded extensions on browser close.

Macha 2y ago
Yeah, the problem is with clients from January or newer, and vaultwarden versions from before October. It did lead me to discover my automatic update process wasn't actually rebooting the vaultwarden server.

infogulch 2y ago

You can enable the new extension UI when you're using vaultwarden by setting the EXPERIMENTAL_CLIENT_FEATURE_FLAGS=extension-refresh env var. I wrote more about it here: https://forum.cloudron.io/topic/13001/bitwarden-extension-ui-refresh https://forum.cloudron.io/topic/13001/bitwarden-extension-ui...

sofixa 2y ago

> something I would have rather not thought about I mean, you're explicitly choosing to self-host an alternative backend server which isn't affiliated with Bitwarden. You could have used their SaaS, or self-hosted their official backend they provide on GitHub, for free, and which is almost entirely open source (AGPL, they have some small enterprise specific bits such as SSO which are under a commercial license which is still free, just not open source). But you choose to self-host a random person's project that tries to keep track with Bitwarden APIs and various frontends, on a best effort basis. That's a ton of risk I really wouldn't take with something as sensitive as passwords to everything.

gunalx 2y ago
Its pretty ok as the offical client caches most stuff, everything is still encrypted, and most of all vaultvarden is miles easier to self host than the offical bitwarden stuff.