Latest bw-linux 2024.6.1 isnt compatible with vaultwarden anymore #5606

New Issue

Closed

opened 2026-03-07 20:31:35 -06:00 by GiteaMirror · 4 comments

GiteaMirror commented 2026-03-07 20:31:35 -06:00

Owner

Copy Link

Originally created by @peterge-misoft on GitHub (Jul 9, 2024).

Subject of the issue

We use a CI pipeline that downloads and encrypts a dump of our whole vault. Its running every week. Last week with 2024.6.0 it did work just fine, but this week with 2024.6.1 it says Invalid master password. when executing bw unlock. I did not change the pw of course.

Deployment environment

• vaultwarden version:
  Vaultwarden Web Version 2024.1.2 (vaultwarden/server:latest)

• Install method:
  docker compose

• Clients used:
  bw-linux 2024.6.1
  https://vault.bitwarden.com/download/?app=cli&platform=linux

• Other relevant details:

Steps to reproduce

  script:
    # Install prerequisites
    - apt-get update >/dev/null && apt install unzip sshpass wget -y >/dev/null 
    - wget --no-check-certificate 'https://vault.bitwarden.com/download/?app=cli&platform=linux' -O bw-linux.zip > /dev/null 2>&1
    - unzip bw-linux.zip
    - rm bw-linux.zip
    - chmod +x bw
    # Set timezone to Eurpoe/Berlin for printing date
    - ln -fs /usr/share/zoneinfo/Europe/Berlin /etc/localtime
    - dpkg-reconfigure -f noninteractive tzdata
    # Install certificate
    - echo "$CERTIFICATE" > /root/certificate.pem
    # Set env vars
    - export NODE_EXTRA_CA_CERTS="/root/certificate.pem"
    - export BW_CLIENTID=$BW_CLIENTID
    - export BW_CLIENTSECRET=$BW_CLIENTSECRET
    - export MASTERPASSWORD_EXPORT_USER="$MASTERPASSWORD_EXPORT_USER"
    # Show bw-cli version
    - ./bw -v
    # Configure server
    - ./bw config server https://pass.misoft.local/
    # Login in
    - ./bw login --apikey
    # Export the session key as env var
    - export BW_SESSION=$(./bw unlock --passwordenv MASTERPASSWORD_EXPORT_USER --raw)
    # Export the misoft organization in plaintext
    - ./bw export --organizationid 4ad08680-93e8-400e-a74b-cde5c6e41ce3 --format json --output vaultwarden-misoft-organization-export.json

Expected behaviour

create a dump file, this is the CI output from last week with bw 2024.6.0:

Actual behaviour

this is the CI output with bw 2024.6.1:

Troubleshooting data

see both screenshots

Originally created by @peterge-misoft on GitHub (Jul 9, 2024). <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue We use a CI pipeline that downloads and encrypts a dump of our whole vault. Its running every week. Last week with 2024.6.0 it did work just fine, but this week with 2024.6.1 it says `Invalid master password.` when executing bw unlock. I did not change the pw of course. ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: Vaultwarden Web Version 2024.1.2 (vaultwarden/server:latest) <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: docker compose * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> bw-linux 2024.6.1 https://vault.bitwarden.com/download/?app=cli&platform=linux * Other relevant details: ### Steps to reproduce ``` script: # Install prerequisites - apt-get update >/dev/null && apt install unzip sshpass wget -y >/dev/null - wget --no-check-certificate 'https://vault.bitwarden.com/download/?app=cli&platform=linux' -O bw-linux.zip > /dev/null 2>&1 - unzip bw-linux.zip - rm bw-linux.zip - chmod +x bw # Set timezone to Eurpoe/Berlin for printing date - ln -fs /usr/share/zoneinfo/Europe/Berlin /etc/localtime - dpkg-reconfigure -f noninteractive tzdata # Install certificate - echo "$CERTIFICATE" > /root/certificate.pem # Set env vars - export NODE_EXTRA_CA_CERTS="/root/certificate.pem" - export BW_CLIENTID=$BW_CLIENTID - export BW_CLIENTSECRET=$BW_CLIENTSECRET - export MASTERPASSWORD_EXPORT_USER="$MASTERPASSWORD_EXPORT_USER" # Show bw-cli version - ./bw -v # Configure server - ./bw config server https://pass.misoft.local/ # Login in - ./bw login --apikey # Export the session key as env var - export BW_SESSION=$(./bw unlock --passwordenv MASTERPASSWORD_EXPORT_USER --raw) # Export the misoft organization in plaintext - ./bw export --organizationid 4ad08680-93e8-400e-a74b-cde5c6e41ce3 --format json --output vaultwarden-misoft-organization-export.json ``` ### Expected behaviour create a dump file, this is the CI output from last week with bw 2024.6.0:  ### Actual behaviour this is the CI output with bw 2024.6.1:  ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data --> see both screenshots

