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 13 Packages Projects Releases 10 Wiki Activity

Vaultwarden Installation error #749

New Issue
Closed
opened 2026-02-04 21:13:45 +03:00 by OVERLORD · 14 comments
OVERLORD commented 2026-02-04 21:13:45 +03:00
Owner
Copy Link

Originally created by @webmogul1 on GitHub (Apr 4, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 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)"

📝 Provide a clear and concise description of the issue.

error while installing it.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

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

❌ Paste the full error output (if available).

 _    __            ____                          __         
| |  / /___ ___  __/ / /__      ______ __________/ /__  ____ 
| | / / __ `/ / / / / __/ | /| / / __ `/ ___/ __  / _ \/ __ \
| |/ / /_/ / /_/ / / /_ | |/ |/ / /_/ / /  / /_/ /  __/ / / /
|___/\__,_/\__,_/_/\__/ |__/|__/\__,_/_/   \__,_/\___/_/ /_/ 
                                                             
  ⚙️  Using Default Settings on node pve03
  🖥️  Operating System: debian
  🌟  Version: 12
  📦  Container Type: Unprivileged
  💾  Disk Size: 6 GB
  🧠  CPU Cores: 4
  🛠️  RAM Size: 6144 MiB
  🆔  Container ID: 102
  🚀  Creating a Vaultwarden LXC using the above default settings
  
  ✔️  Using local-zfs for Template Storage.
  ✔️  Using local-zfs for Container Storage.
  ✔️  Updated LXC Template List
  ✔️  LXC Template is ready to use.
  ✔️  LXC Container 102 was successfully created.
  ✔️   Started LXC Container
  ✔️  Set up Container OS
  ✔️  Network Connected: 10.0.1.222 
  ✔️  IPv4 Internet Connected
  ✖️  IPv6 Internet Not Connected
  ✔️  DNS Resolved github.com to 140.82.114.4
  ✔️  Updated Container OS
  ✔️  Core dependencies installed
  ✔️  Installed Dependencies
  ✔️  Installed Rust
 ⠼ Building Vaultwarden 1.33.2 (Patience) 
[ERROR] in line 50: exit code 0: while executing command "$@" > /dev/null 2>&1
The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output.
root@pve03:~#

second try

 ⠹   Compiling miniz_oxide v0.8.7
error: failed to run custom build command for `mysqlclient-sys v0.4.4`

Caused by:
  process didn't exit successfully: `/vaultwarden/target/release/build/mysqlclient-sys-a3020e2eebb801cc/build-script-build` (exit status: 101)
  --- stdout
  cargo::rerun-if-env-changed=MYSQLCLIENT_VERSION
  cargo::rerun-if-env-changed=MYSQLCLIENT_INCLUDE_DIR
  cargo::rerun-if-env-changed=MYSQLCLIENT_INCLUDE_DIR_X86_64_UNKNOWN_LINUX_GNU
  cargo::rerun-if-env-changed=MYSQLCLIENT_LIB
  cargo::rerun-if-env-changed=MYSQLCLIENT_LIB_DIR
  cargo::rerun-if-env-changed=MYSQLCLIENT_LIB_DIR_X86_64_UNKNOWN_LINUX_GNU
  cargo::rerun-if-env-changed=MYSQLCLIENT_LIBNAME
  cargo::rerun-if-env-changed=MYSQLCLIENT_LIBNAME_X86_64_UNKNOWN_LINUX_GNU
  cargo::rerun-if-env-changed=MYSQLCLIENT_STATIC
  cargo::rerun-if-env-changed=MYSQLCLIENT_VERSION_X86_64_UNKNOWN_LINUX_GNU
  cargo::rerun-if-env-changed=MYSQLCLIENT_LIB_X86_64_UNKNOWN_LINUX_GNU
  cargo::rerun-if-env-changed=MYSQLCLIENT_STATIC_X86_64_UNKNOWN_LINUX_GNU
  cargo:rerun-if-env-changed=MYSQLCLIENT_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=MYSQLCLIENT_STATIC
  cargo:rerun-if-env-changed=MYSQLCLIENT_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=SYSROOT
  cargo:rerun-if-env-changed=MYSQLCLIENT_STATIC
  cargo:rerun-if-env-changed=MYSQLCLIENT_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rustc-link-search=native=/usr/lib/x86_64-linux-gnu/
  cargo:rustc-link-lib=mariadb
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=MYSQLCLIENT_STATIC
  cargo:rerun-if-env-changed=MYSQLCLIENT_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=TARGET
  cargo:rerun-if-env-changed=BINDGEN_EXTRA_CLANG_ARGS_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=BINDGEN_EXTRA_CLANG_ARGS_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=BINDGEN_EXTRA_CLANG_ARGS
  cargo:rerun-if-changed=bindings/wrapper.h

  --- stderr

  thread 'main' panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/bindgen-0.71.1/lib.rs:604:27:
  Unable to find libclang: "couldn't find any valid shared libraries matching: ['libclang.so', 'libclang-*.so', 'libclang.so.*', 'libclang-*.so.*'], set the `LIBCLANG_PATH` environment variable to a path where one of these files can be found (invalid: [])"
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
 ⠹
