There is a problem connecting to the server #241

@JoaoMXN commented on GitHub (Jun 28, 2018):

I looked at the settings and gave two more permissions (camera and memory), but still keeps loading in "logging in" and after a few minutes gives the error.

@JoaoMXN commented on GitHub (Jun 28, 2018): I looked at the settings and gave two more permissions (camera and memory), but still keeps loading in "logging in" and after a few minutes gives the error.

GiteaMirror commented

@kspearrin commented on GitHub (Jun 28, 2018):

Does it have internet permissions?

@kspearrin commented on GitHub (Jun 28, 2018): Does it have internet permissions?

GiteaMirror commented

@JoaoMXN commented on GitHub (Jun 28, 2018):

Yes. I took a screenshot of all the permissions.

@JoaoMXN commented on GitHub (Jun 28, 2018): Yes. I took a screenshot of all the permissions. ![screenshot_2018-06-28-20-54-44](https://user-images.githubusercontent.com/6750448/42066243-f35903e4-7b15-11e8-9c72-3ba77af4bb74.png) ![screenshot_2018-06-28-20-54-53](https://user-images.githubusercontent.com/6750448/42066244-f37aacd8-7b15-11e8-92cd-c136af0b95dd.png)

GiteaMirror commented

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

Can you try this? Open a notes app or something where you can see what you are typing. Type your master password there so you can see that it is exactly correct. Then copy and paste it into Bitwarden login form rather than typing it. Does that change anything?

@kspearrin commented on GitHub (Jun 29, 2018): Can you try this? Open a notes app or something where you can see what you are typing. Type your master password there so you can see that it is exactly correct. Then copy and paste it into Bitwarden login form rather than typing it. Does that change anything?

GiteaMirror commented

@JoaoMXN commented on GitHub (Jun 29, 2018):

It didn't work, unfortunately. I also changed my DNS and nothing. Funny that the first day when I downloaded the app it worked normally and today it doesn't want to log in anymore.

@JoaoMXN commented on GitHub (Jun 29, 2018): It didn't work, unfortunately. I also changed my DNS and nothing. Funny that the first day when I downloaded the app it worked normally and today it doesn't want to log in anymore.

GiteaMirror commented

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

Unfortunately I don't have any other ideas at this time. Please let me know if you figure anything out.

@kspearrin commented on GitHub (Jun 29, 2018): Unfortunately I don't have any other ideas at this time. Please let me know if you figure anything out.

GiteaMirror commented

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

Also, is this on the regular Bitwarden cloud servers or are you using your own server?

@kspearrin commented on GitHub (Jun 29, 2018): Also, is this on the regular Bitwarden cloud servers or are you using your own server?

GiteaMirror commented

2025-11-07 08:32:19 -06:00

@JoaoMXN commented on GitHub (Jun 29, 2018):

It is on the regular Bitwarden servers. By the way, my phone is rooted, could that be it?

@JoaoMXN commented on GitHub (Jun 29, 2018): It is on the regular Bitwarden servers. By the way, my phone is rooted, could that be it?

GiteaMirror commented

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

It could be anything. Does logcat report any kind of errors when logging in?

@kspearrin commented on GitHub (Jun 29, 2018): It could be anything. Does logcat report any kind of errors when logging in?

GiteaMirror commented

@JoaoMXN commented on GitHub (Jun 29, 2018):

I don't know how to read it properly, but I don't see any errors.

bitwarden log.txt

@JoaoMXN commented on GitHub (Jun 29, 2018): I don't know how to read it properly, but I don't see any errors. [bitwarden log.txt](https://github.com/bitwarden/mobile/files/2147725/bitwarden.log.txt)

GiteaMirror commented

@x11x commented on GitHub (Jul 20, 2018):

I am also having problems logging in on a rooted phone.
There is no delay, just a dialog "An error has occurred. Not connected to the internet." It appears instantly when I try to log in.
I have verified that I am connected to the internet, other apps have connectivity, tried all different connections, I'm sure its not a connectivity problem.
I am running Afwall+ (firewall), and I have checked that it is configured correctly for Bitwarden (allowed full access). I have also tried disabling Afwall+.
It is an unusual setup, Chinese firmware (ZUI, based on Android 7.0) and does not have Google Play services. However, most apps work. I realise this app uses Firebase, Google push messaging etc.
bitwarden-logcat.txt
I read #6 that it should still work without push messaging. I tried the Fdroid apk,.
My theory is that the connectivity check has some requirement (Google play services?) and is causing it to fail even though there is connectivity. Is there any way to disable that connectivity check? It would be good if the connectivity check could be skipped if Google play services is not detected.
I have not had a chance to try building myself and probably will not for some time. My first thought was to try removing the check https://github.com/bitwarden/mobile/blob/master/src/App/Repositories/ApiRepository.cs#L26 but I am not familiar with the code at all so have no idea if this is the right track or not.
A bit of logcat is attached (adb logcat | grep -i bitwarden), I can't see any exceptions in there. I can post another complete logcat if you need.

@x11x commented on GitHub (Jul 20, 2018): I am also having problems logging in on a rooted phone. There is no delay, just a dialog "An error has occurred. Not connected to the internet." It appears instantly when I try to log in. I have verified that I am connected to the internet, other apps have connectivity, tried all different connections, I'm sure its not a connectivity problem. I am running Afwall+ (firewall), and I have checked that it is configured correctly for Bitwarden (allowed full access). I have also tried disabling Afwall+. It is an unusual setup, Chinese firmware (ZUI, based on Android 7.0) and does not have Google Play services. However, most apps work. I realise this app uses Firebase, Google push messaging etc. [bitwarden-logcat.txt](https://github.com/bitwarden/mobile/files/2213953/bitwarden-logcat.txt) I read #6 that it should still work without push messaging. I tried the Fdroid apk,. My theory is that the connectivity check has some requirement (Google play services?) and is causing it to fail even though there is connectivity. Is there any way to disable that connectivity check? It would be good if the connectivity check could be skipped if Google play services is not detected. I have not had a chance to try building myself and probably will not for some time. My first thought was to try removing the check https://github.com/bitwarden/mobile/blob/master/src/App/Repositories/ApiRepository.cs#L26 but I am not familiar with the code at all so have no idea if this is the right track or not. A bit of logcat is attached (`adb logcat | grep -i bitwarden`), I can't see any exceptions in there. I can post another complete logcat if you need.

GiteaMirror commented

https://github.com/jamesmontemagno/ConnectivityPlugin/blob/master/src/Connectivity.Plugin.Android/ConnectivityImplementation.cs

@kspearrin commented on GitHub (Jul 20, 2018):

@x11x This is the library we use for connectivity testing on Android:

We updated it recently and pushed it to the beta track on Google Play. Could you re-test it with these updates and see if the problem was fixed perhaps?

https://play.google.com/apps/testing/com.x8bit.bitwarden

Or download the raw APK here:
https://ci.appveyor.com/project/bitwarden/mobile/build/artifacts

@kspearrin commented on GitHub (Jul 20, 2018): @x11x This is the library we use for connectivity testing on Android: https://github.com/jamesmontemagno/ConnectivityPlugin/blob/master/src/Connectivity.Plugin.Android/ConnectivityImplementation.cs We updated it recently and pushed it to the beta track on Google Play. Could you re-test it with these updates and see if the problem was fixed perhaps? https://play.google.com/apps/testing/com.x8bit.bitwarden Or download the raw APK here: https://ci.appveyor.com/project/bitwarden/mobile/build/artifacts

GiteaMirror commented

@x11x commented on GitHub (Jul 20, 2018):

@kspearrin I tried with the updates and it works!
Thanks very much for your quick response, I'm impressed.
Really love this app and service, very happy with it.
That solves my issue but I think my issue was different to the OP.
Hoping the Fdroid release will work out soon and I can install from there, although I know they can make it difficult to get apps in that have nonfree components.

@x11x commented on GitHub (Jul 20, 2018): @kspearrin I tried with the updates and it works! Thanks very much for your quick response, I'm impressed. Really love this app and service, very happy with it. That solves my issue but I think my issue was different to the OP. Hoping the Fdroid release will work out soon and I can install from there, although I know they can make it difficult to get apps in that have nonfree components.

GiteaMirror commented

2025-11-07 08:32:21 -06:00

@kspearrin commented on GitHub (Jul 20, 2018):

@JoaoMXN Can you try latest beta please?

@kspearrin commented on GitHub (Jul 20, 2018): @JoaoMXN Can you try latest beta please?

GiteaMirror commented

@JoaoMXN commented on GitHub (Jul 20, 2018):

@kspearrin Still has the problem. It doesn't show the error right away like with x11x, but stays at the login loading for several minutes before the server error.

@JoaoMXN commented on GitHub (Jul 20, 2018): @kspearrin Still has the problem. It doesn't show the error right away like with x11x, but stays at the login loading for several minutes before the server error.

GiteaMirror commented

2025-11-07 08:32:21 -06:00

@road42 commented on GitHub (Jul 22, 2018):

Same problem here. Also installed beta.
Self hosted server with LE certificate and nondefault port.

@road42 commented on GitHub (Jul 22, 2018): Same problem here. Also installed beta. Self hosted server with LE certificate and nondefault port.

GiteaMirror commented

2025-11-07 08:32:21 -06:00

@kspearrin commented on GitHub (Jul 22, 2018):

@road42 Sounds like a separate issue. Your LE cert probably doesn't have a full trust chain, which is required on Android.

@kspearrin commented on GitHub (Jul 22, 2018): @road42 Sounds like a separate issue. Your LE cert probably doesn't have a full trust chain, which is required on Android.

GiteaMirror commented

2025-11-07 08:32:22 -06:00

@andre1808 commented on GitHub (Jul 24, 2018):

Got the same problem as road42 too. Installed Bitwarden to my qnap NAS and created a LE cert using the QNAP ddns service. Also used a nondefault port.
It's working from everywhere except the android app. Also working from any android browser (tested Chrome and Firefox).

Also tried the beta app, still the same issue. However the "There is a problem connecting to the server" error message comes quite instantly.

@andre1808 commented on GitHub (Jul 24, 2018): Got the same problem as road42 too. Installed Bitwarden to my qnap NAS and created a LE cert using the QNAP ddns service. Also used a nondefault port. It's working from everywhere except the android app. Also working from any android browser (tested Chrome and Firefox). Also tried the beta app, still the same issue. However the "There is a problem connecting to the server" error message comes quite instantly.

GiteaMirror commented

2025-11-07 08:32:22 -06:00

@kspearrin commented on GitHub (Jul 24, 2018):

@andre1808 Sounds like a separate issue. Your LE cert probably doesn't have a full trust chain, which is required on Android. Check on https://www.digicert.com/help/

@kspearrin commented on GitHub (Jul 24, 2018): @andre1808 Sounds like a separate issue. Your LE cert probably doesn't have a full trust chain, which is required on Android. Check on https://www.digicert.com/help/

GiteaMirror commented

2025-11-07 08:32:22 -06:00

@road42 commented on GitHub (Jul 24, 2018):

@kspearrin
If I call my Bitwarden Local Site via Android Chrome everything is valid including the certificate. Chrome seems to bring its own CertificateChain.

I checked the Settings -> DeviceSecurity -> Certificates if anything sounds like "LE" and did not find anything.

Then I went to: https://letsencrypt.org/certificates/ and
downloaded the two "active intermediate" certificates.
Renamed them to .pem (instead of .txt) and
imported them to the UserCertificates.

Now I can successfully connect to my own bitwarden server.

@road42 commented on GitHub (Jul 24, 2018): @kspearrin If I call my Bitwarden Local Site via Android Chrome everything is valid including the certificate. Chrome seems to bring its own CertificateChain. I checked the Settings -> DeviceSecurity -> Certificates if anything sounds like "LE" and did not find anything. 1. Then I went to: https://letsencrypt.org/certificates/ and 2. downloaded the two "active intermediate" certificates. 3. Renamed them to .pem (instead of .txt) and 4. imported them to the UserCertificates. Now I can successfully connect to my own bitwarden server.

GiteaMirror commented

2025-11-07 08:32:23 -06:00

@andre1808 commented on GitHub (Jul 24, 2018):

@road42
Christoph, you are the man!
Did the exact same thing as you did and now it's working just fine!
Honestly, I was fiddling around with this shit for like 10 hours (since yesterday) and now it's finally the way I was wishing it would be!
Thank you so much :)
An easier way to get around this (without importing the certificates) would be great though :D

@andre1808 commented on GitHub (Jul 24, 2018): @road42 Christoph, you are the man! Did the exact same thing as you did and now it's working just fine! Honestly, I was fiddling around with this shit for like 10 hours (since yesterday) and now it's finally the way I was wishing it would be! Thank you so much :) An easier way to get around this (without importing the certificates) would be great though :D

