bitwarden / server

Bitwarden infrastructure/backend (API, database, Docker, etc).
https://bitwarden.com
Other
15.46k stars 1.3k forks source link

Bitwarden Unified fails to start: identity terminated by SIGABRT #3951

Open ianalexander opened 6 months ago

ianalexander commented 6 months ago

Steps To Reproduce

  1. Start bitwarden unified with the following docker compose configuration:
    
    version: "3.8"

services: bitwarden: image: bitwarden/self-host:beta container_name: bitwarden restart: unless-stopped ports:

Expected Result

Container starts successfully and allows registration.

Actual Result

identity service crashes, which prevents registration

Screenshots or Videos

No response

Additional Context

No response

Githash Version

e7658192-dirty

Environment Details

Docker running on x86_64 system

Database Image

Sqlite

Issue-Link

https://github.com/bitwarden/server/issues/2480

Issue Tracking Info

ianalexander commented 6 months ago

I can help debug, but any pointers to collect more information about the Unhandled exception. Interop+Crypto+OpenSslCryptographicException: error:10080002:BIO routines::system lib exception would be very helpful. Thak you!

sammbw commented 6 months ago

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

xaocon commented 5 months ago

@ianalexander, I'm not from bitwarden and I'm not familiar with the codebase so take anything I say with a grain of salt. Despite that, I'm looking at trying out hosted as well and was curious about this issue.

Unhandled exception. Interop+Crypto+OpenSslCryptographicException: error:10080002:BIO routines::system lib isn't very helpful but it's basically handing back an unhelpful error message from OpenSSL. error:10080002:BIO routines::system lib should allow you to trace down the specific problem from OpenSSL but I wasn't able to find more info about it.

Further down in your trace we see that you're running down the code path here, which is trying to get a certificate from the file identity.pfx with a stored password.

I suspect there might be a problem with the identity.pfx. Maybe a permissions issue reading from it or some kind of corruption. No hard evidence with the info provided but might help you tracking more info down.