mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-03-02 22:57:18 -05:00
Collections cannot be assigned since Desktop Version 6.0 in self-hosted Servers #1955
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
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#1955
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 @DenisGajs on GitHub (Jun 28, 2024).
Collections cannot be assigned since Desktop Version 6.0 in self-hosted Servers, an unexpected error occurs.
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: DOMAIN, SENDS_ALLOWED, USER_ATTACHMENT_LIMIT, ORG_ATTACHMENT_LIMIT, TRASH_AUTO_DELETE_DAYS, SIGNUPS_ALLOWED, SIGNUPS_VERIFY, ORG_CREATION_USERS, INVITATIONS_ALLOWED, EMERGENCY_ACCESS_ALLOWED, SHOW_PASSWORD_HINT, ADMIN_TOKEN, INVITATION_ORG_NAME, ADMIN_SESSION_LIFETIME, SMTP_HOST, SMTP_SECURITY, SMTP_PORT, SMTP_FROM, SMTP_FROM_NAME, SMTP_USERNAME, SMTP_PASSWORD, SMTP_TIMEOUT
Install method: Docker
Clients used: desktop
MySQL/MariaDB or PostgreSQL version: SQLite
Other relevant details:
Steps to reproduce
Expected behaviour
The entry should be assigned to the selected collection(s)Actual behaviour
An error pop up comes with the text "an unexpected error has occurred" and nothing happens.Troubleshooting data
The problem occurs since Bitwarden Desktop Version 6.0 so Version 6.1, 6.2 and 6.3 has the same error.
Version 5.0 works fine without this bug
@BlackDex commented on GitHub (Jun 28, 2024):
Closing as a duplicate of #4681