GiteaMirror commented

2025-11-07 08:32:23 -06:00

@Joshndroid commented on GitHub (Jul 27, 2018):

@road42

    Then I went to: https://letsencrypt.org/certificates/ and
    downloaded the two "active intermediate" certificates.
    Renamed them to .pem (instead of .txt) and
    imported them to the UserCertificates.

Are you self hosting?
I see with your method that there is no private.key listed as you have just downloaded .pem files are you converting them to .crt to place in your bwdata for self hosting?

@Joshndroid commented on GitHub (Jul 27, 2018): @road42 ``` Then I went to: https://letsencrypt.org/certificates/ and downloaded the two "active intermediate" certificates. Renamed them to .pem (instead of .txt) and imported them to the UserCertificates. ``` Are you self hosting? I see with your method that there is no private.key listed as you have just downloaded .pem files are you converting them to .crt to place in your bwdata for self hosting?

GiteaMirror commented

2025-11-07 08:32:23 -06:00

@andre1808 commented on GitHub (Jul 27, 2018):

@Joshndroid
You first have to create certificates (with lets encrypt) for your server. You need to integrate those to your bitwarden installation.
When you did that you can download the intermediate certificates from letsencrypt and import them on your mobile.

@andre1808 commented on GitHub (Jul 27, 2018): @Joshndroid You first have to create certificates (with lets encrypt) for your server. You need to integrate those to your bitwarden installation. When you did that you can download the intermediate certificates from letsencrypt and import them on your mobile.

