mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #6671] Unable to create organizations #2504
Labels
No 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
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#2504
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @Jurgen-DOUCHY on GitHub (Jan 6, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6671
Prerequisites
Vaultwarden Support String
I keep getting the error: Cannot read properties of undefined (reading 'find')
Users email addres is set in ORG_CREATION_USERS.
Any Ideas?
Screenshots or Videos
No response
Additional Context
No response
@woprandi commented on GitHub (Jan 6, 2026):
It's fixed with the
testingimage taghttps://github.com/dani-garcia/vaultwarden/issues/6638
https://github.com/dani-garcia/bw_web_builds/pull/224
@BlackDex commented on GitHub (Jan 6, 2026):
You didn't searched closed issues, there are many already
@Jurgen-DOUCHY commented on GitHub (Jan 6, 2026):
ok my bad, did a quick search and forgot to remove the 'open' tag. :)
On the other hand, It's a bit weird to mark an issieu as closed/solved when it is clearly not solved in the production version.
At best the solution is 'pending'.
Any Idea when the test version goes live?
@BlackDex commented on GitHub (Jan 6, 2026):
The solution isn't pending as it's solved in the
testingtagged images. Also we do ask to search for closed issues too, and you ticked the box.Keeping an issue open isn't useful for us, and tagging a PR that it fixes an issue also automatically closes such an issue.
There also isn't a pending state, and for me pending would mean it still needs to be fixed which isn't the case.
@lolo-orsu commented on GitHub (Jan 8, 2026):
Hi all,
Do you know when the fix will be push in the latest tag?
Cheers
@duczz commented on GitHub (Jan 18, 2026):
i have the problem also with the current Version
@stefan0xC commented on GitHub (Jan 18, 2026):
@duczz
v1.35.1-r0is not the current version. Cf. https://github.com/dani-garcia/vaultwarden/releases/latest@duczz commented on GitHub (Jan 18, 2026):
ah okay, thanks, than the proxmox helper script via Alpine is not up2date.