Comments (40)
I tried commenting out compose_version
in bwdata/config.yaml
file and it worked.
Also after update finished this property is gone from config so this should be only one-time workaround.
from server.
Ok, workaround is to switch back to version 2024.4.1:
- Stop bitwarden
./bitwarden.sh stop
- Then change the version to 2024.4.1. Patch:
--- bitwarden.sh_old 2024-05-07 00:45:13.804462923 +0200
+++ bitwarden.sh 2024-05-07 00:44:22.369781760 +0200
@@ -62,8 +62,8 @@
RUN_SCRIPT_URL="https://func.bitwarden.com/api/dl/?app=self-host&platform=linux&variant=run"
# Please do not create pull requests modifying the version numbers.
-COREVERSION="2024.4.2"
-WEBVERSION="2024.4.2"
+COREVERSION="2024.4.1"
+WEBVERSION="2024.4.1"
KEYCONNECTORVERSION="2024.4.0"
echo "bitwarden.sh version $COREVERSION"
- Start bitwarden again
./bitwarden.sh start
from server.
Thank you for reporting this issue. We have addressed the problem, and you can run ./bitwarden.sh update
and it will grab the latest setup
image and complete successfully.
Please feel free to re-open if you continue to have issues.
from server.
Hi there,
Thank you for your report!
I was able to reproduce this issue, and I have flagged this to our engineering team.
If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.
Thanks once again!
from server.
Ok, workaround is to switch back to version 2024.4.1:
1. Stop bitwarden `./bitwarden.sh stop` 2. Then change the version to 2024.4.1. Patch:
--- bitwarden.sh_old 2024-05-07 00:45:13.804462923 +0200 +++ bitwarden.sh 2024-05-07 00:44:22.369781760 +0200 @@ -62,8 +62,8 @@ RUN_SCRIPT_URL="https://func.bitwarden.com/api/dl/?app=self-host&platform=linux&variant=run" # Please do not create pull requests modifying the version numbers. -COREVERSION="2024.4.2" -WEBVERSION="2024.4.2" +COREVERSION="2024.4.1" +WEBVERSION="2024.4.1" KEYCONNECTORVERSION="2024.4.0" echo "bitwarden.sh version $COREVERSION"
3. Start bitwarden again `./bitwarden.sh start`
I confirm that a rollback this way worked fine.
Thank you!
from server.
I'm having this issue when upgrading. I tried to upgrade the docker but that didn't make any difference. I have reverted the script back to 2024.4.1 temporarily for now. Hope this problem will be fixed soon.
from server.
They just removed a prop from whatever class it was serializing config.yaml into. Can not find property and runtime just blows up. No secret there. Probably just someone forgot to test on previous version of the config. Or just a mistake - shit happens.
Anyway if this work it works. Yeah should be fixed but you know... one problem less out of your head :)
Yup, this seems to be the culprit https://github.com/bitwarden/server/pull/3972/files
Obviously there is a regression testing issue though, this should never have been allowed to be rolled out to customers
from server.
Same here, upgrading to latest docker-compose (2.27.0) and docker-ce (26.1.1) did the trick :
For Ubuntu / debian :
# Check the current version of Docker Compose
docker-compose version
# Backup
cp /usr/local/bin/docker-compose /usr/local/bin/docker-compose.bck
# Download the latest version of Docker Compose
sudo curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
# Apply executable permissions to the binary
sudo chmod +x /usr/local/bin/docker-compose
# Verify the installation
docker-compose version
from server.
You can replace bitwarden.sh with the one from 2024.4.1 release
from server.
For me the "workaround" was to simply start manually the containers... I still have the errors but Bitwarden is running.
sudo -u bitwarden /srv/bitwarden/bitwarden.sh start
from server.
I tried commenting out
compose_version
inbwdata/config.yaml
file and it worked. Also after update finished this property is gone from config so this should be only one-time workaround.
@npodbielski seems that you found the bug!
Tested this method successfully and the complete upgrade went through!
from server.
Same here. Looks like it's enough to add
version: '3'
at the start of the bwdata/docker/docker-compose.yml
file as a workaround.
from server.
same problem here. Any progress on creating a workaround? Or is there a way to do a fallback?
from server.
For me the "workaround" was to simply start manually the containers... I still have the errors but Bitwarden is running.
sudo -u bitwarden /srv/bitwarden/bitwarden.sh startI've tried that also, didn't help :(
What error do you get?
from server.
For me the "workaround" was to simply start manually the containers... I still have the errors but Bitwarden is running.
sudo -u bitwarden /srv/bitwarden/bitwarden.sh startI've tried that also, didn't help :(
What error do you get?
The same as in the OP IIRC. Already did a rollback to the previous version, so can't retry it.
You can retry after running the following:
./bitwarden.sh updateself
This will gather again the new version of the bitwarden.sh script with the faulty versions.
from server.
Nope
ERROR: The Compose file '/opt/bitwarden/bwdata/docker/docker-compose.yml' is invalid because: Unsupported config option for services: 'api' 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: 'attachments' Unsupported config option for networks: 'default' root@vault:/opt/bitwarden#
Rebuild with a new snapshot again...
I had the same issue with docker-compose version 1.25.1. I fixed it by updating to Docker Compose version v2.27.0 (https://docs.docker.com/compose/install/standalone/)
i did a VM Clone and this worked for me too, now im gonna do that on the Productive VM later today my docker-compose versionw as 1.26 despite the ubuntu package manage saying 1.29.0
from server.
Having the same problem here and the suggested workarounds haven't worked.
A couple days ago, an update failed with the error:
Unhandled exception. YamlDotNet.Core.YamlException: (Line: 6, Col: 1, Idx: 193) - (Line: 6, Col: 1, Idx: 193): Exception during deserialization
I've tried the manual bitwarden.sh
patch, but it fails (note that it fails with all the stop/update/start commands with the same kind of error):
bitwarden@zf:~$ ./bitwarden.sh update
_ _ _ _
| |__ (_) |___ ____ _ _ __ __| | ___ _ __
| '_ \| | __\ \ /\ / / _` | '__/ _` |/ _ \ '_ \
| |_) | | |_ \ V V / (_| | | | (_| | __/ | | |
|_.__/|_|\__| \_/\_/ \__,_|_| \__,_|\___|_| |_|
Open source password management solutions
Copyright 2015-2024, 8bit Solutions LLC
https://bitwarden.com, https://github.com/bitwarden
===================================================
bitwarden.sh version 2024.4.1
Docker version 24.0.2, build cb74dfc
docker-compose version 1.26.2, build eefe0d31
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'
bitwarden@zf:~$
Adding version: '3'
to bwdata/docker/docker-compose.yml
also did not work.
Any idea what else I can try to get around this issue?
from server.
Upgrade Docker?
This is my version data:
bitwarden.sh version 2024.4.2
Docker version 26.1.1, build 4cf5afa
Docker Compose version v2.27.0
from server.
Success
with following minor changes
- installing docker-compose with the curl method above or via link above (https://docs.docker.com/compose/install/standalone/) and set the x bit, remove other distribution docker-composes (1.25.0-1, 1.27.x, 1.29.x) or make sure bitwarden.sh find the 2.27 in path
- comment out the
compose_version
inbwdata/config.yml
- it will be overwritten on next update
Environment
This work on the old 20.04 LTS Ubuntu on a VM.
This is essential because I have to maintain other self hosted instances without snapshot possibility for a rollback.
A update of docker.io (24.0.5) was not neccessary.
Tested on 22.04 LTS Ubuntu too. Same procedure.
Updated from 2024.4.0 -> 2024.5.0.
from server.
I tried commenting out
compose_version
inbwdata/config.yaml
file and it worked. Also after update finished this property is gone from config so this should be only one-time workaround.
Hero! Worked for me too
from server.
I tried commenting out
compose_version
inbwdata/config.yaml
file and it worked. Also after update finished this property is gone from config so this should be only one-time workaround.
+1 worked for me too
from server.
I tried commenting out
compose_version
inbwdata/config.yaml
file and it worked. Also after update finished this property is gone from config so this should be only one-time workaround.
Thank you, worked for me
from server.
I have this on bitwarden.sh version 2024.4.2.
Otherwise works fine. I just can't update it.
from server.
For me the "workaround" was to simply start manually the containers... I still have the errors but Bitwarden is running.
sudo -u bitwarden /srv/bitwarden/bitwarden.sh start
I've tried that also, didn't help :(
from server.
For me the "workaround" was to simply start manually the containers... I still have the errors but Bitwarden is running.
sudo -u bitwarden /srv/bitwarden/bitwarden.sh startI've tried that also, didn't help :(
What error do you get?
The same as in the OP IIRC. Already did a rollback to the previous version, so can't retry it.
from server.
I tried commenting out
compose_version
inbwdata/config.yaml
file and it worked. Also after update finished this property is gone from config so this should be only one-time workaround.
It works for me! Thanks!!
from server.
I tried commenting out
compose_version
inbwdata/config.yaml
file and it worked. Also after update finished this property is gone from config so this should be only one-time workaround.
Works!
from server.
I tried commenting out
compose_version
inbwdata/config.yaml
file and it worked. Also after update finished this property is gone from config so this should be only one-time workaround.
Works!
from server.
I tried commenting out
compose_version
inbwdata/config.yaml
file and it worked. Also after update finished this property is gone from config so this should be only one-time workaround.
Well spotted! I searched the code for compose_version
and nothing came up....well done.
from server.
@tmknight I am not sure where you comment go (did you deleted it?) but:
I suggest this is the workaround and not the solution
I did not stated it is the solution. But a way to just ignore this if anyone had a problem get along with their life. I am sure people here have better things to do :)
Unfortunately, my C# isn't the sharpest (pun) and not finding the exact line that is the culprit.
They just removed a prop from whatever class it was serializing config.yaml into. Can not find property and runtime just blows up. No secret there. Probably just someone forgot to test on previous version of the config. Or just a mistake - shit happens.
Anyway if this work it works. Yeah should be fixed but you know... one problem less out of your head :)
from server.
I had the same issue. Thanks to the community for the quick workaround.
Is this specific to a Linux release or version?
from server.
I had the same issue. Thanks to the community for the quick workaround. Is this specific to a Linux release or version?
Don't think so. But Debian 12 here.
from server.
I tried commenting out
compose_version
inbwdata/config.yaml
file and it worked. Also after update finished this property is gone from config so this should be only one-time workaround.
This worked for me. And totally agree, this should be a one-time workaround.
Regression tests may not have been thorough enough to catch this. Even after the update failed, my containers started up fine and ran without an issue on the current version (2024.4.1)
Testing can be hard 😄 At least it was a minor issue.
from server.
Same issue here after trying to solve new issues with HELO-Rejects from SMTP-Server.
Got different error messages from same call like "unknown option public on network", differs from call to call.
Ending up rebuilding from backup snapshot.
I never lernt from it, tried it again, a simple
./bitwarden.sh updateself
./bitwarden.sh update
to
ERROR: The Compose file '/opt/bitwarden/bwdata/docker/docker-compose.yml' is invalid because:
Unsupported config option for services: 'admin'
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: 'attachments'
Unsupported config option for networks: 'public'
root@vault:/opt/bitwarden#
from server.
I tried commenting out
compose_version
inbwdata/config.yaml
file and it worked. Also after update finished this property is gone from config so this should be only one-time workaround.
Worked for me, too.
Sumthin's happening to quality in Bitwarden. After 18 months of quiet, reliable upgrades and new feature additions...suddenly this week, it's driving me crazy. I sure hope this is only a burp and not a slow descent.
from server.
After update nothing works with the error
ERROR: Version mismatch: file /srv/docker/bitwarden/bwdata/docker/docker-compose.yml specifies version 1 but extension file /srv/docker/bitwarden/bwdata/docker/docker-compose.override.yml uses version 3.0
and when i search for compose_ver in the /bwdata/config.yml nothing is there
from server.
Nope
ERROR: The Compose file '/opt/bitwarden/bwdata/docker/docker-compose.yml' is invalid because:
Unsupported config option for services: 'api'
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: 'attachments'
Unsupported config option for networks: 'default'
root@vault:/opt/bitwarden#
Rebuild with a new snapshot again...
from server.
Nope
ERROR: The Compose file '/opt/bitwarden/bwdata/docker/docker-compose.yml' is invalid because: Unsupported config option for services: 'api' 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: 'attachments' Unsupported config option for networks: 'default' root@vault:/opt/bitwarden#
Rebuild with a new snapshot again...
I had the same issue with docker-compose version 1.25.1.
I fixed it by updating to Docker Compose version v2.27.0 (https://docs.docker.com/compose/install/standalone/)
from server.
Upgrading docker-compose did the trick (after resolving some docker login issues that resulted from the upgrade). All set now, it seems. Thanks!
from server.
None of the solutions here were suitable for me - my docker-compose.yml needs the version: "3" line and I don't want to use the curl solution to update docker-compose.
My workaround is to run bitwarden.sh update, observe the error message, add version: "3" to docker-compose.override.yml. The version line should be the same in both docker-compose.override.yml and docker-compose.yml.
Then run bitwarden.sh start
from server.
Related Issues (20)
- Vault domains don't support IPv6 HOT 1
- Invited user synced from Bitwarden Directory Connector causes unhandled server error if invitation is accepted following an email change HOT 1
- Update selfhosted instance to v2024.5.0 no such service: admin HOT 1
- Bitwarden 2024.5.0 unable to start - docker-compose.yml is invalid HOT 2
- 500 Unexpected error during login - CorsPolicyService - key not found in the key ring HOT 2
- vault-management-api.json validation error HOT 2
- swagger authentication with oauth2 scope "api.organization" fails HOT 1
- bitwarden/self-host:beta is still broken on Raspberry Pi 4 HOT 1
- Organization view fail: Unknown column 'p.Gateway' in 'field list' HOT 1
- License status corruption HOT 4
- Cannot set up yubikey on self-hosted instance HOT 1
- Error running sso and identity containers HOT 2
- DOC - Server Setup Guide HOT 1
- User's can't log in with SSO suddenly: The absolute expiration value must be in the future. HOT 3
- Unable to login after recover-delete HOT 1
- Still binding on port 80? HOT 1
- Bitwarden admin console not accessible after update to 2024.7.4 HOT 1
- Unable to add Github Passkeys to Bitwarden wallet HOT 2
- User creation on new installation not working
- There are no items to list. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from server.