github-starred/vaultwarden
2
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-05-24 17:12:43 -05:00
Code Issues 307 Packages Projects Releases 83 Wiki Activity

[GH-ISSUE #6638] Organization creation fails in web vault with "Cannot read properties of undefined (reading 'find')" - v1.35.1 #19265

New Issue
Closed
opened 2026-04-25 21:48:36 -05:00 by GiteaMirror · 21 comments
GiteaMirror commented 2026-04-25 21:48:36 -05:00
Owner
Copy Link

Originally created by @aknanai on GitHub (Dec 30, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6638

Prerequisites

Vaultwarden Support String

Description

Creating a new organization in the web vault fails with a JavaScript error.

Steps to Reproduce

  1. Log into web vault
  2. Click "+ New organization"
  3. Enter organization name and email
  4. Click "Submit"

Expected Behavior

Organization should be created successfully.

Actual Behavior

Error popup appears: "Cannot read properties of undefined (reading 'find')"

Browser Console Error

console-log.service.ts:51 Async submit exception: TypeError: Cannot read properties of undefined (reading 'find')
at bit-submit.directive.ts:48
at catchError.ts:117

Environment

  • Vaultwarden version: 1.35.1
  • Platform: Synology NAS (Docker)
  • Browser: Microsoft Edge (also tested in incognito)

Workaround

Downgrading to version 1.34.0 resolves the issue. Organization creation works normally in 1.34.0.

Vaultwarden Build Version

1.35.1

Deployment method

Official Container Image

Custom deployment method

No response

Reverse Proxy

nginx

Host/Server Operating System

Linux

Operating System Version

Synology 7.x

Clients

Web Vault

Client Version

No response

Steps To Reproduce

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. Click on '...'
  5. Etc '...'

Expected Result

Expected Behavior

Organization should be created successfully.

Actual Result

Actual Behavior

Error popup appears: "Cannot read properties of undefined (reading 'find')"

Logs

Screenshots or Videos

No response

Additional Context

No response

Originally created by @aknanai on GitHub (Dec 30, 2025). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6638 ### Prerequisites - [x] I have searched the existing **Closed _AND_ Open** [Issues](https://github.com/dani-garcia/vaultwarden/issues?q=is%3Aissue%20) **_AND_** [Discussions](https://github.com/dani-garcia/vaultwarden/discussions?discussions_q=) - [x] I have searched and read the [documentation](https://github.com/dani-garcia/vaultwarden/wiki/) ### Vaultwarden Support String ## Description Creating a new organization in the web vault fails with a JavaScript error. ## Steps to Reproduce 1. Log into web vault 2. Click "+ New organization" 3. Enter organization name and email 4. Click "Submit" ## Expected Behavior Organization should be created successfully. ## Actual Behavior Error popup appears: "Cannot read properties of undefined (reading 'find')" ## Browser Console Error console-log.service.ts:51 Async submit exception: TypeError: Cannot read properties of undefined (reading 'find') at bit-submit.directive.ts:48 at catchError.ts:117 ## Environment - Vaultwarden version: 1.35.1 - Platform: Synology NAS (Docker) - Browser: Microsoft Edge (also tested in incognito) ## Workaround Downgrading to version 1.34.0 resolves the issue. Organization creation works normally in 1.34.0. ### Vaultwarden Build Version 1.35.1 ### Deployment method Official Container Image ### Custom deployment method _No response_ ### Reverse Proxy nginx ### Host/Server Operating System Linux ### Operating System Version Synology 7.x ### Clients Web Vault ### Client Version _No response_ ### Steps To Reproduce 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. Click on '...' 5. Etc '...' ### Expected Result ## Expected Behavior Organization should be created successfully. ### Actual Result ## Actual Behavior Error popup appears: "Cannot read properties of undefined (reading 'find')" ### Logs ```text ``` ### Screenshots or Videos _No response_ ### Additional Context _No response_
GiteaMirror added the bug label 2026-04-25 21:48:36 -05:00
GiteaMirror commented 2026-04-25 21:48:38 -05:00
Author
Owner
Copy Link

@stefan0xC commented on GitHub (Dec 30, 2025):

Oh, thanks. Seems like I missed patching out this particular change 12222e39b4 in web-v2025.12.1 which does not work because we don't have any plans in Vaultwarden. I will create a PR for this shortly.

<!-- gh-comment-id:3700528294 --> @stefan0xC commented on GitHub (Dec 30, 2025): Oh, thanks. Seems like I missed patching out this particular change https://github.com/bitwarden/clients/commit/12222e39b47cbeb10c87eb7a42c4f7490242f7d5 in `web-v2025.12.1` which does not work because we don't have any plans in Vaultwarden. I will create a PR for this shortly.
GiteaMirror commented 2026-04-25 21:48:39 -05:00
Author
Owner
Copy Link

@ln-12 commented on GitHub (Dec 31, 2025):

@stefan0xC There seems to be a similar issue when trying to enable the option "Log in with passkey" under Settings -> Security where I get the error:

An error has occurred.
Cannot read properties of undefined (reading 'split')

Could you look into that as well here or should I create a new issue?

<!-- gh-comment-id:3701819945 --> @ln-12 commented on GitHub (Dec 31, 2025): @stefan0xC There seems to be a similar issue when trying to enable the option "Log in with passkey" under `Settings `-> `Security` where I get the error: ``` An error has occurred. Cannot read properties of undefined (reading 'split') ``` Could you look into that as well here or should I create a new issue?
GiteaMirror commented 2026-04-25 21:48:39 -05:00
Author
Owner
Copy Link

@stefan0xC commented on GitHub (Dec 31, 2025):

@ln-12 that option is not supported yet and should already be hidden via CSS
3e2cef7e8b/src/static/templates/scss/vaultwarden.scss.hbs (L57-L60)

<!-- gh-comment-id:3701874160 --> @stefan0xC commented on GitHub (Dec 31, 2025): @ln-12 that option is not supported yet and should already be hidden via CSS https://github.com/dani-garcia/vaultwarden/blob/3e2cef7e8b27cf33cb735d428553f835bc5dd6c2/src/static/templates/scss/vaultwarden.scss.hbs#L57-L60
GiteaMirror commented 2026-04-25 21:48:40 -05:00
Author
Owner
Copy Link

@Karbust commented on GitHub (Dec 31, 2025):

Oh, thanks. Seems like I missed patching out this particular change bitwarden/clients@12222e3 in web-v2025.12.1 which does not work because we don't have any plans in Vaultwarden. I will create a PR for this shortly.

When will this change be rolled out? New instance, don't want to start with an older version just to be able to create an organization.

Thank you for the quick fix.

<!-- gh-comment-id:3701953984 --> @Karbust commented on GitHub (Dec 31, 2025): > Oh, thanks. Seems like I missed patching out this particular change [bitwarden/clients@12222e3](https://github.com/bitwarden/clients/commit/12222e39b47cbeb10c87eb7a42c4f7490242f7d5) in `web-v2025.12.1` which does not work because we don't have any plans in Vaultwarden. I will create a PR for this shortly. When will this change be rolled out? New instance, don't want to start with an older version just to be able to create an organization. Thank you for the quick fix.
GiteaMirror commented 2026-04-25 21:48:40 -05:00
Author
Owner
Copy Link

@ln-12 commented on GitHub (Dec 31, 2025):

@stefan0xC Well, for me it's definitely visible in 2025.12.1:

Image
<!-- gh-comment-id:3702204137 --> @ln-12 commented on GitHub (Dec 31, 2025): @stefan0xC Well, for me it's definitely visible in 2025.12.1: <img width="889" height="244" alt="Image" src="https://github.com/user-attachments/assets/0515b7ab-244e-4089-a17e-176069ed86fb" />
GiteaMirror commented 2026-04-25 21:48:41 -05:00
Author
Owner
Copy Link

@stefan0xC commented on GitHub (Dec 31, 2025):

@ln-12 Does your browser block the /css/vaultwarden.css file? Or do you have perhaps overwritten the vaultwarden.scss.hbs template?

<!-- gh-comment-id:3702263782 --> @stefan0xC commented on GitHub (Dec 31, 2025): @ln-12 Does your browser block the `/css/vaultwarden.css` file? Or do you have perhaps [overwritten the vaultwarden.scss.hbs template](https://github.com/dani-garcia/vaultwarden/wiki/Customize-Vaultwarden-CSS)?
GiteaMirror commented 2026-04-25 21:48:42 -05:00
Author
Owner
Copy Link

@ln-12 commented on GitHub (Dec 31, 2025):

After clearing the browser cache it works now. Seems like the old vaultwarden.css was still used. Sorry, my bad.

<!-- gh-comment-id:3702270658 --> @ln-12 commented on GitHub (Dec 31, 2025): After clearing the browser cache it works now. Seems like the old `vaultwarden.css` was still used. Sorry, my bad.
GiteaMirror commented 2026-04-25 21:48:42 -05:00
Author
Owner
Copy Link

@rivolity commented on GitHub (Dec 31, 2025):

Big Issue on that
On a fresh Vaultwarden deployment, a user who has permission to create organizations encounters a frontend error when attempting to create their first organization.
The UI displays an error and the organization is not created.
I downgraded to 1.34 to create the organization and switched back to 1.35.1
Just need to know why the bug is closed ?

Image
<!-- gh-comment-id:3702576569 --> @rivolity commented on GitHub (Dec 31, 2025): Big Issue on that On a fresh Vaultwarden deployment, a user who has permission to create organizations encounters a frontend error when attempting to create their first organization. The UI displays an error and the organization is not created. I downgraded to 1.34 to create the organization and switched back to 1.35.1 Just need to know why the bug is closed ? <img width="396" height="118" alt="Image" src="https://github.com/user-attachments/assets/74b4e94f-c7ae-4ac4-86a4-34f2510d8ce0" />
GiteaMirror commented 2026-04-25 21:48:43 -05:00
Author
Owner
Copy Link

@stefan0xC commented on GitHub (Dec 31, 2025):

probably because of my comment in this PR https://github.com/dani-garcia/bw_web_builds/pull/224 (the web-vault still needs to be released and then also used before this is truly resolved).

<!-- gh-comment-id:3702579684 --> @stefan0xC commented on GitHub (Dec 31, 2025): probably because of my comment in this PR https://github.com/dani-garcia/bw_web_builds/pull/224 (the web-vault still needs to be released and then also used before this is truly resolved).
GiteaMirror commented 2026-04-25 21:48:44 -05:00
Author
Owner
Copy Link

@xxcbzxx commented on GitHub (Jan 3, 2026):

vaultwarden-server:latest

returns the same, still having issues with creating organisation,

deployment method: portainer via Swarm

<!-- gh-comment-id:3706696428 --> @xxcbzxx commented on GitHub (Jan 3, 2026): vaultwarden-server:latest returns the same, still having issues with creating organisation, deployment method: portainer via Swarm
GiteaMirror commented 2026-04-25 21:48:45 -05:00
Author
Owner
Copy Link

@esperc commented on GitHub (Jan 3, 2026):

vaultwarden-server:latest
returns the same, still having issues with creating organisation,
deployment method: portainer via Swarm

I'm in the exact same boat. What will be the path to fixing the issue with docker? Just repull the :latest image?

<!-- gh-comment-id:3706765239 --> @esperc commented on GitHub (Jan 3, 2026): > vaultwarden-server:latest > returns the same, still having issues with creating organisation, > deployment method: portainer via Swarm I'm in the exact same boat. What will be the path to fixing the issue with docker? Just repull the :latest image?
GiteaMirror commented 2026-04-25 21:48:46 -05:00
Author
Owner
Copy Link

@BlackDex commented on GitHub (Jan 3, 2026):

No you need the :testing image which is based upon main.

<!-- gh-comment-id:3706906128 --> @BlackDex commented on GitHub (Jan 3, 2026): No you need the `:testing` image which is based upon main.
GiteaMirror commented 2026-04-25 21:48:47 -05:00
Author
Owner
Copy Link

@ditahkk commented on GitHub (Jan 3, 2026):

Thanks for fixing this bug over the holidays, the tag: "testing-alpine" works well for creating orgs via the Web

<!-- gh-comment-id:3707313773 --> @ditahkk commented on GitHub (Jan 3, 2026): Thanks for fixing this bug over the holidays, the `tag: "testing-alpine" ` works well for creating orgs via the Web
GiteaMirror commented 2026-04-25 21:48:48 -05:00
Author
Owner
Copy Link

@lakemike commented on GitHub (Jan 7, 2026):

Same for me with a fresh install. Happy to report once this is out of testing. Also- Happy New Year and by this channel, huge thanks to everyone contributing to vaultwarden!

<!-- gh-comment-id:3720285783 --> @lakemike commented on GitHub (Jan 7, 2026): Same for me with a fresh install. Happy to report once this is out of testing. Also- Happy New Year and by this channel, huge thanks to everyone contributing to vaultwarden!
GiteaMirror commented 2026-04-25 21:48:49 -05:00
Author
Owner
Copy Link

@delasource commented on GitHub (Jan 8, 2026):

when can we expect testing to be merged into latest/stable ?

<!-- gh-comment-id:3726391519 --> @delasource commented on GitHub (Jan 8, 2026): when can we expect testing to be merged into latest/stable ?
GiteaMirror commented 2026-04-25 21:48:49 -05:00
Author
Owner
Copy Link

@stefan0xC commented on GitHub (Jan 9, 2026):

when can we expect testing to be merged into latest/stable ?

That's not how this works. Like testing the latest release is also build from the main branch so the fix is already merged. (The difference is that testing is always build from the head of the branch while releases are tagged versions meaning fixed points in time, that are deemed stable at the time.)

If you are asking when is the next release then please see this FAQ for a general answer. Given that there is already a PR pending https://github.com/dani-garcia/vaultwarden/pull/6686 for the issue mentioned here https://github.com/dani-garcia/vaultwarden/pull/6646#issuecomment-3723095246 I'm guessing that it will be hopefully be in the next few days...

<!-- gh-comment-id:3726692191 --> @stefan0xC commented on GitHub (Jan 9, 2026): > when can we expect testing to be merged into latest/stable ? That's not how this works. Like `testing` the latest release is also build from the `main` branch so the fix is already merged. (The difference is that `testing` is always build from the head of the branch while releases are tagged versions meaning fixed points in time, that are deemed `stable` at the time.) If you are asking when is the next release then please [see this FAQ for a general answer](https://github.com/dani-garcia/vaultwarden/wiki/FAQs#when-is-the-next-release-of-vaultwarden-can-you-give-an-eta). Given that there is already a PR pending https://github.com/dani-garcia/vaultwarden/pull/6686 for the issue mentioned here https://github.com/dani-garcia/vaultwarden/pull/6646#issuecomment-3723095246 I'm guessing that it will be hopefully be in the next few days...
GiteaMirror commented 2026-04-25 21:48:50 -05:00
Author
Owner
Copy Link

@lakemike commented on GitHub (Jan 10, 2026):

I got the new version today via TrueNAS docker app. Seems to work! Thanks!

<!-- gh-comment-id:3733235856 --> @lakemike commented on GitHub (Jan 10, 2026): I got the new version today via TrueNAS docker app. Seems to work! Thanks!
GiteaMirror commented 2026-04-25 21:48:51 -05:00
Author
Owner
Copy Link

@XtheCutterBetOn commented on GitHub (Jan 15, 2026):

Thanks
New one image: vaultwarden/server:1.35.2 is fixed

<!-- gh-comment-id:3754180598 --> @XtheCutterBetOn commented on GitHub (Jan 15, 2026): Thanks New one image: vaultwarden/server:1.35.2 is fixed
GiteaMirror commented 2026-04-25 21:48:52 -05:00
Author
Owner
Copy Link

@GammaScorpii commented on GitHub (Jan 16, 2026):

I'm on 1.35.2 image and still seem to have this issue? Can't seem to create organizations.

<!-- gh-comment-id:3759817000 --> @GammaScorpii commented on GitHub (Jan 16, 2026): I'm on 1.35.2 image and still seem to have this issue? Can't seem to create organizations.
GiteaMirror commented 2026-04-25 21:48:53 -05:00
Author
Owner
Copy Link

@stefan0xC commented on GitHub (Jan 16, 2026):

I'm on 1.35.2 image and still seem to have this issue? Can't seem to create organizations.

Are you using a custom web-vault? If you open /vw-version.json does it say {"version":"2025.12.1+build.3"}? You might have the old web-vault still cached, so you might want to force reload (Ctrl+Shift+R) your site.

<!-- gh-comment-id:3759834930 --> @stefan0xC commented on GitHub (Jan 16, 2026): > I'm on 1.35.2 image and still seem to have this issue? Can't seem to create organizations. Are you using a custom web-vault? If you open `/vw-version.json` does it say `{"version":"2025.12.1+build.3"}`? You might have the old web-vault still cached, so you might want to force reload (Ctrl+Shift+R) your site.
GiteaMirror commented 2026-04-25 21:48:54 -05:00
Author
Owner
Copy Link

@lakemike commented on GitHub (Jan 16, 2026):

I'm on 1.35.2 image and still seem to have this issue? Can't seem to create organizations.

Do you still see the error message as per subject of this issue?

<!-- gh-comment-id:3759836823 --> @lakemike commented on GitHub (Jan 16, 2026): > I'm on 1.35.2 image and still seem to have this issue? Can't seem to create organizations. Do you still see the error message as per subject of this issue?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
documentation
duplicate
enhancement
future Vault
good first issue
help wanted
low priority
notes
pull-request
Mirrored from GitHub Pull Request
 question
SSO
Third party
troubleshooting
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#19265
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?