mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
iOS App - an error has occurred #2060
Reference in New Issue
Block a user
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 @theo-rettisch on GitHub (Oct 10, 2024).
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden: ADMIN_TOKEN
Vaultwarden Build Version
v1.32.1
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
traefik:v2.9
Host/Server Operating System
Linux
Operating System Version
Ubuntu 22.04.5 LTS
Clients
iOS
Client Version
2024.9.2 (1106)
Steps To Reproduce
Expected Result
Entries are successfully synchronized
Actual Result
The error message “An error has occurred” appears
Logs
Screenshots or Videos
(message says: An error occured)
Additional Context
I have tried the following, but nothing has helped
Login via web and desktop app works fine
@BlackDex commented on GitHub (Oct 10, 2024):
several other reports regarding this already. But as of yet, nobody provided any useful details to tackle this.
There are also reports of this at Bitwarden , though, unclear to me if those are only with Vaultwarden self-hosted or also Bitwarden.
https://github.com/bitwarden/ios/issues/1025
https://github.com/bitwarden/ios/issues/891
Until someone is able to figure out what specific item is causing this, it is going to be very very difficult to track this down.
All other clients seem to work just fine, including the Native Android.
@bricej13 commented on GitHub (Oct 10, 2024):
I was able to solve the problem by updating my Vaultwarden to the latest (1.32.1)
@BlackDex commented on GitHub (Oct 10, 2024):
But the TS is already on v1.32.1
@BlackDex commented on GitHub (Oct 10, 2024):
Also, i tested several account's i have, and no issue on the iOS device i have using the exact same client version
2024.9.2 (1106)And i know several users on my system have an iOS device, and they all have a working app.
@cplaetzinger commented on GitHub (Oct 10, 2024):
I've the same issue. Any idea which information could be helpful to debug this issue?
When I try to login via the iOs app the server only logs the following
@BlackDex commented on GitHub (Oct 10, 2024):
Are you using Vaultwarden 1.32.1?
@cplaetzinger commented on GitHub (Oct 10, 2024):
I thought that I'm on 1.32.1 but it seems that
docker-compose pulldid not pull the latest version. After configuring 1.32.1 explicitly it worked. Thanks!@W1BTR commented on GitHub (Oct 11, 2024):
I have the same issue, we use yunohost, and I cant update it yet as it requires a yunohost version that hasnt been released yet. Guess it's time to move to docker for it, lol
@Gerardv514 commented on GitHub (Oct 11, 2024):
According to this comment, could it be some emoji in a vault item jacking it up?
@Philambdo commented on GitHub (Oct 11, 2024):
I am using vaultwarden on nixos with the latest available version 1.32.1:
From the Diagnostic Page:
Recently i upgraded my iphone to ios 18 and now i get the same issue.
Additionally i have sometimes the problem that i can't save within the firefox plugin or the dedicated app. (I'm not sure if this is related or some other websocket issue?)
Saving in the Web-App is working fine.
I tried a little bit of ngrep between haproxy and the vaultwarden, but all i got is the following response with return code 200:
@BlackDex commented on GitHub (Oct 11, 2024):
@Philambdo
Websocket connections have nothing to do with saving an item (unless you modified it on client 1, and then try to modify it via client 2 which still has the old data).
It might be an iOS18 issue then?
Are there users here which still are on iOS17 or lower?
Because the phone i have for testing is an older model and is stuck on iOS 15 even.
@Philambdo commented on GitHub (Oct 11, 2024):
It might not be the iOS Version after all (or at least not alone).
I Just fetched the ipad with iOS 17.7 and Bitwarden App 2024.09.02 and its showing the same error message.
I also used other accounts on my instance to rule out a broken password - with no success.
I am not sure how to debug any further.
If there is any information i can provide just give me a heads up.
@Philambdo commented on GitHub (Oct 11, 2024):
Another thing. Just to be sure. The version that should work with current Bitwarden App is 1.32.1 and not latest?
Because nixos is using the following Checkout from Git:
https://hydra.nixos.org/build/274609331#tabs-buildinputs
@BlackDex commented on GitHub (Oct 11, 2024):
1.32.1andlatestshould be the same regarding the container images.I do not know where and how nixos downloads the source of this project. So i can't answer that question.
@Gerardv514 commented on GitHub (Oct 11, 2024):
I’m on iOS 18 running BW app 2024.9.2 and latest Vaultwarden and I am not seeing an issue. I also have an organization setup with two users and a few test accounts.
Its got to be an item in the vault
@theo-rettisch commented on GitHub (Oct 11, 2024):
I have no entries with emojis.
I checked if my app version (2024.9.2 (1106)) works with a the SaaS version - it does.
Could attached files be the problem?
@BlackDex commented on GitHub (Oct 11, 2024):
Files are probably not an issue. Those are only references to files, nothing more.
My best guess would be the new key per cipher stuff.
But I'm also not able to trigger any issue when i have entries with that.
To troubleshoot it you should create a backup first, let nobody else access the server anymore and then delete each cipher one-by-one from the vault and trash, and check if you can sync again with the mobile client.
@theo-rettisch commented on GitHub (Oct 11, 2024):
Hm... yeah. I will try it tomorrow. I am curious what the problem is.
@Doomsdayrs commented on GitHub (Oct 12, 2024):
This is not limited to IOS, Experienced this on Android today too.
@Gerardv514 commented on GitHub (Oct 12, 2024):
Can you share anything informative?
@BlackDex commented on GitHub (Oct 12, 2024):
@Doomsdayrs and you are 101% sure you are running the latest 1.32.1 version of Vaultwarden?
@BlackDex commented on GitHub (Oct 12, 2024):
@theo-rettisch , that would be great. Any information might be useful.
@Doomsdayrs commented on GitHub (Oct 12, 2024):
Just double checked, and for some reason my pod didn't update
I thought it was, but it seems it wasn't.
2024.6.2 makes it work for me
@Gerardv514 commented on GitHub (Oct 12, 2024):
🙄
@theo-rettisch commented on GitHub (Oct 12, 2024):
I found the solution - at least for me.
After I deleted every entry from the trash, the iOS client was able to synchronize successfully.
edit: i will try to find out which of the entries caused the problem
@theo-rettisch commented on GitHub (Oct 12, 2024):
Ok. I had an entry in my trash with custom fields but for these fields the field type (hidden / password, text, boolean) were missing. Both of them were text fields.
After i deleted the faulty fields the iOS client synchronized successfully.
Unfortunately I don't know which version I updated from but it was definitely < 1.31
@BlackDex commented on GitHub (Oct 12, 2024):
@theo-rettisch Do you have the original entry from the database?
That would be supper!!
@theo-rettisch commented on GitHub (Oct 12, 2024):
@BlackDex Here you go.
(i couldn't resist to replace the encrypted data with text...)
@miberecz commented on GitHub (Oct 12, 2024):
I had the same issue. Solved with updating both the iOS app and the container running VW
App version 2024.9.2
VW version 1.32.1
@Philambdo commented on GitHub (Oct 12, 2024):
Hello all,
so as i had no further way of debugging and no idea how to proceed i did a vanilla install on a different vm via podman with the lastest version, with an empty database and all.
=> Login works
So i tried to copy over the database stuff to the container
=> Login works
So it boils down to nixos having an issue. I removed everything from the server and did a "fresh" install (which is nixos doing during an upgrade all the time anyway) and guess what:
=> Login works
So now i have no clue what part of the old install wasn't correctly updated or misconfigured by me ( i had still some websocket config left in the environment file pointing to port 3012 which was replaced by rocket in 1.31 i guess).
I'm sorry for the troubles but at least another thumbs up for version 1.32.1 in combination with ios 18 and latest bitwarden app from me.
Keep up the good work.
@mleisi commented on GitHub (Oct 12, 2024):
I encountered the same error using Bitwarden mobile client
2024.9.2 (1106)on iOS 17.6.1 against vaultwarden 1.30.5 running in a docker container on a Synology.Web access and Bitwarden desktop client
2024.6.3 (25879)on MacOS 14.5 were not affected.Upgrading to vaultwarden 1.32.1 fixed the issue with the Bitwarden mobile client.
@Gerardv514 commented on GitHub (Oct 12, 2024):
This is a different issue than here that yes was fixed. It looks like there maybe still one more instance out here causing issues, and this is known because they have updated to 1.32.1 and still have an issue. So for anyone having the same issue but on an old version, that then upgraded, and is now resolved that is NOT the same issue as what some are still reporting. As mentioned the last bit of what some are reporting are already on 1.32.1 and are having the issue.
Anyone further saying that have the same issue, needs to be already on 1.32.1 and if not you need to update first because your specific issue may already be handled and handled in other threads.
This thread is for anyone already on 1.32.1 and experiencing an issue.
@BlackDex commented on GitHub (Oct 13, 2024):
@theo-rettisch, it looks like the item you posted is not the same item you which was in your trash i think.
As it has no
deleted_atdate. So it probably is either the result of after you updated it, or not the same item.I need to know how it looked like when it was causing issues, before you fixed it.
@theo-rettisch commented on GitHub (Oct 13, 2024):
@BlackDex, it seems it does not matter if it is deleted or not. After i restored the entry the client could still not synchronize. I removed the two faulty custom fields and then it worked.
Here's the same entry in deleted-state:
@BlackDex commented on GitHub (Oct 13, 2024):
Thanks @theo-rettisch, after an other good look, i think i have found the issue.
The
Typevalues are strings, while all other clients work fine with this, the iOS does not.@theo-rettisch commented on GitHub (Oct 13, 2024):
The specific item were created by the api.
I will validate tomorrow some more entries in another installation which were created by the api too.
Maybe this is the problem.
@BlackDex commented on GitHub (Oct 13, 2024):
Well, i think we should do some more type casting/converting on what is incoming. This does mean we need to do more processing during the input of ciphers or other API calls especially since the new clients they are more strict regarding the types of those fields.
@BlackDex commented on GitHub (Oct 13, 2024):
Ok, the just built
testingtagged container images should work now with the faulty items. And this should hopefully resolve all issues with iOS sync.@theo-rettisch commented on GitHub (Oct 15, 2024):
Yeah, this works! Thank you!
@StefanGruell commented on GitHub (Oct 19, 2024):
Hi, i am running the
testingtagged container but i am still running into this error.Which information do you need?
I switched from my iPhone 8 to an iPhone 16 Pro. Both have the version 2924.9.2. While on the old phone it still works the new one shows me the error.
Any help is kindly appreciated!
@BlackDex commented on GitHub (Oct 19, 2024):
First, i think you probably mend to say
v2024.9.2else you are living in a very far future, and then I'm glad to see Vaultwarden and Bitwarden still exits 🤣Maybe what the exact error is the client is showing. If there are any logs in Vaultwarden or your reverse proxy during these attempts.
Be sure to validate the domain you configured in the client, one small typo is made very quickly.
Also, check if you are able to access your web-vault via the Safari Browser and if there are no SSL/Certificate issues reported just to be sure.
@StefanGruell commented on GitHub (Oct 19, 2024):
Haha ye ofc i meant v2024.9.2 😄
So the error in the client i am getting is
It is a selfhosted without any outside connection. I can connect via the browser and log in. The server logs can be seen here when trying to connect.
@BlackDex commented on GitHub (Oct 19, 2024):
Looks like a TLS/SSL Issue to me.
Either you have not configured Vaultwarden correctly for the used certificate which i think is probably the issue, since you seem to try connect via a local IP address. And i doubt you have a certificate created for that specific IP address.
If you are using a self-signed certificate, it should then still have that specific IP in it's
Subject Alt Names.But this is totally out of scope of this specific issue.
Either do not use SSL if only running via local IP's and see if that solves it, if so, then fix a proper SSL Certificate with a domain linked to it. Or it might be an issue that Rocket somehow is not able to correctly communicate with the new iOS18, which i doubt, but could be of course. In that case, try to add a well known reverse proxy in-front of Vaultwarden and see if that solves your issues.
Also, i have no clue on how to allow/add/trust self-signed certificates on an iOS device, so i would suggest to search for that somewhere else.
@StefanGruell commented on GitHub (Oct 19, 2024):
Well after some investigation i think i found the issue. Yes I use a self-signed certificate with that exact IP but everything is as far as I can see set up correctly.
I found out that in the iOS 18 settings i am not able to trust my own certificate even though its installed. As seen in that or that post i am sadly not the only one.
I guess i gotta wait for an iOS update to fix it.
Still thanks for the help!
@BlackDex commented on GitHub (Oct 19, 2024):
@StefanGruell looking at https://support.apple.com/en-us/102390 I'm not sure which cert you installed, but i think you need both the CA Cert and Vaultwarden Cert to be installed/trusted.
Looking a bit more, it seems a lot if users have this, and the Apple fora's are also filled with issues.
@StefanGruell commented on GitHub (Oct 19, 2024):
@BlackDex If understand correctly (I did it on my old iPhone and it did work) I have to install the CA Cert, then trust it and after that trust the Vaultwarden Cert.
Yeah I think Apple did a bit of an oopsie there.
@shelterx commented on GitHub (Nov 4, 2024):
Fyi, I had this error or a few weeks, I updated vaultwarden to latest version. Did not help.
Only thing that helped was to start over, removing the vaultwarden docker, make a backup of the vault in json format and removing the data folder.
@BlackDex commented on GitHub (Nov 4, 2024):
And you probably do not have a backup maybe? So that we could try and compare solve this without the need of exporting and starting all over again?
@shelterx commented on GitHub (Nov 4, 2024):
Not sure where to look, I dumped the databases and ran a diff on them,
the only noticeable change was that the new one contained these changes:
@BlackDex commented on GitHub (Nov 4, 2024):
That tells me that you previous update didn't succeeded fully, and you were probably not running the latest version of Vaultwarden when you deleted everything.
My guess would be the container was still running an older version of Vaultwarden which is known to have issues with iOS clients. And the latest version of Vaultwarden works, which has those changes in the database, and are totally unrelated btw.
@shelterx commented on GitHub (Nov 4, 2024):
Maybe something happened during the update then, never had issues in the past tho', yes, vaultwarden has stopped working before but then I just had to update it and it started working again.
@BlackDex commented on GitHub (Nov 4, 2024):
If something happened during the update, then you would have seen a log message noting that.
Or, Vaultwarden would have stopped running all together.
For example, if a database update didn't worked, Vaultwarden will stop and not start anymore since it is unable to complete the database migration.
@shelterx commented on GitHub (Nov 4, 2024):
Docker pull said it was the latest version, the web interface worked fine. But anyway, I can't check that now since I don't have a backup of the previous state.
@BlackDex commented on GitHub (Nov 4, 2024):
If you forgot to do a
docker compose up -dor forgot to delete and recreate the container after the pull, it wasn't updated. Only pulling and restarting will not update the container. Which is a mistake which happens a lot.@xHyperElectric commented on GitHub (Dec 13, 2024):
Any solution for this? I'm on the latest vaultwarden server and latest ios app
@BlackDex commented on GitHub (Dec 13, 2024):
@xHyperElectric and what version is latest according to your installed version?
What does the
/admin/diagnosticsreport?@xHyperElectric commented on GitHub (Dec 13, 2024):
1.32.6
@BlackDex commented on GitHub (Dec 13, 2024):
And you tried to fully logout, clear all data of the app, re-install clean and test it again?
If you have an Android phone, could you try that too and see if that works or not?
@xHyperElectric commented on GitHub (Dec 13, 2024):
I freshly installed vaultwarden two days ago for the first time ever. And I can try an android later. I tried it on two different iOS Phones last night and they both got the same error
@BlackDex commented on GitHub (Dec 13, 2024):
Wait, it is a clean Vault? Does it have any entries?
If so, i would suggest to open a new discussion and provide details on your setup there instead of abusing this already closed issue.
@syafi-dev commented on GitHub (Jul 12, 2025):
It happen the same to me and it has been more than two weeks .
"An error has occurred" on IOS app. No issue on web vault.
IOS version : 18.5
Bitwarden App version : 2025.6.0
Vaultwarden version
Server : 1.34.1
Web : 2025.5.0
I tried to reinstall the app and clear all records in the trash but still the same.
@serafearz commented on GitHub (Sep 10, 2025):
Anyone found a solution, fresh installation here, unable to login using iOS 26 & latest bitwarden iOS app.
@RWayne93 commented on GitHub (Oct 18, 2025):
@serafearz did you ever find a solution to this. Everything works fine on my spare iPhone on iOS 18 but on iOS 26 I get this issue on the latest client and latest vaultwarden docker image.
Edit: Posting another solution here for anybody on iOS 26 experiencing this.
I self host vaultwarden behind caddy reverse proxy. On previous iOS versions bitwarden client wasn't so picky about the ssl certificate but on iOS 26 you will need to install your rootCA if you are using a self signed certificate and then trust that cert in Settings > about > Trust Certificate settings.
This makes it work as normal again for me.