github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-12 05:04:17 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Android app started giving error connecting to server #749

New Issue
Closed
opened 2025-11-26 22:28:26 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-26 22:28:26 -06:00
Owner
Copy Link

Originally created by @hank on GitHub (May 12, 2019).

The android app was working great until today. Now I can't get it to connect to my server anymore. I'm using Letsencrypt certificates that work fine in mobile chrome with no warnings. Login through mobile chrome works perfectly. Please let me know how I can display the actual error.

Originally created by @hank on GitHub (May 12, 2019). The android app was working great until today. Now I can't get it to connect to my server anymore. I'm using Letsencrypt certificates that work fine in mobile chrome with no warnings. Login through mobile chrome works perfectly. Please let me know how I can display the actual error.
GiteaMirror commented 2025-11-26 22:28:26 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (May 13, 2019):

Nothing has changed with the Android app in weeks, so something else has caused this problem, likely with your server. I suggest checking the trust chain for your server with https://www.digicert.com/help/

@kspearrin commented on GitHub (May 13, 2019): Nothing has changed with the Android app in weeks, so something else has caused this problem, likely with your server. I suggest checking the trust chain for your server with https://www.digicert.com/help/
GiteaMirror commented 2025-11-26 22:28:27 -06:00
Author
Owner
Copy Link

@hank commented on GitHub (May 13, 2019):

Capture

@hank commented on GitHub (May 13, 2019): ![Capture](https://user-images.githubusercontent.com/8534/57591510-ca3d2c80-74ff-11e9-8d3c-4c36f154d57a.PNG)
GiteaMirror commented 2025-11-26 22:28:27 -06:00
Author
Owner
Copy Link

@hank commented on GitHub (May 13, 2019):

Capture

@hank commented on GitHub (May 13, 2019): ![Capture](https://user-images.githubusercontent.com/8534/57591597-391a8580-7500-11e9-89e1-83022465a303.PNG)
GiteaMirror commented 2025-11-26 22:28:27 -06:00
Author
Owner
Copy Link

@hank commented on GitHub (May 13, 2019):

Did a couple more tests and saw this: could it be the culprit? (From the Qualys TLS test)

OCSP STAPLING ERROR: OCSP response expired on Thu May 09 19:00:00 UTC 2019

@hank commented on GitHub (May 13, 2019): Did a couple more tests and saw this: could it be the culprit? (From the [Qualys TLS test](https://www.ssllabs.com/ssltest/)) OCSP STAPLING ERROR: OCSP response expired on Thu May 09 19:00:00 UTC 2019 --
GiteaMirror commented 2025-11-26 22:28:27 -06:00
Author
Owner
Copy Link

@hank commented on GitHub (May 13, 2019):

Also I only support TLS 1.2 - would that be an issue?

@hank commented on GitHub (May 13, 2019): Also I only support TLS 1.2 - would that be an issue?
GiteaMirror commented 2025-11-26 22:28:27 -06:00
Author
Owner
Copy Link

@hank commented on GitHub (May 13, 2019):

Turns out I had a permissions issue on my ocsp response cache:

May 12 22:42:38 caddy caddy[8129]: 2019/05/12 22:42:38 [WARNING] Stapling OCSP: unable to write OCSP staple file for [bitwarden.mydoma.in]: open /etc/caddy/ocsp/bitwarden.mydoma.in-a7a7a7a7: permission denied

I corrected this and restarted caddy to update the cache. Then I tried the app again and everything worked. The strange part is: I don't have OCSP must staple on:

OCSP Must Staple | No

Please add a better error for this case if it occurs to steer people in the right direction. Something like "OCSP validation failed: expired response" or something to that effect would do the trick.

@hank commented on GitHub (May 13, 2019): Turns out I had a permissions issue on my ocsp response cache: ``` May 12 22:42:38 caddy caddy[8129]: 2019/05/12 22:42:38 [WARNING] Stapling OCSP: unable to write OCSP staple file for [bitwarden.mydoma.in]: open /etc/caddy/ocsp/bitwarden.mydoma.in-a7a7a7a7: permission denied ``` I corrected this and restarted caddy to update the cache. Then I tried the app again and everything worked. The strange part is: I don't have OCSP must staple on: ``` OCSP Must Staple | No ``` Please add a better error for this case if it occurs to steer people in the right direction. Something like "OCSP validation failed: expired response" or something to that effect would do the trick.
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#749
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?