starred/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2025-12-09 09:13:02 +03:00
Code Issues 429 Packages Projects Releases 10 Wiki Activity

web version creates folder inside "All vaults" instead of "My vault" per default #899

New Issue
Closed
opened 2025-10-09 16:56:18 +03:00 by OVERLORD · 10 comments
OVERLORD commented 2025-10-09 16:56:18 +03:00
Owner
Copy Link

Originally created by @AnthillSudoku on GitHub.

Subject of the issue

web version creates folder inside "All vaults" instead of "My vault" per default

Deployment environment

I am using https://bitwarden.garudalinux.org as an end user and have no access to the admin page

Steps to reproduce

I have no organizations, so "My Vault" is the only vault

  1. open vaultwarden from the web
  2. "All Vaults" is selected by default, if not select it
  3. press plus button to add a folder
  4. name it, eg "test from web"
  5. select "My Vault"

Expected behaviour

folder "test from web" must be listed in "My Vault" folders

Actual behaviour

folder "test from web" is not listed in "My Vault" folders, but only in "All Vaults".

Firefox extensions and Android version creates the new folders correctly inside "My Vault" and they are also displayed in "All Vaults"

Originally created by @AnthillSudoku on GitHub. <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Describe your issue here. --> web version creates folder inside "All vaults" instead of "My vault" per default ### Deployment environment I am using https://bitwarden.garudalinux.org as an end user and have no access to the admin page ### 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? --> I have no organizations, so "My Vault" is the only vault 1. open vaultwarden from the web 2. "All Vaults" is selected by default, if not select it 3. press plus button to add a folder 4. name it, eg "test from web" 5. select "My Vault" ### Expected behaviour <!-- Tell us what you expected to happen --> folder "test from web" must be listed in "My Vault" folders ### Actual behaviour <!-- Tell us what actually happened --> folder "test from web" is not listed in "My Vault" folders, but only in "All Vaults". Firefox extensions and Android version creates the new folders correctly inside "My Vault" and they are also displayed in "All Vaults"
OVERLORD added the troubleshooting label 2025-10-09 16:56:18 +03:00
OVERLORD commented 2025-10-09 16:56:20 +03:00
Author
Owner
Copy Link

@AnthillSudoku commented on GitHub:

First, test this with the testing tagged images of Vaultwarden

sorry, the instance is not mine, I am just an end user

test this on vault.bitwarden.com

does not have this issue, in the main page both instances states 2023.2.0

@AnthillSudoku commented on GitHub: > First, test this with the testing tagged images of Vaultwarden sorry, the instance is not mine, I am just an end user > test this on vault.bitwarden.com does not have this issue, in the main page both instances states 2023.2.0
OVERLORD commented 2025-10-09 16:56:20 +03:00
Author
Owner
Copy Link

@AnthillSudoku commented on GitHub:

My Vault's folders

My Vaults

Vault's folders

Vault

@AnthillSudoku commented on GitHub: # My Vault's folders ![My Vaults](https://user-images.githubusercontent.com/15078341/222557440-959ef9f3-1c73-4227-a40d-07508193d2b4.png) # Vault's folders ![Vault](https://user-images.githubusercontent.com/15078341/222557446-dfeb0d41-fd28-453d-82fb-160c60f51478.png)
OVERLORD commented 2025-10-09 16:56:20 +03:00
Author
Owner
Copy Link

@stefan0xC commented on GitHub:

I'm not sure what the issue is. Does the folder disappear when you click my vault? Testing it with the latest testing image, i.e. 337cbfaf seems to work just fine.

Peek 2023-03-02 22-14.webm

@stefan0xC commented on GitHub: I'm not sure what the issue is. Does the folder disappear when you click my vault? Testing it with the latest `testing` image, i.e. `337cbfaf` seems to work just fine. [Peek 2023-03-02 22-14.webm](https://user-images.githubusercontent.com/509385/222555395-bc39b5ee-128a-4766-b56e-4764c24bb581.webm)
OVERLORD commented 2025-10-09 16:56:21 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub:

Seems like a client issue to me.
First, test this with the testing tagged images of Vaultwarden.
Second, test this on vault.bitwarden.com if it also happens there it's definitely a client issue. Also, since you say ot works on the extensions, it probably isn't a server side bug.

If this also happens on the Bitwarden Cloud, then i suggest to report this at the bitwarden/clients repo.

