bitwarden.sh update - 2024.2.2 - Value cannot be null about self-host HOT 8 OPEN

I received the same error after upgrading to 2024.2.1 however the mssql container appeared to start without issue. I was also having issues with my nginx container starting that seems to be intermittent it was complaining about an entry in default.conf.

from self-host.

Experiencing the same issue @git-tec

from self-host.

Hi there,

This has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

from self-host.

Just noticed the same error. When I login to the admin portal it says I'm on an old version of both the server and the web:

If I try the update process again it says "Update not needed".

Problem is that my organisation licence has expired, but I can't apply the new licence as it says "Version 14 is not supported"

from self-host.

Ok - ignore my earlier post about the version being old. I have two instances and was looking at the wrong one. Doh!

However, after updating the in-use instance and then attempting to disable the old instance in Docker I came across what might be the source of the "Value cannot be Null" error. If you look at the docker settings for the bitwarden-admin container the globalSettings__syslog__destination field appears to be empty and it requires a value. This is preventing me making changes to the container - e.g. to make sure it stays shutdown!

Hope this helps!

from self-host.

Check your diskspace? The upgrade command can leave a lot of debris, especially if an update failed. And "/var/lib/docker/" can wind up overwhelmed by other content in the "/var/" partition, especially "/var/log/" if you've not left enough space in the relevant partition. auditd, in particular, tends to spew logs with docker running.

from self-host.