starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Alpine Vaultwarden does not update webvault #120

New Issue
Closed
opened 2026-02-04 16:43:25 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-04 16:43:25 +03:00
Owner
Copy Link

Originally created by @LilTrublMakr on GitHub (Nov 30, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

When using the script to update Vaultwarden, it does not update the webvault. The script does update the webvault ("(81/81) Upgrading vaultwarden-web-vault (1.31.0-r0 -> 1.32.5-r0)"), it does not actually update it. When updated, the webvault would still be running the old version of the webvault.

In todays example, I was running "Vaultwarden Web Version 2024.5.0",and after the update, it stayed the same even after a restart.

To fix this, I had to manually update the webvault using the following:

WEBVAULT=$(curl -s https://api.github.com/repos/dani-garcia/bw_web_builds/releases/latest |
  grep "tag_name" |
  awk '{print substr($2, 2, length($2)-3) }')
curl -fsSLO https://github.com/dani-garcia/bw_web_builds/releases/download/$WEBVAULT/bw_web_$WEBVAULT.tar.gz
tar -xvzf bw_web_$WEBVAULT.tar.gz
rm -r /var/lib/vaultwarden/web-vault
mv ./web-vault/ /var/lib/vaultwarden/
rc-service vaultwarden restart

What settings are you currently utilizing?

  • Default Settings
  • Advanced Settings

Which Linux distribution are you employing?

Alpine

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

No response

Originally created by @LilTrublMakr on GitHub (Nov 30, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. When using the script to update Vaultwarden, it does not update the webvault. The script does update the webvault ("(81/81) Upgrading vaultwarden-web-vault (1.31.0-r0 -> 1.32.5-r0)"), it does not actually update it. When updated, the webvault would still be running the old version of the webvault. In todays example, I was running "Vaultwarden Web Version 2024.5.0",and after the update, it stayed the same even after a restart. To fix this, I had to manually update the webvault using the following: ``` WEBVAULT=$(curl -s https://api.github.com/repos/dani-garcia/bw_web_builds/releases/latest | grep "tag_name" | awk '{print substr($2, 2, length($2)-3) }') curl -fsSLO https://github.com/dani-garcia/bw_web_builds/releases/download/$WEBVAULT/bw_web_$WEBVAULT.tar.gz tar -xvzf bw_web_$WEBVAULT.tar.gz rm -r /var/lib/vaultwarden/web-vault mv ./web-vault/ /var/lib/vaultwarden/ rc-service vaultwarden restart ``` ### What settings are you currently utilizing? - [X] Default Settings - [X] Advanced Settings ### Which Linux distribution are you employing? Alpine ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. _No response_
OVERLORD commented 2026-02-04 16:43:31 +03:00
Author
Owner
Copy Link

@towerhand commented on GitHub (Dec 1, 2024):

This is what it shows in my diagnostics page in the admin panel, which seems like everything is up to date.

Versions:

  • Server Installed Update
    1.32.5-r0
    Server Latest
    1.32.5-da3701c0

  • Web Installed
    2024.6.2c
    Web Latest
    2024.6.2c

@towerhand commented on GitHub (Dec 1, 2024): This is what it shows in my diagnostics page in the admin panel, which seems like everything is up to date. Versions: - Server Installed Update 1.32.5-r0 Server Latest 1.32.5-da3701c0 - Web Installed 2024.6.2c Web Latest 2024.6.2c
OVERLORD commented 2026-02-04 16:43:41 +03:00
Author
Owner
Copy Link

@LilTrublMakr commented on GitHub (Dec 1, 2024):

That is what I am currently getting as well, but it is after I had to manually update the web vault. Before that my Vaultwarden login screen was showing "Version 2023.5.0" which made me think 'this seems really old... I wonder if there's an update...'

For the Alpine variant, I think the script is updating the binary web vault, but is not using the binary version.

@LilTrublMakr commented on GitHub (Dec 1, 2024): That is what I am currently getting as well, but it is after I had to manually update the web vault. Before that my Vaultwarden login screen was showing "Version 2023.5.0" which made me think 'this seems really old... I wonder if there's an update...' For the Alpine variant, I think the script is updating the binary web vault, but is not using the binary version.
OVERLORD commented 2026-02-04 16:43:45 +03:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Dec 5, 2024):

What is your WEB_VAULT_FOLDER setting in /etc/conf.d/vaultwarden?

The default config /etc/conf.d/vaultwarden should correctly point to /usr/share/webapps/vaultwarden-web where the package vaultwarden-web-vault is installed

# /etc/conf.d/vaultwarden
export WEB_VAULT_FOLDER=/usr/share/webapps/vaultwarden-web
@havardthom commented on GitHub (Dec 5, 2024): What is your `WEB_VAULT_FOLDER` setting in `/etc/conf.d/vaultwarden`? The default config `/etc/conf.d/vaultwarden` should correctly point to `/usr/share/webapps/vaultwarden-web` where the package `vaultwarden-web-vault` is installed ``` # /etc/conf.d/vaultwarden export WEB_VAULT_FOLDER=/usr/share/webapps/vaultwarden-web ```
OVERLORD commented 2026-02-04 16:43:53 +03:00
Author
Owner
Copy Link

@LilTrublMakr commented on GitHub (Dec 6, 2024):

Ah. Looks like this was changed all the way back in June 2023... e1037834d7

@LilTrublMakr commented on GitHub (Dec 6, 2024): Ah. Looks like this was changed all the way back in June 2023... https://github.com/community-scripts/ProxmoxVE/commit/e1037834d7e5cd02cf599223e2be5ddc95f75ce2
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#120
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?