[GH-ISSUE #11771] Vaultwarden update #2476

Closed
opened 2026-02-26 12:52:35 +03:00 by kerem · 11 comments
Owner

Originally created by @Kitchigo on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11771

Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

Vaultwarden

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/vaultwarden.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

8.4.14 | 6.8.12-15-pve

📝 Provide a clear and concise description of the issue.

Hello, I have a problem, it clearly states that the update was successful, but when I check the version it is still at 1.34.2.

Image Image

🔄 Steps to reproduce the issue.

Update the lxc

Paste the full error output (if available).

no

🖼️ Additional context (optional).

No response

Originally created by @Kitchigo on GitHub (Feb 10, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11771 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? Vaultwarden ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/vaultwarden.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 8.4.14 | 6.8.12-15-pve ### 📝 Provide a clear and concise description of the issue. Hello, I have a problem, it clearly states that the update was successful, but when I check the version it is still at 1.34.2. <img width="742" height="140" alt="Image" src="https://github.com/user-attachments/assets/948acafd-fc7a-4426-b06b-8b14d6ce9c37" /> <img width="841" height="292" alt="Image" src="https://github.com/user-attachments/assets/aa7c1457-9277-4bb3-a45a-127717ba8755" /> ### 🔄 Steps to reproduce the issue. Update the lxc ### ❌ Paste the full error output (if available). no ### 🖼️ Additional context (optional). _No response_
kerem 2026-02-26 12:52:35 +03:00
Author
Owner

@MickLesk commented on GitHub (Feb 10, 2026):

Its correct. The Version Number is not updated.

<!-- gh-comment-id:3880391698 --> @MickLesk commented on GitHub (Feb 10, 2026): Its correct. The Version Number is not updated.
Author
Owner

@pictosun commented on GitHub (Feb 11, 2026):

For me today it updated to 1.35.3

But web vault says it's 2025.12.1 as the actual version is 2026.1.1

<!-- gh-comment-id:3884930744 --> @pictosun commented on GitHub (Feb 11, 2026): For me today it updated to 1.35.3 But web vault says it's` 2025.12.1` as the actual version is `2026.1.1`
Author
Owner

@MickLesk commented on GitHub (Feb 11, 2026):

nope isnt. the latest release is v2025.12.1+build.3 Latest

<!-- gh-comment-id:3885017991 --> @MickLesk commented on GitHub (Feb 11, 2026): nope isnt. the latest release is [v2025.12.1+build.3](https://github.com/dani-garcia/bw_web_builds/releases/tag/v2025.12.1%2Bbuild.3) [Latest](https://github.com/dani-garcia/bw_web_builds/releases/latest)
Author
Owner

@pictosun commented on GitHub (Feb 11, 2026):

nope - you're wrong. latest release is v2026.1.1 https://github.com/dani-garcia/bw_web_builds/releases/tag/v2026.1.1

<!-- gh-comment-id:3885796212 --> @pictosun commented on GitHub (Feb 11, 2026): nope - you're wrong. latest release is v2026.1.1 https://github.com/dani-garcia/bw_web_builds/releases/tag/v2026.1.1
Author
Owner

@MickLesk commented on GitHub (Feb 11, 2026):

Nope. Its Not latest.

<!-- gh-comment-id:3885855409 --> @MickLesk commented on GitHub (Feb 11, 2026): Nope. Its Not latest.
Author
Owner

@KaelanTesseract commented on GitHub (Feb 17, 2026):

Can you update the script pls for updating on latest release? https://github.com/dani-garcia/bw_web_builds/releases/latest

<!-- gh-comment-id:3917097080 --> @KaelanTesseract commented on GitHub (Feb 17, 2026): Can you update the script pls for updating on latest release? https://github.com/dani-garcia/bw_web_builds/releases/latest
Author
Owner

@MickLesk commented on GitHub (Feb 17, 2026):

Script Always use latest. Now its marked as latest and our build process use this as latest

<!-- gh-comment-id:3917109288 --> @MickLesk commented on GitHub (Feb 17, 2026): Script Always use latest. Now its marked as latest and our build process use this as latest
Author
Owner

@KaelanTesseract commented on GitHub (Feb 17, 2026):

But it dont work für Alpine version than.
It installed still 2025.12.1

<!-- gh-comment-id:3917111921 --> @KaelanTesseract commented on GitHub (Feb 17, 2026): But it dont work für Alpine version than. It installed still 2025.12.1
Author
Owner

@MickLesk commented on GitHub (Feb 17, 2026):

Alpine is Not maintained by us or Dani, its another Dev. Alpine need every Release some time. We and Dani doesnt have any affect on alpine packages

<!-- gh-comment-id:3917118504 --> @MickLesk commented on GitHub (Feb 17, 2026): Alpine is Not maintained by us or Dani, its another Dev. Alpine need every Release some time. We and Dani doesnt have any affect on alpine packages
Author
Owner

@KaelanTesseract commented on GitHub (Feb 17, 2026):

Oh okey good to know. thank you

<!-- gh-comment-id:3917123329 --> @KaelanTesseract commented on GitHub (Feb 17, 2026): Oh okey good to know. thank you
Author
Owner

@frankkubler commented on GitHub (Feb 18, 2026):

Latest Vaultwarden is available in Alpine Edge Repo.
I follow these steps to upgrade :
Alpine Edge Vaultwarden

Vaultwarden on Alpine Linux edge is available in the latest version as of February 18, 2026.

  • The current vaultwarden package version in the Alpine edge repository is 1.35.3-r0 (for armhf architecture), with a build time of 2026-02-12 15:10:30.
  • The corresponding vaultwarden-web-vault package is at version 1.35.2-r0, built on 2026-01-20 11:30:43.
  • To ensure you’re using the latest edge packages, verify your /etc/apk/repositories file includes the edge branch URLs:
    https://dl-cdn.alpinelinux.org/alpine/edge/main
    https://dl-cdn.alpinelinux.org/alpine/edge/community
    https://dl-cdn.alpinelinux.org/alpine/edge/testing
    
  • Run the following commands to update and install:
    sudo apk update
    sudo apk upgrade
    sudo apk add vaultwarden
    

⚠️ Using edge provides rolling updates but may introduce instability. Always verify compatibility in your environment.

<!-- gh-comment-id:3919929790 --> @frankkubler commented on GitHub (Feb 18, 2026): Latest Vaultwarden is available in Alpine Edge Repo. I follow these steps to upgrade : Alpine Edge Vaultwarden **Vaultwarden** on **Alpine Linux edge** is available in the latest version as of February 18, 2026. - The current **vaultwarden** package version in the Alpine `edge` repository is **1.35.3-r0** (for `armhf` architecture), with a build time of **2026-02-12 15:10:30**. - The corresponding **vaultwarden-web-vault** package is at version **1.35.2-r0**, built on **2026-01-20 11:30:43**. - To ensure you’re using the latest edge packages, verify your `/etc/apk/repositories` file includes the `edge` branch URLs: ``` https://dl-cdn.alpinelinux.org/alpine/edge/main https://dl-cdn.alpinelinux.org/alpine/edge/community https://dl-cdn.alpinelinux.org/alpine/edge/testing ``` - Run the following commands to update and install: ```bash sudo apk update sudo apk upgrade sudo apk add vaultwarden ``` > ⚠️ Using `edge` provides rolling updates but may introduce instability. Always verify compatibility in your environment.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#2476
No description provided.