### Vaultwarden Build Version
v1.35.1
### Deployment method
Official Container Image
### Custom deployment method
_No response_
### Reverse Proxy
cloudflare tunnel
### Host/Server Operating System
Other
### Operating System Version
truenas 25.04.2.6
### Clients
Browser Extension, Web Vault
### Client Version
_No response_
### Steps To Reproduce
1. login
2. create organization
### Expected Result
organization created
### Actual Result
Error: Cannot read properties of undefined (reading 'find')
### Logs
```text
no errors in log to see
<!-- gh-comment-id:3713833492 -->
@woprandi commented on GitHub (Jan 6, 2026):
It's fixed with the `testing` image tag
https://github.com/dani-garcia/vaultwarden/issues/6638
https://github.com/dani-garcia/bw_web_builds/pull/224
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?
<!-- gh-comment-id:3713892072 -->
@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?
The solution isn't pending as it's solved in the testing tagged 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.
<!-- gh-comment-id:3713925181 -->
@BlackDex commented on GitHub (Jan 6, 2026):
The solution isn't pending as it's solved in the `testing` tagged 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.
<!-- gh-comment-id:3765364254 -->
@stefan0xC commented on GitHub (Jan 18, 2026):
@duczz `v1.35.1-r0` is not the current version. Cf. https://github.com/dani-garcia/vaultwarden/releases/latest
ah okay, thanks, than the proxmox helper script via Alpine is not up2date.
<!-- gh-comment-id:3765369526 -->
@duczz commented on GitHub (Jan 18, 2026):
ah okay, thanks, than the proxmox helper script via Alpine is not up2date.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.
@ghost 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.