I am not sure if this issue is a bug, a misconfiguration, or a misunderstanding on my part. Let me explain the background.
I self-host the Bitwarden server. Initially, when I only used the master password for authentication, everything worked fine. However, after I added 2FA (Authenticator App), problems started to arise.
I tried read this forum post: Android App "We were unable to process your request. Please try again or contact us"
- Windows Bitwarden App Bypasses 2FA
When I log in to the Windows Bitwarden app using my master password, it bypasses 2FA entirely and takes me straight to the vault. However, when I log in to Bitwarden through Google Chrome, it asks for 2FA, as expected.
I tried the following steps but with no success:
- Deauthorized all sessions via the Bitwarden web interface on Google Chrome.
- Waited for 1 hour before retrying.
The issue persisted. The Windows app still bypasses 2FA and directly accesses the vault. I can create new passwords in the app, and they sync properly to the web interface.
- Browser Extension Issues (Google Chrome)
When I tried to log in via the Bitwarden browser extension, I encountered an error (unfortunately, I can’t remember the exact error code). I tried the following steps:
- Reinstalled the browser extension.
- Deauthorized all sessions via the Bitwarden web interface on Google Chrome and waited for 1 hour.
After these steps, I was able to log in to the browser extension. However, like the Windows app, it no longer asks for 2FA.
- Android App Login Fails
I cannot log in to the Bitwarden Android app. It shows the error message:
“We were unable to process your request. Please try again or contact us.”
I tried:
- Reinstalling the Bitwarden app.
- Deauthorizing all sessions via the Bitwarden web interface and waiting for 1 hour.
Unfortunately, none of these resolved the issue.
- I checked for updates using
bitwarden.sh
commands (updateself
andupdate
) and updated the server. - I ensured that my host OS and its packages are up-to-date.
- I confirmed that all Bitwarden clients (Windows app, browser extension, Android app) are running the latest versions.
Despite these steps, the issues persist.
My network setup is relatively complex:
- From the internet → My router → Main reverse proxy → Bitwarden host → Bitwarden VM’s Nginx server.
I checked the logs for all reverse proxies in the path, but I found no relevant errors.
I also checked the logs inbwdata/logs
, but there are no relevant errors there either. Is there a specific configuration needed to enable detailed logging for login errors?
The Only Hint I Have:
While inspecting the browser console (via F12), I noticed this error:
“Error: WebSocket failed to connect. The connection could not be found on the server, either the endpoint may not be a SignalR endpoint, the connection ID is not present on the server, or there is a proxy blocking WebSockets. If you have multiple servers check that sticky sessions are enabled. at s.onclose [as __zone_symbol__ON_PROPERTYclose] (WebSocketTransport.ts:136:28)”
I will provide more information if needed. Any guidance or suggestions would be greatly appreciated! - Trisorn Thanamok