Cryptography error, The cipher's MAC doesn't match the expected value #5011
Replies: 6 comments 24 replies
-
When did this issue first occur? Were they using the iOS beta with |
Beta Was this translation helpful? Give feedback.
-
|
I have not used a beta for iOS/Bitwarden. The version was the normal version from the App Store. Fortunately, the people have saved their passwords in organizations so that I can simply delete their user accounts and create new ones. I will report if the error occurs again. |
Beta Was this translation helpful? Give feedback.
-
|
We have the same issue on 2 bitwarden instances since yesterday. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, one person has had it for a few weeks and one person started last Friday. Which version of Vaultwarden were you running when you had the problem? And have you managed to get your data back yet? |
Beta Was this translation helpful? Give feedback.
-
|
It might be the issue regarding the key per cipher and why Bitwarden disabled that feature. |
Beta Was this translation helpful? Give feedback.
-
|
If this is the error, then Vaultwarden must have released an update, right? |
Beta Was this translation helpful? Give feedback.
-
|
Must have an update for what? |
Beta Was this translation helpful? Give feedback.
-
|
OK i understand. Should we now only work via the web version? It can start with 100 people at any time with one person, then I'm just restoring the backup every day :( |
Beta Was this translation helpful? Give feedback.
-
|
For anyone that follows this, I had to view several threads to get resolved. You'll need to restore a backup of your vault. If you don't have a backup, you may not resolve this.
If you don't have a backup, you can try to remove the last entry in the Alternatively, perhaps removing the |
Beta Was this translation helpful? Give feedback.
-
|
@BlackDex The entry I think which was causing the issue was one entered earlier today, it has a I tried again to delete just the last entry but the vault remained empty when restarting VW. I wasn't running the latest version of Vaultwarden (I don't know which version), unsure if this matters. |
Beta Was this translation helpful? Give feedback.
-
|
There were some issues with the key per cipher. And this looks like that. Might be an older client which added the entry and caused an issue maybe? I have not yet encountered anything like this my self yet, and i do have a few ciphers with an own key. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much remove the I lost the item that change, but is one for all |
Beta Was this translation helpful? Give feedback.
-
|
I've also gotten hit by this and got around it by pulling the latest and clearing out all the edit: I don't know if the 23 entries survived or not. I have a back up with those keys still intact and could recover if I knew what to change. Only one of those entries has an |
Beta Was this translation helpful? Give feedback.
-
|
I also had this issue after adding a new user, unfortunately no backup to restore. I remove the newly added user, shut down the docker, opened the db.sqlite3 DB with sqlite and checked the latest added entries. |
Beta Was this translation helpful? Give feedback.
-
|
I am able to reproduce this issue using the iOS client with the following procedure:
The Edited to add: I don't need to wait the 2 minutes. I just retested without the wait and it does the same thing. iOS client version: 2024.9.2 (1106). Vaultwarden server version: 1.31.0 |
Beta Was this translation helpful? Give feedback.
-
|
If the client is faulty and sends the organization id in an unrecognizable way (eg. because they for whatever reason change it to |
Beta Was this translation helpful? Give feedback.
-
|
I had it with 3 users with official Bitwarden clients. |
Beta Was this translation helpful? Give feedback.
-
|
With |
Beta Was this translation helpful? Give feedback.
-
|
Yes with 1.31.0 and the Bitwarden clients were not in beta, but the normal stable app from the App Store. |
Beta Was this translation helpful? Give feedback.
-
|
I meant when we released the fixed version |
Beta Was this translation helpful? Give feedback.
-
|
I probably came across the same issue today, running Vaultwarden 1.32.5 I'm sure that this was caused by some entry I added via the latest version of the iOS app which did have an org but no folder/collection assigned which failed, then I selected a collection and was able to save. Sadly I can't reproduce |
Beta Was this translation helpful? Give feedback.
-
|
Same issue here. After trying to save a password to a collection the error occurred. Any way to fix this? Or is restoring a backup the only way? |
Beta Was this translation helpful? Give feedback.
-
|
Copied from earlier answer: |
Beta Was this translation helpful? Give feedback.
-
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: ADMIN_TOKEN
{ "_duo_akey": null, "_enable_duo": false, "_enable_email_2fa": true, "_enable_smtp": true, "_enable_yubico": true, "_icon_service_csp": "", "_icon_service_url": "", "_ip_header_enabled": true, "_max_note_size": 10000, "_smtp_img_src": "cid:", "admin_ratelimit_max_burst": 3, "admin_ratelimit_seconds": 300, "admin_session_lifetime": 20, "admin_token": "***", "allowed_iframe_ancestors": "", "attachments_folder": "data/attachments", "auth_request_purge_schedule": "30 * * * * *", "authenticator_disable_time_drift": false, "data_folder": "data", "database_conn_init": "", "database_max_conns": 10, "database_timeout": 30, "database_url": "***************", "db_connection_retries": 15, "disable_2fa_remember": false, "disable_admin_token": false, "disable_icon_download": false, "domain": "*****://********************", "domain_origin": "*****://********************", "domain_path": "", "domain_set": true, "duo_context_purge_schedule": "30 * * * * *", "duo_host": null, "duo_ikey": null, "duo_skey": null, "duo_use_iframe": false, "email_2fa_auto_fallback": false, "email_2fa_enforce_on_verified_invite": false, "email_attempts_limit": 3, "email_change_allowed": true, "email_expiration_time": 600, "email_token_size": 6, "emergency_access_allowed": true, "emergency_notification_reminder_schedule": "0 3 * * * *", "emergency_request_timeout_schedule": "0 7 * * * *", "enable_db_wal": true, "enable_websocket": true, "event_cleanup_schedule": "0 10 0 * * *", "events_days_retain": null, "experimental_client_feature_flags": "fido2-vault-credentials", "extended_logging": true, "helo_name": null, "hibp_api_key": null, "http_request_block_non_global_ips": true, "http_request_block_regex": null, "icon_blacklist_non_global_ips": true, "icon_blacklist_regex": null, "icon_cache_folder": "data/icon_cache", "icon_cache_negttl": 259200, "icon_cache_ttl": 2592000, "icon_download_timeout": 10, "icon_redirect_code": 302, "icon_service": "internal", "incomplete_2fa_schedule": "30 * * * * *", "incomplete_2fa_time_limit": 3, "increase_note_size_limit": false, "invitation_expiration_hours": 120, "invitation_org_name": "Vaultwarden", "invitations_allowed": true, "ip_header": "X-Real-IP", "job_poll_interval_ms": 30000, "log_file": null, "log_level": "info", "log_timestamp_format": "%Y-%m-%d %H:%M:%S.%3f", "login_ratelimit_max_burst": 10, "login_ratelimit_seconds": 60, "org_attachment_limit": null, "org_creation_users": "", "org_events_enabled": false, "org_groups_enabled": false, "password_hints_allowed": true, "password_iterations": 100000, "push_enabled": false, "push_identity_uri": "https://identity.bitwarden.com", "push_installation_id": "***", "push_installation_key": "***", "push_relay_uri": "https://push.bitwarden.com", "reload_templates": false, "require_device_email": false, "rsa_key_filename": "data/rsa_key", "send_purge_schedule": "0 5 * * * *", "sendmail_command": null, "sends_allowed": true, "sends_folder": "data/sends", "show_password_hint": false, "signups_allowed": false, "signups_domains_whitelist": "**************", "signups_verify": false, "signups_verify_resend_limit": 6, "signups_verify_resend_time": 3600, "smtp_accept_invalid_certs": false, "smtp_accept_invalid_hostnames": false, "smtp_auth_mechanism": null, "smtp_debug": false, "smtp_embed_images": true, "smtp_explicit_tls": null, "smtp_from": "**************************", "smtp_from_name": "Vaultwarden", "smtp_host": "********************", "smtp_password": null, "smtp_port": 25, "smtp_security": "off", "smtp_ssl": null, "smtp_timeout": 15, "smtp_username": null, "templates_folder": "data/templates", "tmp_folder": "data/tmp", "trash_auto_delete_days": null, "trash_purge_schedule": "0 5 0 * * *", "use_sendmail": false, "use_syslog": false, "user_attachment_limit": null, "user_send_limit": null, "web_vault_enabled": true, "web_vault_folder": "web-vault/", "yubico_client_id": "84861", "yubico_secret_key": "***", "yubico_server": null }Vaultwarden Build Version
1.32.0
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
Apache2
Host/Server Operating System
Linux
Operating System Version
Debian Bookworm
Clients
Web Vault, Browser Extension, Desktop, Android, iOS
Client Version
all
Steps To Reproduce
The first person's Bitwarden app crashed on their cell phone and the problem has been there ever since.
For the second person, the problem just happened until daily use without crash
Expected Result
The password manager server should work
Actual Result
For the two people in question, the apps no longer work with the error message mentioned in the title and the Web Vault only shows an infinite loading symbol for the entries/folders
Logs
No response
Screenshots or Videos
Additional Context
Beta Was this translation helpful? Give feedback.
All reactions