github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-11 10:54:26 -05:00
Code Issues 1.1k Packages Projects Releases 124 Wiki Activity

[GH-ISSUE #904] Cannot sync to selfhosted instance on Android 10 #37976

New Issue
Closed
opened 2026-04-23 15:46:40 -05:00 by GiteaMirror · 11 comments
GiteaMirror commented 2026-04-23 15:46:40 -05:00
Owner
Copy Link

Originally created by @rainx0r on GitHub (May 16, 2020).
Original GitHub issue: https://github.com/bitwarden/android/issues/904

Apologies if this should be posted under the "server" repository instead but every other client works fine with my setup.

Describe the Bug

I have a self-hosted instance running at ports 8393 for HTTP and 8394 for HTTPS, behind an nginx reverse proxy routing to port 8393. SSL is configured at reverse proxy level. I can access everything and sync properly fine from browser add-ons and the desktop client, but not the mobile client on Android 10.

The app manages to log in to my instance but whenever I try to sync I get a toast with "Syncing Failed".

Steps To Reproduce

  1. Open App.
  2. Log in to self-hosted instance.
  3. Click on the context menu on top right.
  4. Click on "Sync".

Expected Result

My vault entries appearing on the mobile app.

Actual Result

A toast displaying "Syncing failed"

Environment

  • Device: OnePlus 6
  • Operating system: Android 10.3.2
  • Build Version (go to "Settings" → "About" in the app): 2.3.1 (2257)
  • Is this a Beta release? N

Additional Context

The instance I am trying to connect to is self-hosted and is behind a reverse proxy so I can run it alongside other servers on my machine and not have it bind to 80 / 443. I also installed the cert I have on the reverse proxy manually to the android device to no avail. It also seems like I can connect fine to the vault using the phone's browser, it's just the app not working.

Originally created by @rainx0r on GitHub (May 16, 2020). Original GitHub issue: https://github.com/bitwarden/android/issues/904 <!-- Comment: Please do not submit feature requests. The [Community Forums][1] has a section for submitting, voting for, and discussing product feature requests. [1]: https://community.bitwarden.com --> Apologies if this should be posted under the "server" repository instead but every other client works fine with my setup. ## Describe the Bug <!-- Comment: A clear and concise description of what the bug is. --> I have a self-hosted instance running at ports 8393 for HTTP and 8394 for HTTPS, behind an nginx reverse proxy routing to port 8393. SSL is configured at reverse proxy level. I can access everything and sync properly fine from browser add-ons and the desktop client, but not the mobile client on Android 10. The app manages to log in to my instance but whenever I try to sync I get a toast with "Syncing Failed". ## Steps To Reproduce <!-- Comment: How can we reproduce the behavior: --> 1. Open App. 2. Log in to self-hosted instance. 3. Click on the context menu on top right. 4. Click on "Sync". ## Expected Result <!-- Comment: A clear and concise description of what you expected to happen. --> My vault entries appearing on the mobile app. ## Actual Result <!-- Comment: A clear and concise description of what is happening. --> A toast displaying "Syncing failed" ## Environment - Device: OnePlus 6 - Operating system: Android 10.3.2 - Build Version (go to "Settings" → "About" in the app): 2.3.1 (2257) - Is this a Beta release? N ## Additional Context <!-- Comment: Add any other context about the problem here. --> The instance I am trying to connect to is self-hosted and is behind a reverse proxy so I can run it alongside other servers on my machine and not have it bind to 80 / 443. I also installed the cert I have on the reverse proxy manually to the android device to no avail. It also seems like I can connect fine to the vault using the phone's browser, it's just the app not working.
GiteaMirror commented 2026-04-23 15:46:41 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (May 18, 2020):

Check your server's SSL config here: https://www.digicert.com/help/

Any issues?

<!-- gh-comment-id:630294350 --> @kspearrin commented on GitHub (May 18, 2020): Check your server's SSL config here: https://www.digicert.com/help/ Any issues?
GiteaMirror commented 2026-04-23 15:46:41 -05:00
Author
Owner
Copy Link

@rainx0r commented on GitHub (May 18, 2020):

Nope, all green.

<!-- gh-comment-id:630474778 --> @rainx0r commented on GitHub (May 18, 2020): Nope, all green.
GiteaMirror commented 2026-04-23 15:46:42 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (May 19, 2020):

This is the official Bitwarden server? Or some other community edition?

<!-- gh-comment-id:630524467 --> @kspearrin commented on GitHub (May 19, 2020): This is the official Bitwarden server? Or some other community edition?
GiteaMirror commented 2026-04-23 15:46:42 -05:00
Author
Owner
Copy Link

@rainx0r commented on GitHub (May 19, 2020):

I am using the official Bitwarden server self hosted via its docker image as described in this this guide, not Bitwarden_rs or similar, if that's what your question is.

The main difference is that I have it running on ports other than 80 and 443, and then I am accessing the instance via a reverse proxy on my own nginx server (outside of the docker network), and it's at that proxy level where SSL is set up, which I think is probably the issue here.

Do you have any ideas on how I could debug the android client's connection to my Bitwarden instance? Are there any logs I could check on either side?

<!-- gh-comment-id:630816116 --> @rainx0r commented on GitHub (May 19, 2020): I am using the official Bitwarden server self hosted via its docker image as described in this [this guide](https://bitwarden.com/help/article/install-on-premise/), not Bitwarden_rs or similar, if that's what your question is. The main difference is that I have it running on ports other than 80 and 443, and then I am accessing the instance via a reverse proxy on my own nginx server (outside of the docker network), and it's at that proxy level where SSL is set up, which I think is probably the issue here. Do you have any ideas on how I could debug the android client's connection to my Bitwarden instance? Are there any logs I could check on either side?
GiteaMirror commented 2026-04-23 15:46:43 -05:00
Author
Owner
Copy Link

@rainx0r commented on GitHub (May 20, 2020):

I would like to add that I just tested it with the iOS version of the client, and that works fine. So it seems to be just the Android version of the mobile client that is having this issue.

<!-- gh-comment-id:631685764 --> @rainx0r commented on GitHub (May 20, 2020): I would like to add that I just tested it with the iOS version of the client, and that works fine. So it seems to be just the Android version of the mobile client that is having this issue.
GiteaMirror commented 2026-04-23 15:46:43 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (May 21, 2020):

The only time I have never seen this occur is when there is some SSL related issue. Could you share your server URL here or via email so I could test against it?

<!-- gh-comment-id:632050825 --> @kspearrin commented on GitHub (May 21, 2020): The only time I have never seen this occur is when there is some SSL related issue. Could you share your server URL here or via email so I could test against it?
GiteaMirror commented 2026-04-23 15:46:44 -05:00
Author
Owner
Copy Link

@rainx0r commented on GitHub (May 21, 2020):

Sure, I would prefer sharing it via e-mail though. What address should I mail it to?

<!-- gh-comment-id:632076679 --> @rainx0r commented on GitHub (May 21, 2020): Sure, I would prefer sharing it via e-mail though. What address should I mail it to?
GiteaMirror commented 2026-04-23 15:46:44 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (May 22, 2020):

support@bitwarden.com and just put "attention kspearrin" with a link to this issue.

<!-- gh-comment-id:632715631 --> @kspearrin commented on GitHub (May 22, 2020): support@bitwarden.com and just put "attention kspearrin" with a link to this issue.
GiteaMirror commented 2026-04-23 15:46:44 -05:00
Author
Owner
Copy Link

@rainx0r commented on GitHub (May 22, 2020):

Sent and included the phrase in both the title and body, thank you for any help in advance!

<!-- gh-comment-id:632724332 --> @rainx0r commented on GitHub (May 22, 2020): Sent and included the phrase in both the title and body, thank you for any help in advance!
GiteaMirror commented 2026-04-23 15:46:45 -05:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (May 23, 2020):

I debugged your server and here is the response I am getting when calling any authenticated API from the android app:

<html>
<head><title>400 Request Header Or Cookie Too Large</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<center>Request Header Or Cookie Too Large</center>
</body>
</html>

It seems you need to update your nginx proxy to allow larger header sizes.

<!-- gh-comment-id:632961534 --> @kspearrin commented on GitHub (May 23, 2020): I debugged your server and here is the response I am getting when calling any authenticated API from the android app: ``` <html> <head><title>400 Request Header Or Cookie Too Large</title></head> <body> <center><h1>400 Bad Request</h1></center> <center>Request Header Or Cookie Too Large</center> </body> </html> ``` It seems you need to update your nginx proxy to allow larger header sizes.
GiteaMirror commented 2026-04-23 15:46:45 -05:00
Author
Owner
Copy Link

@rainx0r commented on GitHub (May 23, 2020):

Perfect, thank you so much for taking your time to debug this.

For future reference I solved this by adding the following to my server block and it now works fine with the Android client.

server {
    ....
    large_client_header_buffers 4 32k;
    ...
}
<!-- gh-comment-id:632962943 --> @rainx0r commented on GitHub (May 23, 2020): Perfect, thank you so much for taking your time to debug this. For future reference I solved this by adding the following to my `server` block and it now works fine with the Android client. ``` server { .... large_client_header_buffers 4 32k; ... } ```
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
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#37976
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?