mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
"This is not a recognized Bitwarden server" on Andriod after resetting app #2179
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 @JeremyKennedy on GitHub (Feb 7, 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.1
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
https://github.com/linuxserver/docker-swag/releases/tag/3.1.0-ls361
Host/Server Operating System
Linux
Operating System Version
No response
Clients
Android
Client Version
2025.1.1
Steps To Reproduce
Expected Result
I am able to log in successfully.
Actual Result
I get the "This is not a recognized Bitwarden server" error.
Logs
Screenshots or Videos
No response
Additional Context
Hey, first off thanks for this app. I've tried many things trying to get this to work:
I looked at #5525 and #5296, there it seems to tend to be reverse proxy issues. I've updated all my configs to the latest. This works on all platforms except Android, so I hesitate to blame the proxy config.
Should I try a fresh Vaultwarden instance? Should I try the official Bitwarden server? Should I try skipping the reverse proxy, and exposing Vaultwarden's port directly (would rather avoid that)?
Here is the primary part of my SWAG/Nginx config, let me know if you want to see the referenced files too.
@JeremyKennedy commented on GitHub (Feb 7, 2025):
I just spun up the "unified beta" bitwarden server, with the exact same proxy config except 8080 instead of 80, and it works perfectly.
@BlackDex commented on GitHub (Feb 7, 2025):
Please try the
testingtagged image which has some more fixes.