[ERROR] in line 47: exit code 0: while executing command $STD cargo build --features "sqlite,mysql,postgresql" --release
curl: (22) The requested URL returned error: 400
root@pve03:~#

🖼️ Additional context (optional).

No response

Originally created by @webmogul1 on GitHub (Apr 4, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 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)" ### 📝 Provide a clear and concise description of the issue. error while installing it. ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/vaultwarden.sh)" ### ❌ Paste the full error output (if available). ``` _ __ ____ __ | | / /___ ___ __/ / /__ ______ __________/ /__ ____ | | / / __ `/ / / / / __/ | /| / / __ `/ ___/ __ / _ \/ __ \ | |/ / /_/ / /_/ / / /_ | |/ |/ / /_/ / / / /_/ / __/ / / / |___/\__,_/\__,_/_/\__/ |__/|__/\__,_/_/ \__,_/\___/_/ /_/ ⚙️ Using Default Settings on node pve03 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 💾 Disk Size: 6 GB 🧠 CPU Cores: 4 🛠️ RAM Size: 6144 MiB 🆔 Container ID: 102 🚀 Creating a Vaultwarden LXC using the above default settings ✔️ Using local-zfs for Template Storage. ✔️ Using local-zfs for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✔️ LXC Container 102 was successfully created. ✔️ Started LXC Container ✔️ Set up Container OS ✔️ Network Connected: 10.0.1.222 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ DNS Resolved github.com to 140.82.114.4 ✔️ Updated Container OS ✔️ Core dependencies installed ✔️ Installed Dependencies ✔️ Installed Rust ⠼ Building Vaultwarden 1.33.2 (Patience) [ERROR] in line 50: exit code 0: while executing command "$@" > /dev/null 2>&1 The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output. root@pve03:~# ``` second try ``` ⠹ Compiling miniz_oxide v0.8.7 error: failed to run custom build command for `mysqlclient-sys v0.4.4` Caused by: process didn't exit successfully: `/vaultwarden/target/release/build/mysqlclient-sys-a3020e2eebb801cc/build-script-build` (exit status: 101) --- stdout cargo::rerun-if-env-changed=MYSQLCLIENT_VERSION cargo::rerun-if-env-changed=MYSQLCLIENT_INCLUDE_DIR cargo::rerun-if-env-changed=MYSQLCLIENT_INCLUDE_DIR_X86_64_UNKNOWN_LINUX_GNU cargo::rerun-if-env-changed=MYSQLCLIENT_LIB cargo::rerun-if-env-changed=MYSQLCLIENT_LIB_DIR cargo::rerun-if-env-changed=MYSQLCLIENT_LIB_DIR_X86_64_UNKNOWN_LINUX_GNU cargo::rerun-if-env-changed=MYSQLCLIENT_LIBNAME cargo::rerun-if-env-changed=MYSQLCLIENT_LIBNAME_X86_64_UNKNOWN_LINUX_GNU cargo::rerun-if-env-changed=MYSQLCLIENT_STATIC cargo::rerun-if-env-changed=MYSQLCLIENT_VERSION_X86_64_UNKNOWN_LINUX_GNU cargo::rerun-if-env-changed=MYSQLCLIENT_LIB_X86_64_UNKNOWN_LINUX_GNU cargo::rerun-if-env-changed=MYSQLCLIENT_STATIC_X86_64_UNKNOWN_LINUX_GNU cargo:rerun-if-env-changed=MYSQLCLIENT_NO_PKG_CONFIG cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_PKG_CONFIG cargo:rerun-if-env-changed=PKG_CONFIG cargo:rerun-if-env-changed=MYSQLCLIENT_STATIC cargo:rerun-if-env-changed=MYSQLCLIENT_DYNAMIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH cargo:rerun-if-env-changed=PKG_CONFIG_PATH cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR cargo:rerun-if-env-changed=SYSROOT cargo:rerun-if-env-changed=MYSQLCLIENT_STATIC cargo:rerun-if-env-changed=MYSQLCLIENT_DYNAMIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC cargo:rustc-link-search=native=/usr/lib/x86_64-linux-gnu/ cargo:rustc-link-lib=mariadb cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_PKG_CONFIG cargo:rerun-if-env-changed=PKG_CONFIG cargo:rerun-if-env-changed=MYSQLCLIENT_STATIC cargo:rerun-if-env-changed=MYSQLCLIENT_DYNAMIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH cargo:rerun-if-env-changed=PKG_CONFIG_PATH cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR cargo:rerun-if-env-changed=TARGET cargo:rerun-if-env-changed=BINDGEN_EXTRA_CLANG_ARGS_x86_64-unknown-linux-gnu cargo:rerun-if-env-changed=BINDGEN_EXTRA_CLANG_ARGS_x86_64_unknown_linux_gnu cargo:rerun-if-env-changed=BINDGEN_EXTRA_CLANG_ARGS cargo:rerun-if-changed=bindings/wrapper.h --- stderr thread 'main' panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/bindgen-0.71.1/lib.rs:604:27: Unable to find libclang: "couldn't find any valid shared libraries matching: ['libclang.so', 'libclang-*.so', 'libclang.so.*', 'libclang-*.so.*'], set the `LIBCLANG_PATH` environment variable to a path where one of these files can be found (invalid: [])" note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace warning: build failed, waiting for other jobs to finish... ⠹ [ERROR] in line 47: exit code 0: while executing command $STD cargo build --features "sqlite,mysql,postgresql" --release curl: (22) The requested URL returned error: 400 root@pve03:~# ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bugexternaldependencies labels 2026-02-04 21:13:45 +03:00
OVERLORD commented 2026-02-04 21:13:55 +03:00
Author
Owner
Copy Link

