Update breaks Vaultwarden Web-Vault #2433

Closed
opened 2026-02-05 04:50:36 +03:00 by OVERLORD · 13 comments
Owner

Originally created by @johanngrobe on GitHub (Feb 2, 2026).

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?

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

9.1.4

📝 Provide a clear and concise description of the issue.

I updated vaultwarden with this weird message but everything worked fine.

✔️ Update available: vaultwarden not installed → 1.35.2

After trying to update the web-vault vaultwarden is broken. The update exits with an error In /opt/vaultwarden the folder structure is messed up. Before there were three folders only: bin, data and web-vault. Afterwards it's chaotic. It seems like web-vault gets deployed into the wrong folder.

🔄 Steps to reproduce the issue.

update web-vault

Paste the full error output (if available).

  ✔️   Update available: vaultwarden_webvault not installed → 2025.12.1+build.3
  ✔️   Stopped Service
  ✔️   Deployed: vaultwarden_webvault (2025.12.1+build.3)
  ⏳   Updating Web-Vault to 2025.12.1+build.3chown: cannot access '/opt/vaultwarden/web-vault/': No such file or directory
  ✖️   in line 79: exit code 1 (General error / Operation not permitted): while executing command chown -R 
root:root /opt/vaultwarden/web-vault/
root@vaultwarden:/opt/vaultwarden# ls
155.d06fd751c6eeada1c84d.js      573.b479891548a93d8f2e45.js.map  app                               redirect-connector.html
155.d06fd751c6eeada1c84d.js.map  614.0e7b2be70c6c17f67282.js      app-id.json                       scripts
281.7b08cb8ad5fa80c3817b.js      614.0e7b2be70c6c17f67282.js.map  bd26f4a708570b994235.module.wasm  sso-connector.html
281.7b08cb8ad5fa80c3817b.js.map  677.98a0060cb9547db54359.js      bin                               styles.31d6cfe0d16ae931b73c.js
35.a5925037071c7d20e7c0.js       677.98a0060cb9547db54359.js.map  browserconfig.xml                 styles.f5ed5f8f9da818a932a3.css
35.a5925037071c7d20e7c0.js.map   712.36ecc57259a750067d7a.js      cca56971e438d22818d6.json         styles.f5ed5f8f9da818a932a3.css.map
404.html                         712.36ecc57259a750067d7a.js.map  connectors                        theme_head.6991036cc6ce1ab5eee1.js
449.f9ec1c26355fef21d987.js      782.212b9500d97dd24d74d2.js      data                              theme_head.6991036cc6ce1ab5eee1.js.map
449.f9ec1c26355fef21d987.js.map  782.212b9500d97dd24d74d2.js.map  duo-redirect-connector.html       version.json
453.fbb85954401903bbb832.js      825.acb40a4bcb87700046f9.js      favicon.ico                       videos
453.fbb85954401903bbb832.js.map  825.acb40a4bcb87700046f9.js.map  fonts                             vw-version.json
502.ae02d12143fe68d21925.js      830.a7b806778339c8af4112.js      images                            webauthn-connector.html
531.109af8fb049dada330e0.js      830.a7b806778339c8af4112.js.map  index.html                        webauthn-fallback-connector.html
531.109af8fb049dada330e0.js.map  922.ffc2c4af29e797b0de35.js      locales                           webauthn-mobile-connector.html
573.b479891548a93d8f2e45.js      922.ffc2c4af29e797b0de35.js.map  manifest.json

🖼️ Additional context (optional).

No response