GiteaMirror commented

2025-11-07 08:32:24 -06:00

@Joshndroid commented on GitHub (Jul 27, 2018):

@andre1808

Im running local instance and not allowing outside access (use VPN for that) so I'm lead to nieve let's encrypt won't work in that fashion

@Joshndroid commented on GitHub (Jul 27, 2018): @andre1808 Im running local instance and not allowing outside access (use VPN for that) so I'm lead to nieve let's encrypt won't work in that fashion

GiteaMirror commented

2025-11-07 08:32:24 -06:00

@phantomjinx commented on GitHub (Jul 28, 2018):

Same problem as original bug report.

Created new account for my wife.
Installed bitwarden on the desktop and logs in fine.
Installed firefox extension on android and logs in fine.
Installed android app and fails to login, eventually timing out after a minute or so.

Tried changing permissions for the app and makes no difference.
Tried logging into my own account using the app on my phone and it works fine.
Tried logging into my own account using the app on wife's phone and fails.
Tried logging into my wife's account using the app on my phone and works fine.
Tried logging into my either account with my wife's tablet and fails.
Both phones are running the same version although I installed bitwarden to my phone originally 6 months ago.
Upgraded to the beta and still failed to connect.

Specs

Wife's Phone: Android 7.0
Wife's Tablet: Android 5.0.1
My Phone: Android 8.0

