mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #2725] Cipher doesn't exist #1358
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#1358
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 @Gliptal on GitHub (Sep 5, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2725
Subject of the issue
Some entry cards don't open anymore, failing with a
Cipher doesn't existerror. The data is still there, since I can copy usernames and passwords from the entry's context menu in the vault.Troubleshooting data
@BlackDex commented on GitHub (Sep 5, 2022):
This looks like a JavaScript error. Is there also an issue on the Vaultwarden logs? Also, which version of Vaultwarden are you using.
Could you provide the support string from.the diagnostics page from the admin interface?
And, have you tried an other browser? Or Private/Incognito mode?
@Gliptal commented on GitHub (Sep 5, 2022):
Apologies for the missing info, the collague that installed the server is out today. I'll update it as soon as I can.
I later tried in incognito mode and in the Windows app, and it seems like I lost access to the organization that contained the affected entries (among the others). I think that the error showed up because I was in an inconsistent permissions state (wasn't in the org, but the browser thought I was until I explicitely logged out and logged back in).
I'll know more about what is happening server side tomorrow.
@BlackDex commented on GitHub (Sep 5, 2022):
That can happen if you are still logged in and there hasn't been a new sync done, and you want to edit a cipher. Not really something we could fix.
@Gliptal commented on GitHub (Sep 5, 2022):
The app is also failing any sync requests, so I guess something is up server side.