SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

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

New Issue
Closed
opened 2025-11-20 04:57:50 -05:00 by saavagebueno · 2 comments
saavagebueno commented 2025-11-20 04:57:50 -05:00
Owner
Copy Link

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:50 -05:00
saavagebueno commented 2025-11-20 04:57:51 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Apr 28, 2025):

feel free to build this new ^^ its an tteck script and it worked fine. If the user build every time the same version, its an user issue, not an script issue. The Script doesnt have an RELEASE-Check like other newer scripts, because its too old. We've often had problems with major conversions in the past, so as long as the script works, I'm not going to touch it too much.

@MickLesk commented on GitHub (Apr 28, 2025): feel free to build this new ^^ its an tteck script and it worked fine. If the user build every time the same version, its an user issue, not an script issue. The Script doesnt have an RELEASE-Check like other newer scripts, because its too old. We've often had problems with major conversions in the past, so as long as the script works, I'm not going to touch it too much.
saavagebueno commented 2025-11-20 04:57:51 -05:00
Author
Owner
Copy Link

@ManuelDrescher commented on GitHub (Apr 28, 2025):

OK, I understood :-)

And thank you for your commitment with the Proxmox VE Helper scripts.

@ManuelDrescher commented on GitHub (Apr 28, 2025): OK, I understood :-) And thank you for your commitment with the Proxmox VE Helper scripts.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label bug nice to have not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#998
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?