Bitwarden self host cannot start

Greetings everyone,
I received alarms today from my monitoring system that my bitwarden self-hosted instance is not running. When i log in i do see all bitwarden containers are no longer running. When I attempt to run i receive the below error.
This is a low-maintenance system where auto-updates occur on the Bitwarden application per documentation. There has been no changes to the environment.

Operating System: Ubuntu 22.04.4 LTS

bitwarden.sh version 2024.4.2
Docker version 24.0.5, build 24.0.5-0ubuntu1~22.04.1
docker-compose version 1.29.2, build unknown

"docker inspect" requires at least 1 argument.
See 'docker inspect --help'.

Usage:  docker inspect [OPTIONS] NAME|ID [NAME|ID...]

Return low-level information on Docker objects
2024.4.2: Pulling from bitwarden/setup
Digest: sha256:449b99f14e9ec83f70a264dd76a61bee35e53f576361d860e6ba8dc4da367f02
Status: Image is up to date for bitwarden/setup:2024.4.2
docker.io/bitwarden/setup:2024.4.2

Unhandled exception. YamlDotNet.Core.YamlException: (Line: 6, Col: 1, Idx: 193) - (Line: 6, Col: 1, Idx: 193): Exception during deserialization
 ---> System.Runtime.Serialization.SerializationException: Property 'compose_version' not found on type 'Bit.Setup.Configuration'.
   at YamlDotNet.Serialization.TypeInspectors.TypeInspectorSkeleton.GetProperty(Type type, Object container, String name, Boolean ignoreUnmatched)
   at YamlDotNet.Serialization.NodeDeserializers.ObjectNodeDeserializer.YamlDotNet.Serialization.INodeDeserializer.Deserialize(IParser parser, Type expectedType, Func`3 nestedObjectDeserializer, Object& value)
   at YamlDotNet.Serialization.ValueDeserializers.NodeValueDeserializer.DeserializeValue(IParser parser, Type expectedType, SerializerState state, IValueDeserializer nestedObjectDeserializer)
   --- End of inner exception stack trace ---
   at YamlDotNet.Serialization.ValueDeserializers.NodeValueDeserializer.DeserializeValue(IParser parser, Type expectedType, SerializerState state, IValueDeserializer nestedObjectDeserializer)
   at YamlDotNet.Serialization.ValueDeserializers.AliasValueDeserializer.DeserializeValue(IParser parser, Type expectedType, SerializerState state, IValueDeserializer nestedObjectDeserializer)
   at YamlDotNet.Serialization.Deserializer.Deserialize(IParser parser, Type type)
   at YamlDotNet.Serialization.Deserializer.Deserialize[T](IParser parser)
   at YamlDotNet.Serialization.Deserializer.Deserialize[T](TextReader input)
   at YamlDotNet.Serialization.Deserializer.Deserialize[T](String input)
   at Bit.Setup.Context.LoadConfiguration() in /home/runner/work/server/server/util/Setup/Context.cs:line 154
   at Bit.Setup.Program.RebuildConfigs() in /home/runner/work/server/server/util/Setup/Program.cs:line 315
   at Bit.Setup.Program.Update() in /home/runner/work/server/server/util/Setup/Program.cs:line 163
   at Bit.Setup.Program.Main(String[] args) in /home/runner/work/server/server/util/Setup/Program.cs:line 57
pathconf: Permission denied
--2024-05-07 07:16:56--  https://hc-ping.com/74bfd37a-1d40-41c6-91d6-48a7ecbdaa63
Resolving hc-ping.com (hc-ping.com)... 159.69.66.229, 178.63.26.145, 188.40.122.95, ...
Connecting to hc-ping.com (hc-ping.com)|159.69.66.229|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2 [text/plain]
74bfd37a-1d40-41c6-91d6-48a7ecbdaa63: Permission denied

Cannot write to ‘74bfd37a-1d40-41c6-91d6-48a7ecbdaa63’ (Success).

The issue is already known and seems to be somewhere near the update process :

I just tried to update our on-prem and got the same error. Our Bitwarden server is dead and cannot restart, this is an urgent matter as our entire company vault is not accessible.

 _     _ _                         _            
| |__ (_) |___      ____ _ _ __ __| | ___ _ __  
| '_ \| | __\ \ /\ / / _` | '__/ _` |/ _ \ '_ \ 
| |_) | | |_ \ V  V / (_| | | | (_| |  __/ | | |
|_.__/|_|\__| \_/\_/ \__,_|_|  \__,_|\___|_| |_|

Open source password management solutions
Copyright 2015-2024, 8bit Solutions LLC
https://bitwarden.com, https://github.com/bitwarden

===================================================

bitwarden.sh version 2024.5.0
Docker version 26.1.3, build b72abbb
docker-compose version 1.29.2, build 5becea4c

"docker inspect" requires at least 1 argument.
See 'docker inspect --help'.

Usage:  docker inspect [OPTIONS] NAME|ID [NAME|ID...]

Return low-level information on Docker objects
2024.5.0: Pulling from bitwarden/setup
Digest: sha256:79bc6c1916d885194cc0fc501f0e92c46bdc78d7a84f72b73ea1e4febe9a730e
Status: Image is up to date for bitwarden/setup:2024.5.0
docker.io/bitwarden/setup:2024.5.0

Unhandled exception. YamlDotNet.Core.YamlException: (Line: 6, Col: 1, Idx: 193) - (Line: 6, Col: 1, Idx: 193): Exception during deserialization
 ---> System.Runtime.Serialization.SerializationException: Property 'compose_version' not found on type 'Bit.Setup.Configuration'.
   at YamlDotNet.Serialization.TypeInspectors.TypeInspectorSkeleton.GetProperty(Type type, Object container, String name, Boolean ignoreUnmatched)
   at YamlDotNet.Serialization.NodeDeserializers.ObjectNodeDeserializer.YamlDotNet.Serialization.INodeDeserializer.Deserialize(IParser parser, Type expectedType, Func`3 nestedObjectDeserializer, Object& value)
   at YamlDotNet.Serialization.ValueDeserializers.NodeValueDeserializer.DeserializeValue(IParser parser, Type expectedType, SerializerState state, IValueDeserializer nestedObjectDeserializer)
   --- End of inner exception stack trace ---
   at YamlDotNet.Serialization.ValueDeserializers.NodeValueDeserializer.DeserializeValue(IParser parser, Type expectedType, SerializerState state, IValueDeserializer nestedObjectDeserializer)
   at YamlDotNet.Serialization.ValueDeserializers.AliasValueDeserializer.DeserializeValue(IParser parser, Type expectedType, SerializerState state, IValueDeserializer nestedObjectDeserializer)
   at YamlDotNet.Serialization.Deserializer.Deserialize(IParser parser, Type type)
   at YamlDotNet.Serialization.Deserializer.Deserialize[T](IParser parser)
   at YamlDotNet.Serialization.Deserializer.Deserialize[T](TextReader input)
   at YamlDotNet.Serialization.Deserializer.Deserialize[T](String input)
   at Bit.Setup.Context.LoadConfiguration() in /home/runner/work/server/server/util/Setup/Context.cs:line 154
   at Bit.Setup.Program.RebuildConfigs() in /home/runner/work/server/server/util/Setup/Program.cs:line 315
   at Bit.Setup.Program.Update() in /home/runner/work/server/server/util/Setup/Program.cs:line 163
   at Bit.Setup.Program.Main(String[] args) in /home/runner/work/server/server/util/Setup/Program.cs:line 57

1 Like

Same problem here.

bitwarden.sh version 2024.5.0
Docker version 26.1.3, build b72abbb
Docker Compose version v2.27.0

And WE HAVE O ACCESS TO OUR PASSWORDS = to many systems an websites. :slightly_frowning_face::slightly_frowning_face::slightly_frowning_face:

I’m also unable to start Bitwarden. My error is:

bitwarden.sh version 2024.5.0
Docker version 26.1.3, build b72abbb
docker-compose version 1.25.3, build d4d1b42b

ERROR: The Compose file '/opt/bitwarden/bwdata/docker/docker-compose.yml' is invalid because:
Unsupported config option for networks: 'public'
Unsupported config option for services: 'web'
ERROR: The Compose file '/opt/bitwarden/bwdata/docker/docker-compose.yml' is invalid because:
Unsupported config option for services: 'mssql'
Unsupported config option for networks: 'public'

Are there any fixes?
Thanks.

Ok, I’ve just removed my bitwarden install, I removed docker, following the instructions on Docker website and did a clean install, without importing my data. I am getting a very similar error. It seems the latest bitwarden update is broken. How can we roll back to a previous version?

Error message:

bitwarden.sh version 2024.5.0
Docker version 26.1.3, build b72abbb
docker-compose version 1.25.3, build d4d1b42b

ERROR: The Compose file '/opt/bitwarden/bwdata/docker/docker-compose.yml' is invalid because:
Unsupported config option for services: 'notifications'
Unsupported config option for networks: 'public'
ERROR: The Compose file '/opt/bitwarden/bwdata/docker/docker-compose.yml' is invalid because:
Unsupported config option for services: 'icons'
Unsupported config option for networks: 'public'