The script "Vaultwarden" does not check if the installed version is the latest #995

Open
opened 2025-11-20 04:57:47 -05:00 by saavagebueno · 0 comments
Owner

Originally created by @ManuelDrescher on GitHub (Apr 28, 2025).

Have you read and understood the above guidelines?

yes

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

vaultwarden.sh

📂 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

📝 Provide a clear and concise description of the issue.

If you are using the "update"-command, the script does not check if the installed version is the latest.

Vaultwarden/Webwarden is rebuilt every time without any demand....which logically takes time.
And if the build process is started and you recognize "Oh, it is the same version"...that`s it, you have to wait until it is finished.

In practice and in many cases, an "update"-command results in rebuilding the already installed (latest) version
again and again...until a more current version is available.

Other scripts are checking if the installed version is the latest, so i would mark this as a "Bug".

🔄 Steps to reproduce the issue.

Install Vaultwarden via PVE-Node-Shell:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/vaultwarden.sh)

Run the update command in the LXC and select Vault- or Webwarden to update:
update

Paste the full error output (if available).

No error output available in this case.

🖼️ Additional context (optional).

No response

Originally created by @ManuelDrescher on GitHub (Apr 28, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? vaultwarden.sh ### 📂 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 - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. If you are using the "update"-command, the script does not check if the installed version is the latest. Vaultwarden/Webwarden is rebuilt every time without any demand....which logically takes time. And if the build process is started and you recognize "Oh, it is the same version"...that`s it, you have to wait until it is finished. In practice and in many cases, an "update"-command results in rebuilding the already installed (latest) version again and again...until a more current version is available. Other scripts are checking if the installed version is the latest, so i would mark this as a "Bug". ### 🔄 Steps to reproduce the issue. Install Vaultwarden via PVE-Node-Shell: `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/vaultwarden.sh)` Run the update command in the LXC and select Vault- or Webwarden to update: `update` ### ❌ Paste the full error output (if available). No error output available in this case. ### 🖼️ Additional context (optional). _No response_
saavagebueno added the not a script issuebugnice to have labels 2025-11-20 04:57:47 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#995