github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-22 20:41:29 -05:00
Code Issues 144 Packages Projects Releases 118 Wiki Activity

v2025.2.0 Won't Connect With Self-Hosted Instance #2199

New Issue
Closed
opened 2025-11-26 23:11:32 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-26 23:11:32 -06:00
Owner
Copy Link

Originally created by @ewhac on GitHub (Mar 18, 2025).

Steps To Reproduce

  1. Force-close app. Clear app's cache and local storage.
  2. Launch Bitwarden.
  3. For "Logging in on," select self-hosted. Enter URL of self-hosted server. Click Save.
  4. Enter email address; click Continue.
  5. Enter master password; click on Log in with Master Password.

Expected Result

Connect to self-hosted server and display/browse password entries.

Actual Result

A dialog pops up reading:

An error has occurred.

We were unable to process your request. Please try again or contact us.

Absolutely no details are available concerning the nature of the purported error. Server logs show nothing unusual.

Screenshots or Videos

No response

Additional Context

Server is Vaultwarden 1.30.5.

Server TLS certificate is current. Password verified as correct. Entering an incorrect password yields the same dialog.

Previous version of the Android app worked fine. v2025.2.0 of the browser plugin (Firefox) also works fine.

Build Version

2025.2.0

What server are you connecting to?

Self-host

Self-host Server Version

Vaultwarden 1.30.5

Environment Details

  • Device: Pixel 6 Pro
  • OS: Android 15

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
Originally created by @ewhac on GitHub (Mar 18, 2025). ### Steps To Reproduce 1. Force-close app. Clear app's cache and local storage. 2. Launch Bitwarden. 3. For "Logging in on," select self-hosted. Enter URL of self-hosted server. Click Save. 4. Enter email address; click Continue. 5. Enter master password; click on Log in with Master Password. ### Expected Result Connect to self-hosted server and display/browse password entries. ### Actual Result A dialog pops up reading: > ### An error has occurred. ### > > We were unable to process your request. Please try again or contact us. Absolutely no details are available concerning the nature of the purported error. Server logs show nothing unusual. ### Screenshots or Videos _No response_ ### Additional Context Server is Vaultwarden 1.30.5. Server TLS certificate is current. Password verified as correct. Entering an incorrect password yields the same dialog. Previous version of the Android app worked fine. v2025.2.0 of the browser plugin (Firefox) also works fine. ### Build Version 2025.2.0 ### What server are you connecting to? Self-host ### Self-host Server Version Vaultwarden 1.30.5 ### Environment Details - Device: Pixel 6 Pro - OS: Android 15 ### Issue Tracking Info - [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
GiteaMirror added the app:password-managerbug labels 2025-11-26 23:11:32 -06:00
GiteaMirror commented 2025-11-26 23:11:32 -06:00
Author
Owner
Copy Link

@S-Kakar commented on GitHub (Mar 18, 2025):

Thank you for your report! We've added this to our internal board for review.
ID: PM-19318

@S-Kakar commented on GitHub (Mar 18, 2025): Thank you for your report! We've added this to our internal board for review. ID: PM-19318
GiteaMirror commented 2025-11-26 23:11:33 -06:00
Author
Owner
Copy Link

@BBGhub commented on GitHub (Mar 18, 2025):

Hi There,

It is important to note that Vaultwarden is not associated with Bitwarden. Vaultwarden is a re-writing of the Bitwarden server code in Rust (n.b. Vaultwarden is NOT a fork of Bitwarden), that is not contributed to nor supported by the Bitwarden team or organization. The security audits granted to Bitwarden do not apply to Vaultwarden, and the Bitwarden support team is not able to respond to questions regarding Vaultwarden.

Support options for Vaultwarden are found here:

https://github.com/dani-garcia/vaultwarden?tab=readme-ov-file#get-in-touch

Bitwarden also offers a self-hosted option, with multiple deployment options, including for air-gapped deployments. You can find information on Bitwarden’s deployment options here:

https://bitwarden.com/help/install-on-premise-linux/

https://bitwarden.com/help/install-and-deploy-offline/

