mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Problem creating more than 79 Organizations #865
Reference in New Issue
Block a user
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?
Originally created by @fablav on GitHub (Nov 20, 2020).
Subject of the issue
User crash after creating the 79th Organization
Your environment
Bitwarden_rs server in Docker on a Nas Synology
2.16.1
Steps to reproduce
After creating an account, i try to create the Organizations.
Everything is okay until creating the 79th Organization.
After creating that, the Account loose all the Organizations created.
In the Admin Panel I can see them but in the Portal there is nothing.
My account is locked and I can't create new Organization.
Expected behaviour
Actual behaviour
Relevant logs
@BlackDex commented on GitHub (Nov 20, 2020):
Hello @fablav, to be blunt, why do you need 79+ Organizations?
That seems to be a lot, and not very manageable.
Also, what are the error's you get either in the bitwarden.log or the browser developer console?
@fablav commented on GitHub (Nov 20, 2020):
Hello @BlackDex
We are a company that has to manage the paswords of our customers (over 150).
we would like to enter their organisation and invite them for a read only access.
I don't have the log because I've deleted the Docker Container.
I can reproduce the error reinserting the Organizations, but I don't know where find the log.
I have poor knowledge about Docker and Bitwarden.
@BlackDex commented on GitHub (Nov 20, 2020):
Well that is unfortunate. Without that i can't help to troubleshoot this issue.
I just tried creating 100 organizations, and that works fine for me.
If you try it again, please save the log output and browser errors you may see in the developer console (F12) of the browser.
@BlackDex commented on GitHub (Nov 22, 2020):
Closing this ticket because it's not reproducible and it seems the original logs are going as stated by the reporter.
If someone has this issue also, and has logs, please re-open.