Conclusions:

Not related to account but the communication of the app with the servers.
Some regression bug with older Android versions?

@phantomjinx commented on GitHub (Jul 28, 2018): Same problem as original bug report. Created new account for my wife. Installed bitwarden on the desktop and logs in fine. Installed firefox extension on android and logs in fine. Installed android app and fails to login, eventually timing out after a minute or so. * Tried changing permissions for the app and makes no difference. * Tried logging into my own account using the app on my phone and it works fine. * Tried logging into my own account using the app on wife's phone and fails. * Tried logging into my wife's account using the app on my phone and works fine. * Tried logging into my either account with my wife's tablet and fails. * Both phones are running the same version although I installed bitwarden to my phone originally 6 months ago. * Upgraded to the beta and still failed to connect. Specs * Wife's Phone: Android 7.0 * Wife's Tablet: Android 5.0.1 * My Phone: Android 8.0 Conclusions: * Not related to account but the communication of the app with the servers. * Some regression bug with older Android versions?

GiteaMirror commented

2025-11-07 08:32:24 -06:00

@Celsiusss commented on GitHub (Aug 17, 2018):

Same issue for me, running non-rooted Android 8.0.
Tried the beta app, same thing.

EDIT: Found out that the app has troubles connecting over wifi, using cellular data fixed the problem. Same thing happens when logged in when doing any server requests.

