Originally created by @Tropaion on GitHub (Sep 1, 2023).
Subject of the issue
Hello,
I'm just updated to the latest vaultwarden version but when starting it, I get this error, which before never occured: error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory
I have installed openssl and libssl-dev and it always worked, just not with this version.
Other relevant details:
Building and deployment on separate LXCs
Steps to reproduce
Expected behaviour
Actual behaviour
Troubleshooting data
Originally created by @Tropaion on GitHub (Sep 1, 2023).
<!--
# ###
NOTE: Please update to the latest version of vaultwarden before reporting an issue!
This saves you and us a lot of time and troubleshooting.
See:
* https://github.com/dani-garcia/vaultwarden/issues/1180
* https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image
# ###
-->
<!--
Please fill out the following template to make solving your problem easier and faster for us.
This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them.
Remember to hide/redact personal or confidential information,
such as passwords, IP addresses, and DNS names as appropriate.
-->
### Subject of the issue
<!-- Describe your issue here. -->
Hello,
I'm just updated to the latest vaultwarden version but when starting it, I get this error, which before never occured:
```error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directory```
I have installed openssl and libssl-dev and it always worked, just not with this version.
### Deployment environment
Debian 11 LXC on Proxmox
<!--
=========================================================================================
Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab.
That will auto-generate most of the info requested in this section.
=========================================================================================
-->
<!-- The version number, obtained from the logs (at startup) or the admin diagnostics page -->
<!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden -->
<!-- Remember to check if your issue exists on the latest version first! -->
* vaultwarden version: 1.29.2
<!-- How the server was installed: Docker image, OS package, built from source, etc. -->
* Install method: built from source: https://wiki.flowerhouse.at/index.php/BitWarden#Building
* Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) -->
Web Vaul + Android + Desktop
* Reverse proxy and version: <!-- if applicable -->
Caddy
* MySQL/MariaDB or PostgreSQL version: <!-- if applicable -->
MySQL
* Other relevant details:
Building and deployment on separate LXCs
### Steps to reproduce
<!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults)
and how did you start vaultwarden? -->
### Expected behaviour
<!-- Tell us what you expected to happen -->
### Actual behaviour
<!-- Tell us what actually happened -->
### Troubleshooting data
<!-- Share any log files, screenshots, or other relevant troubleshooting data -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Tropaion on GitHub (Sep 1, 2023).
Subject of the issue
Hello,
I'm just updated to the latest vaultwarden version but when starting it, I get this error, which before never occured:
error while loading shared libraries: libssl.so.3: cannot open shared object file: No such file or directoryI have installed openssl and libssl-dev and it always worked, just not with this version.
Deployment environment
Debian 11 LXC on Proxmox
Install method: built from source: https://wiki.flowerhouse.at/index.php/BitWarden#Building
Clients used:
Web Vaul + Android + Desktop
Reverse proxy and version:
Caddy
MySQL/MariaDB or PostgreSQL version:
MySQL
Other relevant details:
Building and deployment on separate LXCs
Steps to reproduce
Expected behaviour
Actual behaviour
Troubleshooting data