@james Yay it's working again!

Hello @oauth2-tmp-cloudron-1784273754379-im6vnh Please see https://forum.cloudron.io/topic/14812/vaultwarden-fails-to-start-after-update-db-migration-error-sso and apply the fix.

Hi, yes, this did the job. Should have seen this post as relevant for me too, but didnt. So thanks again!

Hello @christophermag Thanks for reporting the update resolved the issue.

James, I found the solution. I forget to add {} before and after the variable, that makes my config.json error. Now, it's solved. { "signups_allowed": false, "invitations_allowed": true, }

Thanks for the heads up - no impact on vaultwarden apparently: https://github.com/dani-garcia/vaultwarden/discussions/7126

@inibudi the latest vaultwarden package already supports Cloudron OpenID. Thanks for getting back though.

Hello @dimtar We have a documentation for exactly that. See https://docs.cloudron.io/packages/vaultwarden#admin

Yes, it is set to false. Maybe I was tricked because I had one Domain whitelisted. I don't remember if the "Register"-Link was always there. Would love to hide it. It seems, that the disabled registration does work. Sorry for alerting...

This is getting updated - https://git.cloudron.io/packages/vaultwarden-app/-/merge_requests/20

By the way, Vaultwarden itself is fine with assets living elsewhere. You can use surfer to host for example logo files and then drop the link in the user.vaultwarden.scss.hbs file.

@jdaviescoates the comment in the package says there are some values that can only be set in env . But I cannot find what they are . AFAICT, it is safe to empty it out.

@girish Hello i confirm, the update fix the issue thank you

@necrevistonnezr my installation is quite old - that's correct. Thanks for checking in! @girish , thank you for the doc's reference! Guess it might make sense to stress that during the installation, as well as an offer to increase KDF up to 2 mln (as per Bitwarden docs as well).