mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
Websocket connection is not working on iOS or Chrome Extension #2208
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 @SuberSeb on GitHub (Mar 1, 2025).
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, ADMIN_TOKEN
Config:
Vaultwarden Build Version
1.33.2
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
Nginx Proxy Manager
Host/Server Operating System
Linux
Operating System Version
Unraid 7.0.1
Clients
iOS, Browser Extension
Client Version
iOS - 2025.1.3 (1884); Chrome - 2025.2.1
Steps To Reproduce
Expected Result
Every change is loaded instantly without manual synchronize.
Actual Result
I need to manual synchronize vault every time I made any update.
Logs
Screenshots or Videos
No response
Additional Context
For browsers websockets seems to be working but iOS and Chrome extension doesn't use websockets for some reason.
@BlackDex commented on GitHub (Mar 1, 2025):
This has nothing to do with websocket connections. Mobile devices do not use those.
Check the logs if the push notificaties work towards Bitwarden.
Also, you might need to de-authorize all logins. Full logout on your mobile, uninstall, reboot, install again, and login again to have it working. Sometimes the device id is not correctly send by the mobile devices which is needed to identify the device for the push services from either Google or Apple.
It works just fine for me on both Android and iOS.
@BlackDex commented on GitHub (Mar 1, 2025):
Regarding Chrome, you might want to check the developer console for the extension it self to see what might be wrong there.
It does look like websocket connections do work according to the check though. If it works on the web-vault, then it should work on all other clients which use websocket connections.
@BlackDex commented on GitHub (Mar 1, 2025):
Going to close this as this is not a bug in Vaultwarden which can be fixed.
If you still need more information, please open a Discussion in the QA section as I'm currently not able to convert this to a discussion due to a bug/issue with GitHub.