Originally created by @johanngrobe on GitHub (Feb 2, 2026). ### ✅ 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? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 9.1.4 ### 📝 Provide a clear and concise description of the issue. I updated vaultwarden with this weird message but everything worked fine. ` ✔️ Update available: vaultwarden not installed → 1.35.2` After trying to update the web-vault vaultwarden is broken. The update exits with an error In `/opt/vaultwarden` the folder structure is messed up. Before there were three folders only: `bin`, `data` and `web-vault`. Afterwards it's chaotic. It seems like web-vault gets deployed into the wrong folder. ### 🔄 Steps to reproduce the issue. update web-vault ### ❌ Paste the full error output (if available). ``` ✔️ Update available: vaultwarden_webvault not installed → 2025.12.1+build.3 ✔️ Stopped Service ✔️ Deployed: vaultwarden_webvault (2025.12.1+build.3) ⏳ Updating Web-Vault to 2025.12.1+build.3chown: cannot access '/opt/vaultwarden/web-vault/': No such file or directory ✖️ in line 79: exit code 1 (General error / Operation not permitted): while executing command chown -R root:root /opt/vaultwarden/web-vault/ ``` ``` root@vaultwarden:/opt/vaultwarden# ls 155.d06fd751c6eeada1c84d.js 573.b479891548a93d8f2e45.js.map app redirect-connector.html 155.d06fd751c6eeada1c84d.js.map 614.0e7b2be70c6c17f67282.js app-id.json scripts 281.7b08cb8ad5fa80c3817b.js 614.0e7b2be70c6c17f67282.js.map bd26f4a708570b994235.module.wasm sso-connector.html 281.7b08cb8ad5fa80c3817b.js.map 677.98a0060cb9547db54359.js bin styles.31d6cfe0d16ae931b73c.js 35.a5925037071c7d20e7c0.js 677.98a0060cb9547db54359.js.map browserconfig.xml styles.f5ed5f8f9da818a932a3.css 35.a5925037071c7d20e7c0.js.map 712.36ecc57259a750067d7a.js cca56971e438d22818d6.json styles.f5ed5f8f9da818a932a3.css.map 404.html 712.36ecc57259a750067d7a.js.map connectors theme_head.6991036cc6ce1ab5eee1.js 449.f9ec1c26355fef21d987.js 782.212b9500d97dd24d74d2.js data theme_head.6991036cc6ce1ab5eee1.js.map 449.f9ec1c26355fef21d987.js.map 782.212b9500d97dd24d74d2.js.map duo-redirect-connector.html version.json 453.fbb85954401903bbb832.js 825.acb40a4bcb87700046f9.js favicon.ico videos 453.fbb85954401903bbb832.js.map 825.acb40a4bcb87700046f9.js.map fonts vw-version.json 502.ae02d12143fe68d21925.js 830.a7b806778339c8af4112.js images webauthn-connector.html 531.109af8fb049dada330e0.js 830.a7b806778339c8af4112.js.map index.html webauthn-fallback-connector.html 531.109af8fb049dada330e0.js.map 922.ffc2c4af29e797b0de35.js locales webauthn-mobile-connector.html 573.b479891548a93d8f2e45.js 922.ffc2c4af29e797b0de35.js.map manifest.json ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 04:50:36 +03:00
Author
Owner

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

Why?
It worked smooth at my system. How old is yours? What are other paths?

@MickLesk commented on GitHub (Feb 2, 2026): Why? It worked smooth at my system. How old is yours? What are other paths?
Author
Owner

@johanngrobe commented on GitHub (Feb 2, 2026):

On The Website it states Vaultwarden Web Version 2025.1.1.

I only installed vaultwarden last summer and updated somewhat regularly.

@johanngrobe commented on GitHub (Feb 2, 2026): On The Website it states `Vaultwarden Web Version 2025.1.1`. I only installed vaultwarden last summer and updated somewhat regularly.
Author
Owner

@johanngrobe commented on GitHub (Feb 2, 2026):

This is from the update script. It removes the web-vault folder first and then tries to chown. This does not make any sense.

      msg_info "Updating Web-Vault to $WVRELEASE"
      rm -rf /opt/vaultwarden/web-vault
      chown -R root:root /opt/vaultwarden/web-vault/
      msg_ok "Updated Web-Vault to ${WVRELEASE}"
