https://bitwarden.com/download/

The package is already out by now.

@necrevistonnezr Thank you for providing this information. It is really nice to know that although I am not a German taxpayer they are watching my back as well. Much appreciated. @joseph And as usual, Cloudron team is on the ball patching quickly so any exposure is minimized. Well done!

Yup, this time it picked it up properly . https://git.cloudron.io/cloudron/vaultwarden-app/-/merge_requests/4

@necrevistonnezr I've been using it for a while now and did not encounter any problems.

@overholt per https://github.com/dani-garcia/vaultwarden/discussions/4707#discussioncomment-10054929 , it's not released yet.

yeah, it asked me for the master password which is nearly half a book long

Thanks, Girish. So if no Yubikey info is provided then it'll use the default Yubico server which works fine. I knew my issue is a time thing but it wouldn't work even after manually syncing the date/time on the new windows PC. It works ONLY if the settings are as shown in the screenshot below. Obviously, replace with your actual timezone but keep "set time zone automatically" as off. Location services are off too. Make sure to sync afterwards. [image: 1719424074639-a1715119-f03e-45b4-8f80-2cdc03fded93-image.png]

This works fine for me . Cloudron has the latest version.

@andreasdueren Good question. I don't know the answer. Is there something similar for Argon2id parameters?

Just to add, I also experienced exactly this too

@girish thank you for explaining. In my case it is easier to: spin up my old server modify my (local) host file to point the dashboard domain to the old IP use the Cloudron web terminal to access MySQL and apply the fixes press the apps backup button and download to backup config afterwards revert host entries and import the apps backup config on my new Cloudron This way I am only using tools that are already shipped with Cloudron without the need of other software.

@pedrocm looks like you are not getting our mail from support@ ? We cannot make changes to your system without your approval. If you see this message, please get back here or via email (but you are not responding to emails...)

I think I have fixed it - I was not putting it in the custom config.json file. It's all working now. Thanks!

working like a charm now, thanks

wow, finally after weeks of frustration and searching around the internet for a solution @girish solved it!!!!

I'm currently doing the opposite (migrating data from non-Cloudron to Cloudron environment) but I assume it's similar in ways @girish described so just wanted to mention some caveats for people trying this: It's not possible (or at least not trivially possible) to migrate your users. The Vaultwarden docker image uses sqlite while Cloudron uses mysql. The org that I'm trying to migrate has less than 30 users so I'm ok with having to re-invite everyone to the new instance. But if you're trying to migrate a bigger Vaultwarden installation, you'll either have to figure out how to transfer the users between mysql and the sqlite database, or everyone has to create a new account. File attachments have to be copied manually. You can't just scp the attachments folder from one server to the other, this means every attachment has to be downloaded manually through the gui and then uploaded again to the new instance. Exporting and importing the vault itself was a matter of exporting a json file and then importing it in the new vault. Took less than 5 min.