starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-02-05 00:29:40 +03:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

Cannot create more than 10 collections after updating to 1.31.0 #1993

New Issue
Closed
opened 2026-02-05 02:28:51 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 02:28:51 +03:00
Owner
Copy Link

Originally created by @senpro-ziegerl on GitHub (Aug 13, 2024).

Subject of the issue

After updating to Vaultwarden 1.31.0, we are no longer able to create more than 10 collections for an organization

Deployment environment

  • vaultwarden version: 1.31.0

  • Install method: Kubernetes (K3S) container with the GitHub image, NixOS as the underlying OS

  • Clients used: Web Vault

  • Reverse proxy and version: Traefik

  • MySQL/MariaDB or PostgreSQL version: PostgreSQL 15

  • Other relevant details: -

Steps to reproduce

Expected behaviour

To be able to create more than 10 collections per organization, as it previously worked

Actual behaviour

Received a popup that free organizations can only have up to 10 collections and that the plan needs to be upgraded

Troubleshooting data

image

Originally created by @senpro-ziegerl on GitHub (Aug 13, 2024). ### Subject of the issue After updating to Vaultwarden 1.31.0, we are no longer able to create more than 10 collections for an organization ### 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.31.0 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: Kubernetes (K3S) container with the GitHub image, NixOS as the underlying OS * Clients used: Web Vault * Reverse proxy and version: Traefik * MySQL/MariaDB or PostgreSQL version: PostgreSQL 15 * 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? --> ### Expected behaviour To be able to create more than 10 collections per organization, as it previously worked ### Actual behaviour Received a popup that free organizations can only have up to 10 collections and that the plan needs to be upgraded ### Troubleshooting data ![image](https://github.com/user-attachments/assets/65676917-e4fb-4599-806d-1f6372cb4bdc)
OVERLORD commented 2026-02-05 02:29:01 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Aug 13, 2024):

Already resolved in 1.32.0

@BlackDex commented on GitHub (Aug 13, 2024): Already resolved in 1.32.0
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
troubleshooting
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1993
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?