@Celsiusss commented on GitHub (Aug 17, 2018): Same issue for me, running non-rooted Android 8.0. Tried the beta app, same thing. EDIT: Found out that the app has troubles connecting over wifi, using cellular data fixed the problem. Same thing happens when logged in when doing any server requests.

GiteaMirror commented

2025-11-07 08:32:25 -06:00

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

I'm having this same issue, and it sounds like the core issue is that the certificate chain isn't available. My question - is there a way to add the chain.pem file from LE into NGINX's config, or do I need to create a new cert file with the cert and full chain together?

NVM, I'm a moron. I changed the certificate that NGINX is using from the "cert.pem" file to the "fullchain.pem" file and I was able to log in.

@FoxBJK commented on GitHub (Aug 27, 2018): I'm having this same issue, and it sounds like the core issue is that the certificate chain isn't available. My question - is there a way to add the chain.pem file from LE into NGINX's config, or do I need to create a new cert file with the cert and full chain together? NVM, I'm a moron. I changed the certificate that NGINX is using from the "cert.pem" file to the "fullchain.pem" file and I was able to log in.

GiteaMirror commented

2025-11-07 08:32:25 -06:00

@phantomjinx commented on GitHub (Aug 29, 2018):

Just to clarify, the issue I am facing has nothing to do with a standalone/local installation of bitwarden. My devices are failing to connect to the main Bitwarden server (and failing).

@phantomjinx commented on GitHub (Aug 29, 2018): Just to clarify, the issue I am facing has nothing to do with a standalone/local installation of bitwarden. My devices are failing to connect to the main Bitwarden server (and failing).

GiteaMirror commented

2025-11-07 08:32:25 -06:00

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

@phantomjinx Maybe you have internet permissions blocked for the app?

@kspearrin commented on GitHub (Aug 29, 2018): @phantomjinx Maybe you have internet permissions blocked for the app?

GiteaMirror commented

2025-11-07 08:32:26 -06:00

@phantomjinx commented on GitHub (Aug 29, 2018):

@kspearrin
No. See my comment above.

