Vaultwarden Update - to fix current issue with mismatch of server and client versions disallowing users to log in from app

[gh3597]

I have some users on the Android app version 2026.2.0 which I believe requires server version 1.35.x but updating using dietpi-software reinstall 183 and it installs 1.34.3. Any chance of getting 1.35.3 packaged soon before everyone updates the app? Luckily only some users have updated so far so the issue isn't widespread (for me at least).

[MichaIng]

v1.35.3 should be available. Can you check this:

root@micha:~# apt policy vaultwarden
vaultwarden:
  Installed: (none)
  Candidate: 1.35.3-dietpi1
  Version table:
     1.35.3-dietpi1 500
        500 https://dietpi.com/apt forky/main arm64 Packages
     1.35.2-dietpi1 500
        500 https://dietpi.com/apt forky/main arm64 Packages
     1.35.1-dietpi1 500
        500 https://dietpi.com/apt forky/main arm64 Packages
     1.34.3-dietpi2 500
        500 https://dietpi.com/apt forky/main arm64 Packages

Generally, no reinstall is needed, just apt upgrade.

[gh3597]

OK this pointed me in the right direction... I think as there was no update message when I logged in I thought I was up to date but I'm still on Bullseye so I guess I need to look to update that before I see an update message?

For reference as per above I get 3.34.3 as the policy target so I am assuming once I have updated to Trixie I'll get the latest. I'll report back shortly....

[gh3597]

Updated to Bookwork and checked along the way and Vaultwarden has updated so seems it was my lack of Linux knowledge here missed the underlying issue.

Also not sure why I have the reinstall command down for an update. I think I was looking for ways to update Vaultwarden (or maybe some other package on on another DietPi installation) and that method was suggested. I think I just took it that that was how you updated software packages in DietPi. Most of my DietPi installs don't use the built in software so it's not something I do a lot of. Seems I can stop doing it I suppose.

[gh3597]

And just to confuse me even further there was a release of Vaultwarden to 1.35.4 2 minutes ago so I was wondering why it still wasn't showing "latest" when checking in the admin panel!

I am now running Trixie and 1.35.3 though so I think we have solved the original issue.

[MichaIng]

A reinstall works as well, but often it is overkill. If unsure, check the docs: https://dietpi.com/docs/software/cloud/#vaultwarden-update-to-latest-version

Makes sense regarding Bullseye updates: we stopped building new packages for Bullseye after dropping support for it with DietPi v10.0. The vaultwarden 1.35.0 release came a week too late 😄. All supported distro versions get all updates. The DietPi major version indicates which Debian version is supported. v10.x requires Bookworm at least, v11.x will require Debian Trixie at least, but still 2 years to go.

[MichaIng]

What a timing: https://github.com/dani-garcia/vaultwarden/releases/tag/1.35.4
Builds triggered: https://github.com/MichaIng/DietPi/actions/runs/22327270472