mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #5296] iOS app "An error has occurred" not a recognized Bitwarden server #2118
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#2118
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @jacksonhull on GitHub (Dec 14, 2024).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/5296
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, ADMIN_TOKEN
Failed HTTP Checks:
Config:
Vaultwarden Build Version
v1.32.6
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
Traefik 3.2.2
Host/Server Operating System
Linux
Operating System Version
iOS
Clients
iOS
Client Version
2024.12.0 (1740)
Steps To Reproduce
In Bitwarden app:
Expected Result
Log in and see vault.
Actual Result
Get error message: "An error has occurred. This is not a recognized Bitwarden server. You may need to check with your provider or update your server."
Logs
Screenshots or Videos
Additional Context
I have another iOS installation that works perfectly, but it is using v2024.11.0 (1680). This is a new iPhone. I have a theory that because it's a new os install, it has installed an updated version of the Bitwarden iOS app (v2024.12.0 (1740)).
@BlackDex commented on GitHub (Dec 14, 2024):
What are the logs of Vaultwarden and your reverse proxy?
What happens with a new clean account?
@jacksonhull commented on GitHub (Dec 14, 2024):
VW logs show nothing suspect:
Traefik doesn't log anything INFO or higher.
A new account and other existing accounts have the same issue.
I should also mention that there is no issue logging into the web app.
@YWxleGlz commented on GitHub (Dec 14, 2024):
Bitwarden seems to want to detect vaultwarden servers...
github.com/bitwarden/ios@361cc87a56/BitwardenShared/Core/Platform/Models/Domain/ServerConfig.swift (L62)github.com/bitwarden/ios@361cc87a56/BitwardenShared/UI/Auth/Login/LoginProcessorTests.swift (L156)EDIT : I'm not able to reproduce the issue on IOS 2024.12.0 (1740) & Web 2024.6.2c
@jacksonhull commented on GitHub (Dec 14, 2024):
That is horrible if it’s intended to disable if the server is VW.
Thanks for trying to recreate. Just confirming you tried deleting app data and then connecting with a fresh install?
@YWxleGlz commented on GitHub (Dec 14, 2024):
Uninstall/install mobile application + install new vaultwarden environment.
Can you try to make a temporary account on a public instance to see if it's related to your server configuration?
(For example, on
redacted)@jacksonhull commented on GitHub (Dec 14, 2024):
I did uninstall/install iOS app before.
The app works on a public instance.
I haven’t taken the step yet to rebuild VW. It’s odd there is just no log in VW to help troubleshoot further. Almost like the request is rejected before it’s routed
@BlackDex commented on GitHub (Dec 14, 2024):
I would not recommend using any random public Vaultwarden instance.
Check what happens if you try to access the web-vault via Safari, does that work?
Do you have the sneaky proxy feature enabled on iOS?
@BlackDex commented on GitHub (Dec 14, 2024):
Also, did you filled in only the first entry of the self-hosted settings or all?
@BlackDex commented on GitHub (Dec 14, 2024):
I just tested it on an older iOS device i have, and it works just fine for me. I'm using a Valid Let's encrypt cert btw.
@BlackDex commented on GitHub (Dec 14, 2024):
That detection is only done to modify the error message to emphasize it's a third party server and not an official Bitwarden.
@BlackDex commented on GitHub (Dec 15, 2024):
If you do not see any log attempt even with debug logging enabled, then it's one of these items.
Check all the steps in between for logs and errors.
@jacksonhull commented on GitHub (Dec 15, 2024):
Thank you. I believe I discovered the issue.
I had some deny/allow rules that allowed the app access to VW through the proxy. Specifically:
I believe that the latest version of the app must be making a call to another endpoint that was being blocked. Allowing all resolved the issue, and it also explains why neither Traefik or VW were not logging any issues.
I wasn't able to determine what additional endpoint is being called.