Vaultwarden 1.30.5 with Bitwarden Client 2024.3.0 - Client does not allow saving new entries due to collections not being available. #1177

Closed
opened 2026-04-06 01:41:23 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @monteroman on 4/4/2024

Subject of the issue

Vaultwarden 1.30.5 running with the Bitwarden client 2024.3.0 - issue with client not allowing to save entries inside an Enterprise collection.

Deployment environment

  • vaultwarden version: 1.30.5
  • Install method: Docker

  • Clients used: Desktop, Edge Plugin, Web

  • Reverse proxy and version: n/a

  • MySQL/MariaDB or PostgreSQL version: MariaDB 10.6.16

  • Other relevant details: This only happens with the Windows Client.

Steps to reproduce

Using the Windows client, I go to a collection. Click + to add a new entry. Fill out the fields. Under Ownership, i see the ownership, but under Collections, I get "There are no collections to list".

Expected behaviour

Show the collections and allow selection of collections.

Actual behaviour

No collections are showing up.

Troubleshooting data

image

The issue does not occur in the web client.
I restarted the Vaultwarden docker and the issue still occurs.
There are no database errors being reported in the docker log.
I have logged out and logged back into the Windows client.
This happens on both enterprise collections.

*Originally created by @monteroman on 4/4/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 Vaultwarden 1.30.5 running with the Bitwarden client 2024.3.0 - issue with client not allowing to save entries inside an Enterprise collection. ### 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: 1.30.5 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Docker * Clients used: Desktop, Edge Plugin, Web * Reverse proxy and version: <!-- if applicable --> n/a * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> MariaDB 10.6.16 * Other relevant details: This only happens with the Windows Client. ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> Using the Windows client, I go to a collection. Click + to add a new entry. Fill out the fields. Under Ownership, i see the ownership, but under Collections, I get "There are no collections to list". ### Expected behaviour <!-- Tell us what you expected to happen --> Show the collections and allow selection of collections. ### Actual behaviour <!-- Tell us what actually happened --> No collections are showing up. ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data --> ![image](https://github.com/dani-garcia/vaultwarden/assets/5451042/4f706aea-702e-4b2d-8ec1-7e59192bd3b0) The issue does not occur in the web client. I restarted the Vaultwarden docker and the issue still occurs. There are no database errors being reported in the docker log. I have logged out and logged back into the Windows client. This happens on both enterprise collections.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/vaultwarden#1177