GiteaMirror closed this issue 2026-03-07 20:31:36 -06:00

GiteaMirror commented 2026-03-07 20:31:36 -06:00

Author

Owner

Copy Link

@otbutz commented on GitHub (Jul 9, 2024):

Deployment environment

* vaultwarden version:
  Vaultwarden Web Version 2024.1.2 (vaultwarden/server:latest)

Could you update to vaultwarden 1.31.0 ? Your web vault version indicates that you're running vaultwarden 1.30.4

@otbutz commented on GitHub (Jul 9, 2024): > ### Deployment environment > > * vaultwarden version: > Vaultwarden Web Version 2024.1.2 (vaultwarden/server:latest) Could you update to vaultwarden [1.31.0](https://github.com/dani-garcia/vaultwarden/releases/tag/1.31.0) ? Your web vault version indicates that you're running vaultwarden [1.30.4](https://github.com/dani-garcia/vaultwarden/releases/tag/1.30.4)

GiteaMirror commented 2026-03-07 20:31:36 -06:00

Author

Owner

Copy Link

@peterge-misoft commented on GitHub (Jul 9, 2024):

I updated to Vaultwarden Web Version 2024.5.1, which is 1.31.0.
But the error message is still the same:

@peterge-misoft commented on GitHub (Jul 9, 2024): I updated to Vaultwarden Web Version 2024.5.1, which is 1.31.0. But the error message is still the same: 

GiteaMirror commented 2026-03-07 20:31:37 -06:00

Author

Owner

Copy Link

@peterge-misoft commented on GitHub (Jul 9, 2024):

When I change the url to use 2024.6.0 like this in the pipeline, it does work again with 1.31.1. So for me it looks like there is a compatibility issue with vaultwarden.

- wget --no-check-certificate 'https://github.com/bitwarden/clients/releases/download/cli-v2024.6.0/bw-linux-2024.6.0.zip' -O bw-linux.zip > /dev/null 2>&1

@peterge-misoft commented on GitHub (Jul 9, 2024): When I change the url to use 2024.6.0 like this in the pipeline, it does work again with 1.31.1. So for me it looks like there is a compatibility issue with vaultwarden.  `- wget --no-check-certificate 'https://github.com/bitwarden/clients/releases/download/cli-v2024.6.0/bw-linux-2024.6.0.zip' -O bw-linux.zip > /dev/null 2>&1`

GiteaMirror commented 2026-03-07 20:31:37 -06:00

Author

Owner

Copy Link

@BlackDex commented on GitHub (Jul 9, 2024):

I just tested it and it and it works fine for me.
I used the exact same arguments (with different org-id of course) and that just outputs the correct json for me.

It only fails if i use the apikey login, then it asks me for the master-password which always reports an invalid master-password.

To note, the sync goes well, after that all is up-to the clients, and nothing is done server-side anymore, for which this is a client issue. I checked the Bitwarden client repo, and found this issue: https://github.com/bitwarden/clients/issues/9919

Going to close this here, as this isn't something we can fix, and Bitwarden already is working on a fix, and it should be resolved in the next cli release.

@BlackDex commented on GitHub (Jul 9, 2024): I just tested it and it and it works fine for me. I used the exact same arguments (with different org-id of course) and that just outputs the correct json for me. It only fails if i use the apikey login, then it asks me for the master-password which always reports an invalid master-password. To note, the sync goes well, after that all is up-to the clients, and nothing is done server-side anymore, for which this is a client issue. I checked the Bitwarden client repo, and found this issue: https://github.com/bitwarden/clients/issues/9919 Going to close this here, as this isn't something we can fix, and Bitwarden already is working on a fix, and it should be resolved in the next cli release.

GiteaMirror referenced this issue 2026-04-20 14:33:51 -05:00

[GH-ISSUE #5606] Web-vault no longer uses .png logos/branding. #11013

GiteaMirror referenced this issue 2026-04-23 06:49:22 -05:00

[GH-ISSUE #5606] Web-vault no longer uses .png logos/branding. #14990

GiteaMirror referenced this issue 2026-04-25 21:20:41 -05:00

[GH-ISSUE #5606] Web-vault no longer uses .png logos/branding. #18974

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

revert-7033-patch-1

cached-config-operations

test_dylint

1.36.0

1.35.8

1.35.7

1.35.6

1.35.5

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

better for forum

bug

documentation

duplicate

enhancement

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

SSO

Third party

troubleshooting

wontfix

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

GiteaMirror ninjasurge

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#5606