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

Android error using self-hosted #145

New Issue
Closed
opened 2025-11-07 08:28:39 -06:00 by GiteaMirror · 14 comments
GiteaMirror commented 2025-11-07 08:28:39 -06:00
Owner
Copy Link

Originally created by @JTechHPS on GitHub (Dec 13, 2017).

I have self hosted setup and working in web browsers. In the Android app, I've entered my server address in the settings, but get the error: "An error has occurred. There is a problem connecting to the server." I am able to log in through my mobile browser.

Originally created by @JTechHPS on GitHub (Dec 13, 2017). I have self hosted setup and working in web browsers. In the Android app, I've entered my server address in the settings, but get the error: "An error has occurred. There is a problem connecting to the server." I am able to log in through my mobile browser.
GiteaMirror commented 2025-11-07 08:28:40 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Dec 13, 2017):

Are you using a self signed cert?

@kspearrin commented on GitHub (Dec 13, 2017): Are you using a self signed cert?
GiteaMirror commented 2025-11-07 08:28:41 -06:00
Author
Owner
Copy Link

@JTechHPS commented on GitHub (Dec 13, 2017):

Yes, the one generated during setup.

@JTechHPS commented on GitHub (Dec 13, 2017): Yes, the one generated during setup.
GiteaMirror commented 2025-11-07 08:28:43 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Dec 13, 2017):

You need to install it to the trusted store on the android device.

@kspearrin commented on GitHub (Dec 13, 2017): You need to install it to the trusted store on the android device.
GiteaMirror commented 2025-11-07 08:28:43 -06:00
Author
Owner
Copy Link

@JTechHPS commented on GitHub (Dec 13, 2017):

I exported the cert from the PC browser and installed it in my mobile trusted store. It is listed, but I get the same error.

@JTechHPS commented on GitHub (Dec 13, 2017): I exported the cert from the PC browser and installed it in my mobile trusted store. It is listed, but I get the same error.
GiteaMirror commented 2025-11-07 08:28:43 -06:00
Author
Owner
Copy Link

@paescuj commented on GitHub (Dec 20, 2017):

Same here. I'm using a self signed cert which I've added to the trust store. It used to work, but stopped with one of the recent updates.

@paescuj commented on GitHub (Dec 20, 2017): Same here. I'm using a self signed cert which I've added to the trust store. It used to work, but stopped with one of the recent updates.
GiteaMirror commented 2025-11-07 08:28:43 -06:00
Author
Owner
Copy Link

@paescuj commented on GitHub (Jan 3, 2018):

Seems to have been resolved in the latest release v1.14.0

@paescuj commented on GitHub (Jan 3, 2018): Seems to have been resolved in the latest release [v1.14.0](https://github.com/bitwarden/mobile/releases/tag/v1.14.0)
GiteaMirror commented 2025-11-07 08:28:44 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jan 3, 2018):

Nothing was changed regarding this issue so I am not sure why 🤷‍♂️

@JTechHPS can you confirm as well?

@kspearrin commented on GitHub (Jan 3, 2018): Nothing was changed regarding this issue so I am not sure why 🤷‍♂️ @JTechHPS can you confirm as well?
GiteaMirror commented 2025-11-07 08:28:44 -06:00
Author
Owner
Copy Link

@Shadow00Caster commented on GitHub (Jan 25, 2018):

I am having this issue, I previously was using a LE cert, I have switched to a Comodo cert and the issue still persists. Presumably eliminating the cert as a potential issue, I am using a non-standard port.

@Shadow00Caster commented on GitHub (Jan 25, 2018): I am having this issue, I previously was using a LE cert, I have switched to a Comodo cert and the issue still persists. Presumably eliminating the cert as a potential issue, I am using a non-standard port.
GiteaMirror commented 2025-11-07 08:28:44 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jan 27, 2018):

Please check your domain's cert using https://www.digicert.com/help/

@kspearrin commented on GitHub (Jan 27, 2018): Please check your domain's cert using https://www.digicert.com/help/
GiteaMirror commented 2025-11-07 08:28:45 -06:00
Author
Owner
Copy Link

@Shadow00Caster commented on GitHub (Jan 29, 2018):

Finally figured this out. I tested with BW on a the standard 443 and a non-standard port, all with the same result. What I figured out was that the cert was appearing as not trusted, however I tested with another CA and have various other services using LE certs without issue that show as trusted on multiple SSL testing platforms.

I got this to work by editing the default.conf file in BW's nginx config under bwdata/nginx/default.conf and changing the ssl_certificate line from the certificate only file provided by LE to the fullchain cert file which is the cert and the CA chain bundle file. This resolved the issue.

Not sure if this was something that was done from my early attempts at configuration, but I imagine by default the SSL file should be using the fullchain/bundle cert file over the cert only file.

@Shadow00Caster commented on GitHub (Jan 29, 2018): Finally figured this out. I tested with BW on a the standard 443 and a non-standard port, all with the same result. What I figured out was that the cert was appearing as not trusted, however I tested with another CA and have various other services using LE certs without issue that show as trusted on multiple SSL testing platforms. I got this to work by editing the default.conf file in BW's nginx config under `bwdata/nginx/default.conf` and changing the `ssl_certificate` line from the certificate only file provided by LE to the fullchain cert file which is the cert and the CA chain bundle file. This resolved the issue. Not sure if this was something that was done from my early attempts at configuration, but I imagine by default the SSL file should be using the fullchain/bundle cert file over the cert only file.
GiteaMirror commented 2025-11-07 08:28:45 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Jan 29, 2018):

The default for LE is to reference fullchain.pem from the nginx config so it sounds like you changed something.

@kspearrin commented on GitHub (Jan 29, 2018): The default for LE is to reference `fullchain.pem` from the nginx config so it sounds like you changed something.
GiteaMirror commented 2025-11-07 08:28:46 -06:00
Author
Owner
Copy Link

@emollusion commented on GitHub (Jul 15, 2018):

I have just installed and got bitwarden to run self hosted.
Accessing it through a browser or browser extensions works fine, but accessing it through the android app does not.
I installed using self-signed certificate.
I also downloaded the certificate from the browser, and installed it on the phone.
Any ideas?

@emollusion commented on GitHub (Jul 15, 2018): I have just installed and got bitwarden to run self hosted. Accessing it through a browser or browser extensions works fine, but accessing it through the android app does not. I installed using self-signed certificate. I also downloaded the certificate from the browser, and installed it on the phone. Any ideas?
GiteaMirror commented 2025-11-07 08:28:46 -06:00
Author
Owner
Copy Link

@ArthurAttout commented on GitHub (Aug 27, 2018):

Has this been looked at since then ? I keep on receiving the error on Android aswell, even after installing the certificate on the device.

@ArthurAttout commented on GitHub (Aug 27, 2018): Has this been looked at since then ? I keep on receiving the error on Android aswell, even after installing the certificate on the device.
GiteaMirror commented 2025-11-07 08:28:47 -06:00
Author
Owner
Copy Link

@dst78 commented on GitHub (Jan 20, 2019):

I can confirm that the workaround as described by Shadow00Caster does indeed work for self-signed certificates.

@dst78 commented on GitHub (Jan 20, 2019): I can confirm that the workaround as described by Shadow00Caster does indeed work for self-signed certificates.
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#145
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?