@ja-softdevel commented on GitHub (Apr 4, 2025):

as an fyi, I just setup the alpine-vaultwarden script without issue.

@ja-softdevel commented on GitHub (Apr 4, 2025): as an fyi, I just setup the alpine-vaultwarden script without issue.
OVERLORD commented 2026-02-04 21:14:01 +03:00
Author
Owner
Copy Link

@tomtheswede commented on GitHub (Apr 5, 2025):

I get the same error

@tomtheswede commented on GitHub (Apr 5, 2025): I get the same error
OVERLORD commented 2026-02-04 21:14:08 +03:00
Author
Owner
Copy Link

@Jimbambuli commented on GitHub (Apr 5, 2025):

The update also no longer works:

thread 'main' panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/bindgen-0.71.1/lib.rs:604:27:
Unable to find libclang: "couldn't find any valid shared libraries matching: ['libclang.so', 'libclang-.so', 'libclang.so.', 'libclang-.so.'], set the LIBCLANG_PATH environment variable to a path where one of these files can be found (invalid: [])"
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
⠸ Updating VaultWarden to 1.33.2 (Patience) Building [==============> ] 341/552: rustls, libsqlite3-sys(buil⠼ Updating VaultWarden to 1.33.2 (Patience) Building [==============> ] 342/552: libsqlite3-sys(build) ⠇ Updating VaultWarden to 1.33.2 (Patience)curl: (22) The requested URL returned error: 400

[ERROR] in line 53: exit code 0: while executing command $STD cargo build --features "sqlite,mysql,postgresql" --release

@Jimbambuli commented on GitHub (Apr 5, 2025): The update also no longer works: thread 'main' panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/bindgen-0.71.1/lib.rs:604:27: Unable to find libclang: "couldn't find any valid shared libraries matching: ['libclang.so', 'libclang-*.so', 'libclang.so.*', 'libclang-*.so.*'], set the `LIBCLANG_PATH` environment variable to a path where one of these files can be found (invalid: [])" note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace warning: build failed, waiting for other jobs to finish... ⠸ Updating VaultWarden to 1.33.2 (Patience) Building [==============> ] 341/552: rustls, libsqlite3-sys(buil⠼ Updating VaultWarden to 1.33.2 (Patience) Building [==============> ] 342/552: libsqlite3-sys(build) ⠇ Updating VaultWarden to 1.33.2 (Patience)curl: (22) The requested URL returned error: 400 [ERROR] in line 53: exit code 0: while executing command $STD cargo build --features "sqlite,mysql,postgresql" --release
OVERLORD commented 2026-02-04 21:14:11 +03:00
Author
Owner
Copy Link

@tgtechy commented on GitHub (Apr 5, 2025):

Same error trying an update as @Jimbambuli - earlier versions of script (~ 4 months ago) update worked fine.

@tgtechy commented on GitHub (Apr 5, 2025): Same error trying an **update** as @Jimbambuli - earlier versions of script (~ 4 months ago) update worked fine.
OVERLORD commented 2026-02-04 21:14:21 +03:00
Author
Owner
Copy Link

@goozoon commented on GitHub (Apr 5, 2025):

just tried to install and got the same Error

@goozoon commented on GitHub (Apr 5, 2025): just tried to install and got the same Error
OVERLORD commented 2026-02-04 21:14:28 +03:00
Author
Owner
Copy Link

@kintaro1981 commented on GitHub (Apr 5, 2025):

same error here

@kintaro1981 commented on GitHub (Apr 5, 2025): same error here
OVERLORD commented 2026-02-04 21:14:33 +03:00
Author
Owner
Copy Link

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

Can anyone ask in there repo? We can't do anything about defects in composer or cargo functions, we use what we get. I don't see a script issue here, but rather a problem with the package itself.

@MickLesk commented on GitHub (Apr 5, 2025): Can anyone ask in there repo? We can't do anything about defects in composer or cargo functions, we use what we get. I don't see a script issue here, but rather a problem with the package itself.
OVERLORD commented 2026-02-04 21:14:35 +03:00
Author
Owner
Copy Link

@datOlle commented on GitHub (Apr 6, 2025):

Update runs now without error

@datOlle commented on GitHub (Apr 6, 2025): Update runs now without error
OVERLORD commented 2026-02-04 21:14:42 +03:00
Author
Owner
Copy Link

@tgtechy commented on GitHub (Apr 6, 2025):

I am still getting the same error when attempting an update even after @datOlle comment:

 - Updating VaultWarden to 1.33.2 (Patience)   
[ERROR] in line 85: exit code 0: while executing command cargo build --features "sqlite,mysql,postgresql" --release &> /dev/null

I understand the external dependencies, but since the failed update destroys vaultwarden by

cd ~ && rm -rf vaultwarden

I have to restore from a backup each time the update fails.

@tgtechy commented on GitHub (Apr 6, 2025): I am still getting the same error when attempting an update even after @datOlle comment: ``` - Updating VaultWarden to 1.33.2 (Patience) [ERROR] in line 85: exit code 0: while executing command cargo build --features "sqlite,mysql,postgresql" --release &> /dev/null ``` I understand the external dependencies, but since the failed update destroys vaultwarden by `cd ~ && rm -rf vaultwarden` I have to restore from a backup each time the update fails.
OVERLORD commented 2026-02-04 21:14:51 +03:00
Author
Owner
Copy Link

@datOlle commented on GitHub (Apr 6, 2025):

Yesterday i had the same error, but today it runs smooth

Installed a new one for test and
🚀 Vaultwarden setup has been successfully initialized!

@datOlle commented on GitHub (Apr 6, 2025): Yesterday i had the same error, but today it runs smooth Installed a new one for test and `🚀 Vaultwarden setup has been successfully initialized!`
OVERLORD commented 2026-02-04 21:14:56 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Apr 6, 2025):

I am still getting the same error when attempting an update even after @datOlle comment:

 - Updating VaultWarden to 1.33.2 (Patience)   
[ERROR] in line 85: exit code 0: while executing command cargo build --features "sqlite,mysql,postgresql" --release &> /dev/null

I understand the external dependencies, but since the failed update destroys vaultwarden by

cd ~ && rm -rf vaultwarden

I have to restore from a backup each time the update fails.

yes, thats what backups are for

@tremor021 commented on GitHub (Apr 6, 2025): > I am still getting the same error when attempting an update even after [@datOlle](https://github.com/datOlle) comment: > > ``` > - Updating VaultWarden to 1.33.2 (Patience) > [ERROR] in line 85: exit code 0: while executing command cargo build --features "sqlite,mysql,postgresql" --release &> /dev/null > ``` > > I understand the external dependencies, but since the failed update destroys vaultwarden by > > `cd ~ && rm -rf vaultwarden` > > I have to restore from a backup each time the update fails. yes, thats what backups are for
OVERLORD commented 2026-02-04 21:14:59 +03:00
Author
Owner
Copy Link

@goozoon commented on GitHub (Apr 6, 2025):

just tried to install and got the same Error

Tried just now and:

🚀 Vaultwarden setup has been successfully initialized!

PS: Opening http://192.168.0.40:8000/ - just a spinning Loading... is it ok?

@goozoon commented on GitHub (Apr 6, 2025): > just tried to install and got the same Error Tried just now and: `🚀 Vaultwarden setup has been successfully initialized!` PS: Opening http://192.168.0.40:8000/ - just a spinning Loading... is it ok?
OVERLORD commented 2026-02-04 21:15:06 +03:00
Author
Owner
Copy Link

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

Need https since x versions. Its an restriction of vaultwarden

@MickLesk commented on GitHub (Apr 6, 2025): Need https since x versions. Its an restriction of vaultwarden
OVERLORD commented 2026-02-04 21:15:12 +03:00
Author
Owner
Copy Link

@tgtechy commented on GitHub (Apr 8, 2025):

I gave up trying to update. I created a fresh LXC on proxmox using the helper script and copied the db.sqlite3, attachments and the config.json to the new LXC. I had to chown the db.sqlite3 to vaultwarden from root. The update then worked.

@tgtechy commented on GitHub (Apr 8, 2025): I gave up trying to update. I created a fresh LXC on proxmox using the helper script and copied the db.sqlite3, attachments and the config.json to the new LXC. I had to chown the db.sqlite3 to vaultwarden from root. The update then worked.
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 bug dependencies external
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#749
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?