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

Hello,

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?

You already asked here:

Nginx’ client_max_body_size defaults to 1M so this could be the issue.

I’d suggest you check the logs of Vaultwarden and MySQL. They might contain error messages or warnings that could give you a clue about why the synchronization fails when the number of organizations exceeds 174.

Hello, we checked this today. The default value for us is 200M. Even after changing to client_max_body_size 525M; didn’t bring any change. We got the value of 525M from the proxy examples Proxy examples · dani-garcia/vaultwarden Wiki · GitHub.

Here are the logs

[2023-12-11 12:48:52.735][request][INFO] GET /api/config
[2023-12-11 12:48:52.735][response][INFO] (config) GET /api/config => 200 OK
[2023-12-11 12:48:54.492][request][INFO] GET /api/devices/knowndevice
[2023-12-11 12:48:54.492][response][INFO] (get_known_device) GET /api/devices/knowndevice => 200 OK
[2023-12-11 12:48:55.460][request][INFO] POST /api/organizations
[2023-12-11 12:48:55.462][response][INFO] (create_organization) POST /api/organizations => 200 OK
[2023-12-11 12:48:55.489][request][INFO] POST /identity/connect/token
[2023-12-11 12:48:55.490][response][INFO] (login) POST /identity/connect/token => 200 OK
[2023-12-11 12:48:55.650][rocket::data::data::][ERROR] Failed to read into peek buffer: Custom { kind: Other, error: hyper::Error(Body, Custom { kind: UnexpectedEof, error: IncompleteBody }) }.
[2023-12-11 12:48:55.650][request][INFO] POST /identity/connect/token
[2023-12-11 12:48:55.650][vaultwarden::api::identity::
][WARN] Data guard Form < ConnectData > failed: Errors([Error { name: Some(“grant_type”), value: None, kind: Missing, entity: Field }]).
[2023-12-11 12:48:55.650][response][INFO] (login) POST /identity/connect/token => 422 Unprocessable Entity
[2023-12-11 12:49:01.248][request][INFO] POST /identity/accounts/prelogin
[2023-12-11 12:49:01.248][response][INFO] (prelogin) POST /identity/accounts/prelogin => 200 OK
[2023-12-11 12:49:01.502][request][INFO] POST /identity/connect/token
[2023-12-11 12:49:01.542][vaultwarden::api::identity][INFO] User xxx logged in successfully. IP: x.x.x.x
[2023-12-11 12:49:01.542][response][INFO] (login) POST /identity/connect/token => 200 OK
[2023-12-11 12:49:16.358][vaultwarden::api::notifications][INFO] Closing WS connection from
[2023-12-11 12:49:16.358][rocket::server][ERROR] Upgraded websocket I/O handler failed: WebSocket protocol error: Sending after closing is not allowed
[2023-12-11 12:50:59.771][request][INFO] GET /api/devices/knowndevice
[2023-12-11 12:50:59.771][response][INFO] (get_known_device) GET /api/devices/knowndevice => 200 OK
[2023-12-11 12:51:06.313][request][INFO] POST /identity/accounts/prelogin
[2023-12-11 12:51:06.314][response][INFO] (prelogin) POST /identity/accounts/prelogin => 200 OK
[2023-12-11 12:51:06.541][request][INFO] POST /identity/connect/token
[2023-12-11 12:51:06.581][vaultwarden::api::identity][INFO] User xxxx logged in successfully. IP: x.x.x.x
[2023-12-11 12:51:06.581][response][INFO] (login) POST /identity/connect/token => 200 OK
[2023-12-11 12:51:06.731][request][INFO] POST /identity/connect/token
[2023-12-11 12:51:06.732][response][INFO] (login) POST /identity/connect/token => 200 OK