@phantomjinx commented on GitHub (Aug 29, 2018): @kspearrin No. See my [comment](https://github.com/bitwarden/mobile/issues/334#issuecomment-408635418) above.

GiteaMirror commented

2025-11-07 08:32:26 -06:00

@FoxBJK commented on GitHub (Aug 29, 2018):

Just to rule this out, does your connection use any kind of proxy or network filtering that might interfere with certificate delivery? Is your Android device modified to not include the root CA and intermediate certs that Bitwarden uses? Android's really picky about certificates in general.

@FoxBJK commented on GitHub (Aug 29, 2018): Just to rule this out, does your connection use any kind of proxy or network filtering that might interfere with certificate delivery? Is your Android device modified to not include the root CA and intermediate certs that Bitwarden uses? Android's _really_ picky about certificates in general.

GiteaMirror commented

2025-11-07 08:32:26 -06:00

@phantomjinx commented on GitHub (Aug 29, 2018):

@FoxBJK
No proxy. Straight to home network router and on to internet. If anyone could let me know the ports that Bitwarden talks to I could log the packets coming in and out of the router. At least then I can confirm connectivity. My LG6 phone has no issues connecting (instantaneous). Yet still the case that my wife's tablet, phone and my own tablet (LineageOS 14.1 / Android 7.1.2) all fail to connect.

@phantomjinx commented on GitHub (Aug 29, 2018): @FoxBJK No proxy. Straight to home network router and on to internet. If anyone could let me know the ports that Bitwarden talks to I could log the packets coming in and out of the router. At least then I can confirm connectivity. My LG6 phone has no issues connecting (instantaneous). Yet still the case that my wife's tablet, phone and my own tablet (LineageOS 14.1 / Android 7.1.2) all fail to connect.

GiteaMirror commented

2025-11-07 08:32:27 -06:00

@FoxBJK commented on GitHub (Aug 29, 2018):

I only needed to open up the standard HTTPS port (443) for my self-hosted instance, so I'd assume all communication is done through there.

@FoxBJK commented on GitHub (Aug 29, 2018): I only needed to open up the standard HTTPS port (443) for my self-hosted instance, so I'd assume all communication is done through there.

GiteaMirror commented

2025-11-07 08:32:27 -06:00

@phantomjinx commented on GitHub (Aug 30, 2018):

Good news!
Yesterday Bitwarden app just wouldn't connect. Today, I have borh my tablet and the wifs's phone up n running. Made no changes to either in last 24 hours so presumably something has been fixed on the server? Anyway, thanks!

@phantomjinx commented on GitHub (Aug 30, 2018): Good news! Yesterday Bitwarden app just wouldn't connect. Today, I have borh my tablet and the wifs's phone up n running. Made no changes to either in last 24 hours so presumably something has been fixed on the server? Anyway, thanks!

GiteaMirror commented

@kspearrin commented on GitHub (Aug 30, 2018):

@phantomjinx No changes were made recently.

@kspearrin commented on GitHub (Aug 30, 2018): @phantomjinx No changes were made recently.

GiteaMirror commented

@phantomjinx commented on GitHub (Aug 30, 2018):

@kspearrin
Well that's juat plain weird. I made my original comment on the 28th July. Intermittently, I have tried logging in ever since both on my tablet and my wifes phone. Both failed as I have reported. Yet this evening both connect without a hitch. Clearly something has changed.

@phantomjinx commented on GitHub (Aug 30, 2018): @kspearrin Well that's juat plain weird. I made my original comment on the 28th July. Intermittently, I have tried logging in ever since both on my tablet and my wifes phone. Both failed as I have reported. Yet this evening both connect without a hitch. Clearly something has changed.

GiteaMirror commented

@kspearrin commented on GitHub (Aug 30, 2018):

Who knows. We haven't made any server changes since last week.

@kspearrin commented on GitHub (Aug 30, 2018): Who knows. We haven't made any server changes since last week.

GiteaMirror commented

@JoaoMXN commented on GitHub (Aug 30, 2018):

Still the same problem here. Timeout error at login.

@JoaoMXN commented on GitHub (Aug 30, 2018): Still the same problem here. Timeout error at login.

GiteaMirror commented

@phantomjinx commented on GitHub (Aug 30, 2018):

@JoaoMXN
What version are you running. Only possibility I can think of is BW app upgraded to 1.18.1 yesterday and I have rebooted.

@phantomjinx commented on GitHub (Aug 30, 2018): @JoaoMXN What version are you running. Only possibility I can think of is BW app upgraded to 1.18.1 yesterday and I have rebooted.

GiteaMirror commented

@JoaoMXN commented on GitHub (Aug 30, 2018):

@phantomjinx I downloaded the latest one from google play. I already give up trying a solution, just waiting some patch to solve it. Impossible to be a device issue since ALL apps work normally and the Bitwarden site in the browser works as well. It's 100% a Bitwarden server issue with the app.

@JoaoMXN commented on GitHub (Aug 30, 2018): @phantomjinx I downloaded the latest one from google play. I already give up trying a solution, just waiting some patch to solve it. Impossible to be a device issue since ALL apps work normally and the Bitwarden site in the browser works as well. It's 100% a Bitwarden server issue with the app.

GiteaMirror commented

@FoxBJK commented on GitHub (Sep 28, 2018):

Not sure this will help anybody, but this issue popped up for me again and I had to ensure a couple of things before it went away:

Make sure that the full certificate chain is available. Android apps will not validate HTTPS connections with just the cert and private key, you need the full chain.
When entering in the base URL for the Bitwarden server, you can't have a trailing '/'. I had to enter https://server.com:port, and only that, in order for this to work.

Running Android 9.0 on an Pixel 2

@FoxBJK commented on GitHub (Sep 28, 2018): Not sure this will help anybody, but this issue popped up for me again and I had to ensure a couple of things before it went away: - Make sure that the full certificate chain is available. Android apps will not validate HTTPS connections with just the cert and private key, you need the full chain. - When entering in the base URL for the Bitwarden server, you can't have a trailing '/'. I had to enter https://server.com:port, and only that, in order for this to work. Running Android 9.0 on an Pixel 2

GiteaMirror commented

@andre1808 commented on GitHub (Oct 19, 2018):

I have no idea why, but it stopped working again :(
Even adding the certificates manually to Android doesn't resolve the issue for me any longer.

Any idea how I can sort this?

@andre1808 commented on GitHub (Oct 19, 2018): I have no idea why, but it stopped working again :( Even adding the certificates manually to Android doesn't resolve the issue for me any longer. Any idea how I can sort this?

GiteaMirror commented