mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-05-24 17:12:43 -05:00
Android Login fails at 2FA #2209
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 @matt-mai on GitHub (Mar 3, 2025).
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: DOMAIN, SIGNUPS_ALLOWED
Config:
Vaultwarden Build Version
1.33.2
Deployment method
Official Container Image
Custom deployment method
Vaultwarden is running in Kubernetes using ghcr.io/dani-garcia/vaultwarden:1.33.2 image.
With ingress-nginx as ingress controller.
Reverse Proxy
nginx 1.25.5
Host/Server Operating System
Linux
Operating System Version
No response
Clients
Android
Client Version
2025.2.2 (19740)
Steps To Reproduce
Expected Result
App should request the second factor after password was accepted
Actual Result
App returns an error instead:
"This is not a recognized Bitwarden server. You may need to check with your provider or update your server"
Logs
Screenshots or Videos
No response
Additional Context
The 2 FA Token is generated and I get the E-Mail containing the token, but the app does not even request it, it just gives me the error message.
@BlackDex commented on GitHub (Mar 3, 2025):
Try to fully logout, clear data, uninstall, reinstall and try again.
@matt-mai commented on GitHub (Mar 3, 2025):
I did. I originally noticed this on a completely new android install and was able to reproduce on an older device with an existing app install.
@BlackDex commented on GitHub (Mar 3, 2025):
Then it might be somehow your reverse proxy changes the response maybe?
Try to download the
devAndroid client here https://github.com/bitwarden/android/actions/runs/13569085049And check the
adb logcatfor output.@matt-mai commented on GitHub (Mar 3, 2025):
I redacted the self hosted url and login data, but these seem to be the relevant logs.
It looks like it's trying to connect to
https://api.bitwarden.com/connect/tokenfor some reason?It also seems as if 2FA isn't actually the problem. I created a new test account without 2FA and it still fails at the same step.
@matt-mai commented on GitHub (Mar 3, 2025):
It seems there's an issue with a network policy in Kubernetes. Login works if i remove them all.
I can fix it myself from here, thanks for your help and sorry for the bother :)
Edit: Just in case someone runs into the same issue in the future:
I had egress traffic for the vaultwarden server limited to ports 80 and 443.
I don't actually see any other ports used, but as soon as i remove that limit, the login works.