@BlackDex commented on GitHub: Seems like a client issue to me. First, test this with the `testing` tagged images of Vaultwarden. Second, test this on vault.bitwarden.com if it also happens there it's definitely a client issue. Also, since you say ot works on the extensions, it probably isn't a server side bug. If this also happens on the Bitwarden Cloud, then i suggest to report this at the bitwarden/clients repo.
OVERLORD commented 2025-10-09 16:56:21 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub:

Thanks for the report. We have to investigate.

@BlackDex commented on GitHub: Thanks for the report. We have to investigate.
OVERLORD commented 2025-10-09 16:56:23 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub:

According to the /api/config endpoint the server you are using is still on version 024d12d

@BlackDex fixed some v2023.2.0 API calls in 7ec00d3 so this might be why? (Have not tested it.)

I tested it on my personal hosted instance. It should be updated, but, i haven't checked to be honest haha.

@BlackDex commented on GitHub: > According to the `/api/config` endpoint the server you are using is still on version [024d12d](https://github.com/dani-garcia/vaultwarden/commit/024d12db08820d89eb7fd8551a5773dc9f295feb) > > @BlackDex fixed some v2023.2.0 API calls in [7ec00d3](https://github.com/dani-garcia/vaultwarden/commit/7ec00d3850f0c058314b4bc4a3c5d1094882c434) so this might be why? (Have not tested it.) I tested it on my personal hosted instance. It should be updated, but, i haven't checked to be honest haha.
OVERLORD commented 2025-10-09 16:56:23 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub:

The issue is that the folder is visible everywhere, no matter which org you select. At least that is what i just noticed on my instance.

I can't debug right now my self, so no clue why this is.

@BlackDex commented on GitHub: The issue is that the folder is visible everywhere, no matter which org you select. At least that is what i just noticed on my instance. I can't debug right now my self, so no clue why this is.
OVERLORD commented 2025-10-09 16:56:23 +03:00
Author
Owner
Copy Link

@stefan0xC commented on GitHub:

According to the /api/config endpoint the server you are using is still on version 024d12db

@BlackDex fixed some v2023.2.0 API calls in 7ec00d3850 so this might be why? (Have not tested it.)

@stefan0xC commented on GitHub: According to the `/api/config` endpoint the server you are using is still on version 024d12db @BlackDex fixed some v2023.2.0 API calls in 7ec00d3850f0c058314b4bc4a3c5d1094882c434 so this might be why? (Have not tested it.)
OVERLORD commented 2025-10-09 16:56:23 +03:00
Author
Owner
Copy Link

@stefan0xC commented on GitHub:

The issue is that the folder is visible everywhere, no matter which org you select. At least that is what i just noticed on my instance.

Okay, tested it with two folders that have items in it and on my instance "My Vault" always shows all folders except for the two folders that have items in it. Seems to be tracked upstream here https://github.com/bitwarden/clients/issues/4805 (oh, and it's already fixed so in the next release of the web-vault this should not happen anymore.)

@stefan0xC commented on GitHub: > The issue is that the folder is visible everywhere, no matter which org you select. At least that is what i just noticed on my instance. > Okay, tested it with two folders that have items in it and on my instance "My Vault" always shows all folders except for the two folders that have items in it. Seems to be tracked upstream here https://github.com/bitwarden/clients/issues/4805 (oh, and it's already fixed so in the next release of the web-vault this should not happen anymore.)
OVERLORD commented 2025-10-09 16:56:24 +03:00
Author
Owner
Copy Link

@BlackDex commented on GitHub:

The issue is that the folder is visible everywhere, no matter which org you select. At least that is what i just noticed on my instance.

Okay, tested it with two folders that have items in it and on my instance "My Vault" always shows all folders except for the two folders that have items in it. Seems to be tracked upstream here bitwarden/clients#4805 (oh, and it's already fixed so in the next release of the web-vault this should not happen anymore.)

Yea, i thought it was expected behavior indeed. Because, you can assign any cipher, not just personal items to a folder.

@BlackDex commented on GitHub: > > The issue is that the folder is visible everywhere, no matter which org you select. At least that is what i just noticed on my instance. > > Okay, tested it with two folders that have items in it and on my instance "My Vault" always shows all folders except for the two folders that have items in it. Seems to be tracked upstream here [bitwarden/clients#4805](https://github.com/bitwarden/clients/issues/4805) (oh, and it's already fixed so in the next release of the web-vault this should not happen anymore.) Yea, i thought it was expected behavior indeed. Because, you can assign any cipher, not just personal items to a folder.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
better for forum
bug
bug
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
troubleshooting
wontfix
No Label troubleshooting
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#899
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?