@BBGhub commented on GitHub (Mar 18, 2025): Hi There, It is important to note that Vaultwarden is not associated with Bitwarden. Vaultwarden is a re-writing of the Bitwarden server code in Rust (n.b. Vaultwarden is NOT a fork of Bitwarden), that is not contributed to nor supported by the Bitwarden team or organization. The security audits granted to Bitwarden do not apply to Vaultwarden, and the Bitwarden support team is not able to respond to questions regarding Vaultwarden. Support options for Vaultwarden are found here: https://github.com/dani-garcia/vaultwarden?tab=readme-ov-file#get-in-touch Bitwarden also offers a self-hosted option, with multiple deployment options, including for air-gapped deployments. You can find information on Bitwarden’s deployment options here: https://bitwarden.com/help/install-on-premise-linux/ https://bitwarden.com/help/install-and-deploy-offline/
GiteaMirror commented 2025-11-26 23:11:33 -06:00
Author
Owner
Copy Link

@ewhac commented on GitHub (Mar 18, 2025):

Let the record show that Bitwarden regards the app displaying, "An error has occurred," with no other diagnostic info, as acceptable behavior.

@ewhac commented on GitHub (Mar 18, 2025): Let the record show that Bitwarden regards the app displaying, "An error has occurred," with no other diagnostic info, as *acceptable behavior.*
GiteaMirror commented 2025-11-26 23:11:33 -06:00
Author
Owner
Copy Link

@BBGhub commented on GitHub (Mar 18, 2025):

While we expect most client functionality to work with non-official servers, such as Vaultwarden, Bitwarden cannot guarantee that official clients will work perfectly with non-official servers. If you're using a non-official server, we recommend that you keep it as up-to-date as possible to take advantage of compatibility updates written by its maintainers. Bitwarden Customer Support may be limited in their ability to assist you with client issues if you're using a non-official server.

For example, Vaultwarden introduced support for native mobile apps in version 1.31.0. If you’re using native mobile apps and a version of VaultWarden prior to 1.31.0, you will receive an error and should upgrade your server.

@BBGhub commented on GitHub (Mar 18, 2025): While we expect most client functionality to work with non-official servers, such as Vaultwarden, Bitwarden cannot guarantee that official clients will work perfectly with non-official servers. If you're using a non-official server, we recommend that you keep it as up-to-date as possible to take advantage of compatibility updates written by its maintainers. Bitwarden Customer Support may be limited in their ability to assist you with client issues if you're using a non-official server. For example, Vaultwarden introduced support for native mobile apps in version 1.31.0. If you’re using native mobile apps and a version of VaultWarden prior to 1.31.0, you will receive an error and should upgrade your server.
GiteaMirror commented 2025-11-26 23:11:33 -06:00
Author
Owner
Copy Link

@ewhac commented on GitHub (Mar 18, 2025):

I was running Vaultwarden 1.28, against which the previous mobile client worked fine. Then the phone updated the client to 2025.2.0, and then it didn't work. When one tries to diagnose a breakage, one first looks at the thing(s) that changed most recently -- in this case, the client software.

Upgrading Vaultwarden from 1.28 to 1.30.5 (what pkg upgrade initially offered) didn't help. As it turns out, upgrading to 1.32.7 has fixed the issue.

I'm not trying to be difficult or contentious or entitled. I have no expectation that you will provide support for Vaultwarden -- I'm fully aware that choice means I'm On My Own here. What I do expect, however, is access to diagnostics more detailed than, "An error has occurred," especially when the server logs look fine. (Even a hint as small as, "Unrecognized data format" would have steered me toward a server issue.)

Nevertheless, thank you for your thoughtful, detailed replies.

@ewhac commented on GitHub (Mar 18, 2025): I was running Vaultwarden 1.28, against which the previous mobile client worked fine. Then the phone updated the client to 2025.2.0, and then it didn't work. When one tries to diagnose a breakage, one first looks at the thing(s) that changed most recently -- in this case, the client software. Upgrading Vaultwarden from 1.28 to 1.30.5 (what `pkg upgrade` initially offered) didn't help. As it turns out, upgrading to 1.32.7 has fixed the issue. I'm not trying to be difficult or contentious or entitled. I have no expectation that you will provide support for Vaultwarden -- I'm fully aware that choice means I'm On My Own here. What I *do* expect, however, is access to diagnostics more detailed than, "An error has occurred," especially when the server logs look fine. (Even a hint as small as, "Unrecognized data format" would have steered me toward a server issue.) Nevertheless, thank you for your thoughtful, detailed replies.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#2199
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?