Unexpected error when logging into server

Running on Proxmox and did the latest pull from Docker and every client receives "unepxected error" when logging though web. Clients fail on error when logging in from mobile device and the chrome plugin. I started the docker container to view the output and there is a repeating aborted connection message which I was also seeing in the December builds but no additional items that lead to why the error is happening. I rolled back to December and client login is working again. Let me know what addition info you need.

The old version I migrated from was: Version 2023.12.0
The version from docker hub latest "beta" tag

```
bitwarden-bitwarden-1 | 2024-01-31 15:58:12,690 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
bitwarden-db-1 | 2024-01-31 15:58:20 64 [Warning] Aborted connection 64 to db: 'unconnected' user: 'bitwarden' host: '172.18.0.3' (Got an error reading communication packets)
bitwarden-db-1 | 2024-01-31 15:58:20 66 [Warning] Aborted connection 66 to db: 'bitwarden_vault' user: 'bitwarden' host: '172.18.0.3' (Got an error reading communication packets)
bitwarden-bitwarden-1 | 2024-01-31 15:58:21,408 INFO exited: admin (terminated by SIGABRT (core dumped); not expected)
bitwarden-bitwarden-1 | 2024-01-31 15:58:22,410 INFO spawned: 'admin' with pid 572
bitwarden-bitwarden-1 | 2024-01-31 15:58:37,429 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
bitwarden-db-1 | 2024-01-31 15:58:45 70 [Warning] Aborted connection 70 to db: 'bitwarden_vault' user: 'bitwarden' host: '172.18.0.3' (Got an error reading communication packets)
bitwarden-db-1 | 2024-01-31 15:58:45 68 [Warning] Aborted connection 68 to db: 'unconnected' user: 'bitwarden' host: '172.18.0.3' (Got an error reading communication packets)
bitwarden-bitwarden-1 | 2024-01-31 15:58:46,312 INFO exited: admin (terminated by SIGABRT (core dumped); not expected)
bitwarden-bitwarden-1 | 2024-01-31 15:58:47,315 INFO spawned: 'admin' with pid 594
bitwarden-bitwarden-1 | 2024-01-31 15:59:02,333 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
bitwarden-db-1 | 2024-01-31 15:59:10 72 [Warning] Aborted connection 72 to db: 'unconnected' user: 'bitwarden' host: '172.18.0.3' (Got an error reading communication packets)
bitwarden-db-1 | 2024-01-31 15:59:10 74 [Warning] Aborted connection 74 to db: 'bitwarden_vault' user: 'bitwarden' host: '172.18.0.3' (Got an error reading communication packets
```

Start by reproducing the login failure with the beta Docker deployment on the reported setup, then inspect the repeating aborted database connections and the admin process SIGABRT messages in the container logs. Done means web, mobile, and Chrome-plugin clients can log in on the current version without the recurring admin crashes.

Written by the indexing model from the issue text.