If there are more than 174 organizations per user, the synchronization no longer works. Limit 174 organizations per user? #1318

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

Originally created by @mhmario on 12/11/2023

Subject of the issue

Currently I have the following problem: A user has 174 organizations. If this user has created another organization, synchronization will no longer work. All 175 organizations no longer appear in the web browser. When I try to synchronize in the Bitwarden APP, the error message appears: “Failed to synchronize”.

If I delete an organization using the admin token, everything works again without any problems.

Vaultwarden runs in a Docker container within ProxMox on the current version 2023.10.0 with the MySQL DB. In the OPNsense it is configured with Nginx.

Do you have a solution for the problem?

Deployment environment

2023.10.0

2023.10.0

  • vaultwarden version: 2023.10.0
  • Install method: Docker image

  • Clients used:

  • Google Chrome

  • Firefox

  • Windows-App

  • iOS APP

  • Reverse proxy and version:

  • Nginx on OPNsnese

  • MySQL/MariaDB or PostgreSQL version:

  • MySQL

  • Other relevant details:

Steps to reproduce

Everything is set to default. If you create the 175 organization for a user, the error occurs.

Expected behaviour

Actual behaviour

Troubleshooting data

*Originally created by @mhmario on 12/11/2023* <!-- # ### 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 Currently I have the following problem: A user has 174 organizations. If this user has created another organization, synchronization will no longer work. All 175 organizations no longer appear in the web browser. When I try to synchronize in the Bitwarden APP, the error message appears: “Failed to synchronize”. If I delete an organization using the admin token, everything works again without any problems. Vaultwarden runs in a Docker container within ProxMox on the current version 2023.10.0 with the MySQL DB. In the OPNsense it is configured with Nginx. Do you have a solution for the problem? ### 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 --> 2023.10.0 <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> 2023.10.0 <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: 2023.10.0 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Docker image * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> * Google Chrome * Firefox * Windows-App * iOS APP * Reverse proxy and version: <!-- if applicable --> * Nginx on OPNsnese * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> * MySQL * Other relevant details: ### 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? --> Everything is set to default. If you create the 175 organization for a user, the error occurs. ### Expected behaviour <!-- Tell us what you expected to happen --> ### Actual behaviour <!-- Tell us what actually happened --> ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/vaultwarden#1318