Hopefully it also enables mobile app support for passkeys.

@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:

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.

Sorry for the previous posts.

It just turns out that something may have been up with Chrome on Windows.
On September 6, they released a new version 117, where they disabled SHA-1 fingerprint, and since then I've had problems with the token on Let's Encrypt certificates with ECC 384bit.
Only today after updating to version 118, it just started working as it should properly even in the „Enchanced protection” mode in the security built into Chrome.

@RazielKanos so your issue is related to https://github.com/dani-garcia/vaultwarden/issues/3819 I think.

My issue is similar to https://github.com/dani-garcia/vaultwarden/issues/3820

@girish Ha! I was one tiny update behind 😁

oh, it never occurred to me to create it.. again..because in the admin console you've already 'created' the account. Shame it doesn't say 'create master password'.

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!

I have created a new thread for documentation here:
https://forum.cloudron.io/topic/9462/cloudron-documentation-ideas/2

I think @girish talents are too precious to be used on documentation and that the community may well prefer him to be focused on something else.

There is nothing in the logs...
I will do what @scooke suggested.... sadly