Replies: 13 comments 45 replies
-
|
What are the logs from Vaultwarden? |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue. this is what I get when I open the app that fails. I cant tell if the app is at fault or the server is. Everything was working fine untile their last update this morning for me Vaultwarden Web EDIT: I just did a docker pull and the app works now. So I am not sure what the issue is actually. |
Beta Was this translation helpful? Give feedback.
-
|
Same logs here, when opening the app: |
Beta Was this translation helpful? Give feedback.
-
|
That is strange. Cache maybe? |
Beta Was this translation helpful? Give feedback.
-
|
Is it enough if I send the response to the |
Beta Was this translation helpful? Give feedback.
-
|
@halms If you can see the vault interface with an error and the sync call succeeded with an ok on the Vaultwarden side. Then yes, that would be enough. Again, all is encrypted, but the full output is needed. |
Beta Was this translation helpful? Give feedback.
-
Why close issue #4920 and turn this into a discussion? Seems like multiple people reporting an issue. I for one haven’t updated my iOS app until I see how this pans out. |
Beta Was this translation helpful? Give feedback.
-
|
Since if it this is an issue with the response of Vaultwarden then there already is an item open. That does have android in the title, but the case is the same. Keeping two issues open with the same story is not needed. |
Beta Was this translation helpful? Give feedback.
-
|
Okay, good news! |
Beta Was this translation helpful? Give feedback.
-
|
Does anyone know of a way to revert the iOS app if there is an issue? I can update the app to see if I experience similar issues, but not if I can revert. |
Beta Was this translation helpful? Give feedback.
-
|
Only way i know of is via itunes backup. But that was a long time ago. |
Beta Was this translation helpful? Give feedback.
-
|
Let me try a secondary device such as an iPad. |
Beta Was this translation helpful? Give feedback.
-
|
No apparent issues on the iPad with new app |
Beta Was this translation helpful? Give feedback.
-
|
I was able to solve this issue for my case, details in the issue: #4870 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
It seems there are different problems by different users regarding Bitwarden IoS 2024.8.1 errors. App only shows "An errors has occured". My setup: Tried both Vaultwarden and Bitwarden open source as Docker on Synology NAS. Synology DDNS and reverse proxy with Let's encrypt certificate. DNS entry points to intranet 192.168.178.x ( I use all clients only within the intranet). Findings:
Summary: |
Beta Was this translation helpful? Give feedback.
-
|
I am using a synology nas with vaultwarden in a docker container. I am using built in reverse proxy, I am not seeing any issues with the latest iOS app rolled out. Additionally I am running latest VW image (not testing). |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, that's interesting. Still doesn't work for me. Do you have any online instructions which you followed, which I can then try to repeat ? I am new, hence if this is not the right place, to ask such questions, let me know please. My docker-compose ( tried both server:testing and server:latest) 
My temporary DDNS setup with Let'S Encrypt cert resolving to an intranet addresss: 192.168.178.86 ( clients only used in local wifi network). Reverse Proxy: 
|
Beta Was this translation helpful? Give feedback.
-
|
I've used this resource. Looking at your port, 8080 doesn't appear correct. Should be port 80. Rocket port is 8080 so there maybe a conflict there. |
Beta Was this translation helpful? Give feedback.
-
|
Curious, did you add an allow rule into your firewall? If so what was the port you used in the firewall entry? |
Beta Was this translation helpful? Give feedback.
-
|
I was able to solve the Problem. In the end it was trivial, but difficult to find, and I only sorted it out after quite some time: My working Setup:
Previous Problem Analysis: Tcpdump packet trace on IPhone showed a DNS lookup attempt for my vaultwarden Synology DDNS Domain. However the DNS-server response didn't show a resolved IP-address, failed ! My Mac was able to connect to Vaultwarden any time, including the Bitwarden Mac client. I only figured out lately that the Mac had configured a manual DNS ( e.g. 8.8.8.8) and my mobile devices were using the default Wifi-router/internet-provider configured DNS. Hence mobile devices were not able to resolve my vaultwarden synology DDNS domain, while being able to resolve any other domain though. Simply configuring a manual DNS of e.g. 8.8.8.8 in the iPhone settings solved the issue right away. Trivial, but difficult to find. I had suspected a SW configuration issue and tried several different bittwarden and vaultwarden-docker variants with and without separate nginx setups on Synology, to no avail. Advise for other starters:
|
Beta Was this translation helpful? Give feedback.
-
|
Vaultwarden 1.32.0 Docker container on Synology NAS with local reverse proxy and Let's Encrypt certificate. |
Beta Was this translation helpful? Give feedback.
-
|
I upgraded to the new iOS app 2024.8.1 and moved a password from my personal vault my my family organization and now I get the following error on my phone. "Cryptograpy error. The cipher's MAC doesn't match the expected value". So nothing loads on my phone. When I go to the WEB UI it spins and loads really slow but eventually loads my vault, I however can not find the password I moved. I am guessing something got corrupted but im not 100% sure. Any ideas? I have updated my vaultwaredn to the testing build. |
Beta Was this translation helpful? Give feedback.
-
|
This has been reported already and fixed in the latest version. Unfortunately once the corruption happens you need to do something in the database to fix. Reference #4767 and continue discussion there to keep the issues organized. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you I did not see that discussion! |
Beta Was this translation helpful? Give feedback.
-
|
@BlackDex I set up a local debug environment (only the network side; I don't have a Mac to actually debug the iOS app and the Bitwarden devs decided to send debug logs to crashlytics instead of the device log where I could have intercepted it). Anyway, I am not yet sure if it's the only problem, but one problem at least is the format of secure notes. Old notes in my vault have a structure like this (only the relevant parts): {
"type": 2,
"data": {
"name": "...",
"fields": [...]
},
"fields": [...],
"secureNote": {
"name": "...",
"fields": [...]
}
}New notes on the other hand look like this: {
"type": 2,
"data": {
"name": "...",
"fields": [...]
},
"fields": [...],
"secureNote": {
"type": 0
}
}As you can see, the "secureNote" field does apparently no longer contain (a third?!) copy of the data, but simply states With the old structure, my sync fails. With the content of the Edit: I just realized: it doesn't even care about the other values in |
Beta Was this translation helpful? Give feedback.
-
|
What you need is the sync response from Vaultwarden. @aksdb can you provide what is actually in database for those secure notes in the data column? I have seen a lot of weird combos there, but never the records you mention there like name and fields. Because that i do not filter/check. If those also contain a type field, then it will now be kept. |
Beta Was this translation helpful? Give feedback.
-
|
@BlackDex here is an example of one of the notes (redacted): {
"Favorite": false,
"Fields":
[
{
"Name": "....",
"Type": 1,
"Value": "...."
}
],
"Name": "....",
"Notes": null,
"RevisionDate": "2018-11-01T16:57:02Z"
} |
Beta Was this translation helpful? Give feedback.
-
|
That looks more like a login item i think |
Beta Was this translation helpful? Give feedback.
-
|
It has SELECT created_at, data->'Type', data FROM ciphers
WHERE atype==2 and data->'Type' is null;Also I noticed that all the affected notes are from the end of 2018 (november and december), so from around vaultwarden 1.0 -and whatever version the bitwarden clients had back then. Additional finding: Running that query I realized, that the current iOS bitwarden client seems to write SELECT created_at, atype, data FROM ciphers
WHERE atype==2 and (data->'Type' is not null or data->'type' is not null) and created_at >= '2024-03-06 18:27:26.282451204';[
{
"created_at": "2024-03-06 18:27:26.282451204",
"atype": 2,
"data": "{\"Type\":0}"
},
{
"created_at": "2024-09-07 16:12:21.507640115",
"atype": 2,
"data": "{\"type\":0}"
},
{
"created_at": "2024-09-07 16:49:14.273893165",
"atype": 2,
"data": "{\"type\":0}"
}
] |
Beta Was this translation helpful? Give feedback.
-
|
Yes, the new clients use camelCase instead of PascalCase. Vaultwarden is already adjusted to return all items in camelCase and PascalCase where still needed otherwise. The old clients accept both, while the new only accepts camelCase (in most places), and is case sensitive. This all is already fixed and should be working in the |
Beta Was this translation helpful? Give feedback.
-
|
I had to backup the data and rebuild the docker with latest version, it worked. |
Beta Was this translation helpful? Give feedback.
-
|
I had the same issue. Nothing mentioned here worked. I finally found the issue: i had 3 entries with no name. They were showing in the web-ui as blank row. I went ahead and deleted the entries and the mobile app is working now |
Beta Was this translation helpful? Give feedback.
-
|
i am not sure where they came from. iam not missing any entries and i never imported into my vault. i also do not remember adding these entries. for debugging purposes i created another account and imported my vault into it. there i noticed that the 3 items had the name "---", i lokked in my original vault and the name was null |
Beta Was this translation helpful? Give feedback.
-
|
i still have a encrypted json export which includes these entries. i imported that file to a test account. the entries are completely null. After import the name is set to "--" but no password, url or anything is set. maybe that helps |
Beta Was this translation helpful? Give feedback.
-
|
If you are willing to provide that file, or a snippet of the part that you think is causing the issue, that would be great. |
Beta Was this translation helpful? Give feedback.
-
|
Sadly the original export file from my main vault is encrypted. But i imported the encrypted json into a test account and then exported the vault again as planm json. These are the two issue causing items. They are right at the start of the items array: "items": [
{
"passwordHistory": null,
"revisionDate": "2024-09-19T12:26:10.803Z",
"creationDate": "2024-09-19T12:26:10.803Z",
"deletedDate": null,
"id": "74f8f483-d891-4916-a3cf-085386aa2e03",
"organizationId": null,
"folderId": null,
"type": 1,
"reprompt": 0,
"name": "--",
"notes": null,
"favorite": false,
"login": {
"fido2Credentials": [],
"uris": [],
"username": null,
"password": null,
"totp": null
},
"collectionIds": null
},
{
"passwordHistory": null,
"revisionDate": "2024-09-19T12:26:10.802Z",
"creationDate": "2024-09-19T12:26:10.801Z",
"deletedDate": null,
"id": "e4bd83a1-7567-45e8-b1b7-c4d41f014adc",
"organizationId": null,
"folderId": null,
"type": 1,
"reprompt": 0,
"name": "--",
"notes": null,
"favorite": false,
"login": {
"fido2Credentials": [],
"uris": [],
"username": null,
"password": null,
"totp": null
},
"collectionIds": null
}]Please notice that the name of these items not being null but "--" is because of the importing of the encrypted json. If there is a way i could decrypt the JSON without importing it i could do that and provide the original JSON Snippet Hope I can help |
Beta Was this translation helpful? Give feedback.
-
|
Did we ever determine what the issue was here? |
Beta Was this translation helpful? Give feedback.
-
|
I am getting this same error now after ios updates and I'm pretty sure DNS isn't the culprit as I can stil log into the vault from the web on safari. |
Beta Was this translation helpful? Give feedback.
-
|
From my understanding this could be because at one place in your vault there is a null string which is not supported by the new Bitwarden app. You could do a unencrypted json export of your vault and search for ": null" and ": --" to find these values. Then you could try to remove these entries if not needed or fill them with a valid string and import the file into a new account. Do this until you got no error |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue. Can login in to web but iphone gives error. Exported vault to json. There are no "--" entries and non of the "name" fields are "null" but almost every entry has at least one "null" field. Is it only the name field that can't be "null" or is it any field? |
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: SIGNUPS_ALLOWED, ADMIN_TOKEN
{ "_duo_akey": null, "_enable_duo": false, "_enable_email_2fa": false, "_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": "Bitwarden_RS", "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": true, "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": false, "smtp_from": "", "smtp_from_name": "Bitwarden_RS", "smtp_host": null, "smtp_password": null, "smtp_port": 587, "smtp_security": "starttls", "smtp_ssl": true, "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": null, "yubico_secret_key": null, "yubico_server": null }Vaultwarden Build Version
v1.32.0
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
caddy 2.8.4
Host/Server Operating System
Linux
Operating System Version
No response
Clients
iOS
Client Version
2024.8.1 (1052)
Steps To Reproduce
Open the iOS app.
Expected Result
See a list of vault entries.
Actual Result
"An error has occured"
Logs
No response
Screenshots or Videos
No response
Additional Context
Unfortunately the app doesn't provide any more details, so it might as well be an actual problem of the app. But since I use vaultwarden vs the official server, I don't want to open a bug report with them.
Beta Was this translation helpful? Give feedback.
All reactions