If you got the automatic updates on the bitwarden clients, they will show an empty vault if you are selfhosting vaultwarden.
It seems to be an accidental bug in the bitwarden clients that are assuming that they’re talking with official servers
It’s fixed with the latest release of the vaultwarden server that was published a few minutes ago
I run watchtower on a cron schedule. It had already fired for today, so it wouldn’t have run again until tomorrow. I could have waited, but manual is just as easy.
Be aware that watchtowerr is not updated anymore and due to the nature of having access to the socket is a security risk.
That’s one of the joys of FOSS, when the dev for a popular project can’t continue; there’s often someone willing to pick up the torch and carry it forward.
I switched to this fork when the one you’re thinking of ended development.
https://github.com/nicholas-fedor/watchtower
Last update 3 days ago.