[1.26.2]
Update vaultwarden to 1.37.2
Full Changelog
This update is required for support with clients with version 2026.8.0+, please update before reporting any issues with them.
Fix Debian cross-linking with xx-cargo by @alexliluz in #7524
Fix playwright test by @Timshel in #7548
Misc fixes and updates by @BlackDex in #7558
Include user email in successful login logs by @lmogthb in #7496
Fix sendmail executable permission check by @p-boenisch in #7483
add dummy revisionDate by @stefan0xC in #7608
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.
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,
}
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...
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.
@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).
