Vaultwarden Installation error

[webmogul1]

✅ 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

[ja-softdevel]

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

[tomtheswede]

I get the same error

[Jimbambuli]

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

[tgtechy]

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

[goozoon]

just tried to install and got the same Error

[kintaro1981]

same error here

[MickLesk]

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.

[datOlle]

Update runs now without error

[tgtechy]

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.

[datOlle]

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

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

[tremor021]

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