@johanngrobe commented on GitHub (Feb 2, 2026): This is from the update script. It removes the web-vault folder first and then tries to chown. This does not make any sense. ``` msg_info "Updating Web-Vault to $WVRELEASE" rm -rf /opt/vaultwarden/web-vault chown -R root:root /opt/vaultwarden/web-vault/ msg_ok "Updated Web-Vault to ${WVRELEASE}" ```
Author
Owner

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

can you try again? edit /root/.vaultwarden_webvault with old version and try again

@MickLesk commented on GitHub (Feb 2, 2026): can you try again? edit /root/.vaultwarden_webvault with old version and try again
Author
Owner

@johanngrobe commented on GitHub (Feb 2, 2026):

it still does not work.

the script removes /opt/vaultwarden/web-vault but never recreates it. Shoundn't it deploy the web-vault into /opt/vaultwarden/web-vault?
fetch_and_deploy_gh_release "vaultwarden_webvault" "dani-garcia/bw_web_builds" "prebuild" "latest" "/opt/vaultwarden" "bw_web_*.tar.gz"

@johanngrobe commented on GitHub (Feb 2, 2026): it still does not work. the script removes `/opt/vaultwarden/web-vault` but never recreates it. Shoundn't it deploy the web-vault into /`opt/vaultwarden/web-vault`? ` fetch_and_deploy_gh_release "vaultwarden_webvault" "dani-garcia/bw_web_builds" "prebuild" "latest" "/opt/vaultwarden" "bw_web_*.tar.gz" `
Author
Owner

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

should work. ive pushed an temp_dir

@MickLesk commented on GitHub (Feb 2, 2026): should work. ive pushed an temp_dir
Author
Owner

@johanngrobe commented on GitHub (Feb 2, 2026):

nope.

  ✔️   Deployed: vaultwarden_webvault (2025.12.1+build.3)
mv: cannot stat '/tmp/tmp.0qNKvMLPZi/web-vault': No such file or directory
  ✖️   in line 80: exit code 1 (General error / Operation not permitted): while executing command mv "$TEMP_DIR/web-vault" /opt/vaultwarden/web-vault
@johanngrobe commented on GitHub (Feb 2, 2026): nope. ``` ✔️ Deployed: vaultwarden_webvault (2025.12.1+build.3) mv: cannot stat '/tmp/tmp.0qNKvMLPZi/web-vault': No such file or directory ✖️ in line 80: exit code 1 (General error / Operation not permitted): while executing command mv "$TEMP_DIR/web-vault" /opt/vaultwarden/web-vault ```
Author
Owner

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

now?

@MickLesk commented on GitHub (Feb 2, 2026): now?
Author
Owner

@johanngrobe commented on GitHub (Feb 2, 2026):

Glad the solution I suggested above works. I was able to update successfully. Thank you!

@johanngrobe commented on GitHub (Feb 2, 2026): Glad the solution I suggested above works. I was able to update successfully. Thank you!
Author
Owner

@schneider-de-com commented on GitHub (Feb 3, 2026):

My update for Vaultwarden Core has been running for 30 minutes now, and it's still not finished. I also received a message saying that no installation was found.

Normally, the Core update takes less than 5 minutes.

@schneider-de-com commented on GitHub (Feb 3, 2026): My update for Vaultwarden Core has been running for 30 minutes now, and it's still not finished. I also received a message saying that no installation was found. Normally, the Core update takes less than 5 minutes.
Author
Owner

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

ok

@MickLesk commented on GitHub (Feb 3, 2026): ok
Author
Owner

@schneider-de-com commented on GitHub (Feb 3, 2026):

The update process is complete, but it took a very long time. However, the comparison between the old and new installations looks good. The update of the web interface also worked.

@schneider-de-com commented on GitHub (Feb 3, 2026): The update process is complete, but it took a very long time. However, the comparison between the old and new installations looks good. The update of the web interface also worked.
Author
Owner

@schneider-de-com commented on GitHub (Feb 3, 2026):

Sorry for the noise.

@schneider-de-com commented on GitHub (Feb 3, 2026): Sorry for the noise.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2433