mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2025-12-09 17:23:04 +03:00
Bitwarden native mobile clients fail sync with invalid ssh-key entries #287
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 @hegedussz on GitHub.
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Vaultwarden Build Version
1.32.7
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
nginx
Host/Server Operating System
Linux
Operating System Version
Ubuntu 22.04
Clients
iOS
Client Version
2024.12.0 (1740)
Steps To Reproduce
value: ssh-key-vault-item,ssh-agent
Later deleted the variables
Expected Result
The synchronisation was successful
Actual Result
Synchronisation does not work, vault not updated, not loading
Logs
No response
Screenshots or Videos
Additional Context
No response
@BlackDex commented on GitHub:
If there are any invalid ssh-key entries this will happen.
Check your ssh-key entries if delete the invalid items, also from you trash.
@BlackDex commented on GitHub:
The web-vault doesn't support this (yet), so that isn't strange.
@tomitomas commented on GitHub:
yep, saw your previous answer ;)
i was just saying its not only ios, but can also happen with android
from my Phone, on the web version I'm not able to see any of the ssh key, and the trash is also empty ... weird
will check tomorrow if I'm able to see anything from desktop app.
--> for sur I made some test with only the name on an
ssh keyitem, see my previous "issue" ... so there might be some in the trash at least (which I see now empty !)@tomitomas commented on GitHub:
same here on android app --> Version: 2024.12.0 (19597)
everything's OK with the desktop app, from where I've added the ssh keys.
edit : will have a look at #5322, tomorrow !
@BlackDex commented on GitHub:
The mobile clients are more strict.
So it's there is any ssh key which is not valid, this will cause that error.
@BlackDex commented on GitHub:
I have created a fix for this. The only issue is that all the data of the key will be lost if just one of the mandatory fields is missing, as anything other than a valid encrypted string will still break the client. And we can't just replace it with something else.
@Gerardv514 commented on GitHub:
If this is happening on both iOS & android, and is all related to ssh keys I’d suggest changing the title of this issue to reflect that. This helps keeps all previous issues of mobile clients not working separate, and specific to the actual issue.
@BlackDex commented on GitHub:
Start a new discussion, post your Support String (generate it via
/admin/diagnostics), if possible, useadb logcatto see what the error is you get during login/sync.@tomitomas commented on GitHub:
so indeed I had 2
sshe keyitems only with a name in the trash, only viewable on the desktop client appI removed them, and now I'm able to use again the mobile app
@miberecz commented on GitHub:
Let me hijack this thread a little bit.
I face again the issue that my Android Client cannot sync with my VW server. I tried to log-out and in again, and now I cannot even authenticate anymore against the server. Web client works, browser extensions, dekstop client also.
But I do not have any ssh keys stored, didnt even know thats possible until now.
Is there any other offending entry that I should remove/modify?
1.32.7 server image
2024.12.0 Android version
Couple weeks/month ago there were a similar occasion where it was solved by updating to latest server/client but that does not help now.
@mannp commented on GitHub:
Thanks :) I've deleted the ssh keys from main and bin and still get the same error above '(unable to process your request)'
Is there potentially another workaround at all while there is another official release of vaultwarden?
Thanks
@BlackDex commented on GitHub:
I meant the testing tagged version of Vaultwarden.
But if you are using Nix, then no version there will fix your issue.
@mannp commented on GitHub:
Okay will wait for the next release 👍 thanks
@BlackDex commented on GitHub:
Use testing to see if that helps.
@mannp commented on GitHub:
I've tried the beta bitwarden client if that is what you mean by testing, but that made no difference, neither the pre release version they released today either.
I use NixOS module, which pulls off the official vaultwarden releases.