# Self-Signed SSL Certificate. OK on desktop but not Android

**URL:** <https://discourse.joplinapp.org/t/self-signed-ssl-certificate-ok-on-desktop-but-not-android/9341>\
**Category:** Support\
**Created:** [12 June 2020 10:21 UTC](https://discourse.joplinapp.org/t/self-signed-ssl-certificate-ok-on-desktop-but-not-android/9341 "2020-06-12T10:21:28Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![henrikfalk](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/henrikfalk/32/2986_2.png) [@henrikfalk](https://discourse.joplinapp.org/u/henrikfalk)\
**Post date:** [12 June 2020 10:21 UTC](https://discourse.joplinapp.org/t/self-signed-ssl-certificate-ok-on-desktop-but-not-android/9341/1 "2020-06-12T10:21:28Z")

</div>

Hi,

I’ve installed OwnCloud on one of my servers and everything works fine(localhost and remotely). I use a Self-Signed SSL Certificate on my apache2 server, so everything is HTTPS.

When I access the Joplins data from a Joplin desktop client, I need to enable: “Ignore TLS certificate errors” in the settings. That is OK. The desktop clients works.

But on the Joplin Android version I just get a “Network request failed”. This is a print of the log:

 ![joplin-cert](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/2X/a/ac1dcaf706c535b415c38bc2d3ceba9fbc1d80fd.jpeg)

I can’t find an “Ignore TLS certificate errors” option in the Android version?  
How can I get it to work?

Joplin Android version: 1.0.331  
Joplin Linux(Mint 19,3) version: 1.0.201

Regards  
Henrik

---

<div class="post-metadata">

**Author:** ![tessus](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/tessus/32/13_2.png) [@tessus](https://discourse.joplinapp.org/u/tessus)\
**Post date:** [12 June 2020 12:47 UTC](https://discourse.joplinapp.org/t/self-signed-ssl-certificate-ok-on-desktop-but-not-android/9341/2 "2020-06-12T12:47:48Z")

</div>

[https://joplinapp.org/faq/#how-can-i-use-self-signed-ssl-certificates-on-android](https://joplinapp.org/faq/#how-can-i-use-self-signed-ssl-certificates-on-android)

---

<div class="post-metadata">

**Author:** ![henrikfalk](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/henrikfalk/32/2986_2.png) [@henrikfalk](https://discourse.joplinapp.org/u/henrikfalk)\
**Post date:** [13 June 2020 10:03 UTC](https://discourse.joplinapp.org/t/self-signed-ssl-certificate-ok-on-desktop-but-not-android/9341/3 "2020-06-13T10:03:00Z")

</div>

OK, RTFM 😉  
But it still does not work.

The address owncloud says I should use as root dir for files: `https://<ip of server>/owncloud/remote.php/dav/files/<user>/`

Joplin Linux client works with "Ignore TLS certificate errors: `https://localhost/owncloud/remote.php/dav/files/<user>/Noter`

I have installed the certificate in my mobile phone.

To test the certificate I installed the app: "File Manager - Local and cloud Explorer" and added the cloud storage: `https://<ip of server>/owncloud/remote.php/dav/files/<user>/Noter`. It asks to trust the certificate, and creates the drive showing the Joplin files. It works.

In Joplin I use the same WebDAV url: `https://<ip of server>/owncloud/remote.php/dav/files/<user>/Noter`. Joplin does not ask for trusting the certificate, but writes the error, as in my first post.

I tried to uninstall and reinstall Joplin but it still does not work.

I tried to browse after Joplin related files(i.e. configuration) in the filesystem of the mobile phone, when Joplin is installed and after a remove, but I can't find any related configuration files. I know that no Joplin data should be able to "survive" an app install, but I was desperate 🙂

I just don't understand why the Joplin client works on my Linux client, and on my mobile with the filemanager app, but not with Joplin.

Maybe I am doing something wrong?  
Or am not able to read the FAQ properly?  
Anyone?

Regards  
Henrik

---

<div class="post-metadata">

**Author:** ![tessus](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/tessus/32/13_2.png) [@tessus](https://discourse.joplinapp.org/u/tessus)\
**Post date:** [13 June 2020 20:21 UTC](https://discourse.joplinapp.org/t/self-signed-ssl-certificate-ok-on-desktop-but-not-android/9341/4 "2020-06-13T20:21:14Z")

</div>

Unfortunately I am not sure why it fails. The error message is not very useful.

Maybe someone on this forum uses self signed certs with Android. It could be a combination of several things. My mobile dev env has a few glitches, so I can’t test it locally.

It would help others to know the version (8, 9, 10) and flavor (Google, Samsung, …) of Android you are using.

---

<div class="post-metadata">

**Author:** ![roman\_r\_m](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/roman_r_m/32/3297_2.png) [@roman\_r\_m](https://discourse.joplinapp.org/u/roman_r_m)\
**Post date:** [13 June 2020 21:25 UTC](https://discourse.joplinapp.org/t/self-signed-ssl-certificate-ok-on-desktop-but-not-android/9341/5 "2020-06-13T21:25:39Z")

</div>

I think this may be the reason it's not working:

> **[GitHub - wkh237/react-native-fetch-blob: A project committed to making file...](https://github.com/wkh237/react-native-fetch-blob#user-content-self-signed-ssl-server)**
>
> A project committed to making file access and data transfer easier, efficient for React Native developers. - GitHub - wkh237/react-native-fetch-blob: A project committed to making file access and d...

> By default, react-native-fetch-blob does NOT allow connection to unknown certification provider since it's dangerous. To connect a server with self-signed certification, you need to add `trusty` to `config` explicitly. This function is available for version \>= `0.5.3`

---

<div class="post-metadata">

**Author:** ![henrikfalk](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/henrikfalk/32/2986_2.png) [@henrikfalk](https://discourse.joplinapp.org/u/henrikfalk)\
**Post date:** [11 July 2020 15:00 UTC](https://discourse.joplinapp.org/t/self-signed-ssl-certificate-ok-on-desktop-but-not-android/9341/6 "2020-07-11T15:00:21Z")

</div>

Hi again.

Now I have Joplin 1.0.333 installed and it still does not work.

I have no problems using “FolderSync Pro” which have a setting to “Trust self-signed certificates”, and I have no problem using DAVx5 which just asked me if I waned to trust my self-signed certificate which is on the phone.  
I also installed the OwnCloud client which also works without problems (As I remember I just had to trust the self-signed certificate).

I am using Android version 10 on a “OnePlus 7T” but I don’t think that’s the problem?

The Joplin app does not have an option to trust self-signed certificates. Is that the reason for my problem?  
Is it something that can be implemented?

Maybe roman\_r\_m have a point? (I am not a programmer anymore…)

Regards  
Henrik

---

<div class="post-metadata">

**Author:** ![dzusan](https://avatars.discourse-cdn.com/v4/letter/d/43a26b/32.png) [@dzusan](https://discourse.joplinapp.org/u/dzusan)\
**Post date:** [21 March 2021 19:57 UTC](https://discourse.joplinapp.org/t/self-signed-ssl-certificate-ok-on-desktop-but-not-android/9341/7 "2021-03-21T19:57:49Z")

</div>

I tried to install Joplin Server on my home server via Nginx proxy. I created a self-signed SSL certificate, enabled the "Ignore TLS certificate errors" option on my two Joplin desktop clients, and it syncronized over the internet with no problem.

But on my OnePlus 6 I just get a “Network request failed” too! What I tried:

1. added .crt to Android certificate storage (after this chrome opened Joplin Server login link without problem)
2. used this instruction: [Self-signed certificate for Android devices](https://wiki.archlinux.org/index.php/Nextcloud#Self-signed_certificate_for_Android_devices)

But the problem was not solved. I was forced to get a free certificate for ZeroSSL and then it worked.

---

<div class="post-metadata">

**Author:** ![iks](https://avatars.discourse-cdn.com/v4/letter/i/c77e96/32.png) [@iks](https://discourse.joplinapp.org/u/iks)\
**Post date:** [24 March 2021 08:51 UTC](https://discourse.joplinapp.org/t/self-signed-ssl-certificate-ok-on-desktop-but-not-android/9341/8 "2021-03-24T08:51:07Z")

</div>

I have had this issue some weeks ago after a server migration (and only on my HTC 10 while all desktop clients was synching well) in the end the "Network request failed" error disappeared when I configured correctly OCSP stapling, I'm using letsencrypt certs btw, so I'm wondering if the same can apply to self signed certs too.

---

<div class="post-metadata">

**Author:** ![JackGruber](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/jackgruber/32/3231_2.png) [@JackGruber](https://discourse.joplinapp.org/u/JackGruber)\
**Post date:** [24 March 2021 10:23 UTC](https://discourse.joplinapp.org/t/self-signed-ssl-certificate-ok-on-desktop-but-not-android/9341/9 "2021-03-24T10:23:16Z")

</div>

Unfortunately, self-sign certificates do not currently work on mobile devices as there is no option to ignore ssl errors at the moment.

---

<div class="post-metadata">

**Author:** ![kristoferb](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/kristoferb/32/12729_2.png) [@kristoferb](https://discourse.joplinapp.org/u/kristoferb)\
**Post date:** [14 February 2022 20:23 UTC](https://discourse.joplinapp.org/t/self-signed-ssl-certificate-ok-on-desktop-but-not-android/9341/10 "2022-02-14T20:23:40Z")

</div>

I had this same issue today with a self-signed certificate. Joplin for Android now has the Ignore SSL Errors and that worked for me. Everything is syncing. I also added the path to the certificate on the Joplin desktop app and that resolved the issue there.

---

<div class="post-metadata">

**Author:** ![Daeraxa](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/daeraxa/32/6172_2.png) [@Daeraxa](https://discourse.joplinapp.org/u/Daeraxa)\
**Post date:** [14 February 2022 20:48 UTC](https://discourse.joplinapp.org/t/self-signed-ssl-certificate-ok-on-desktop-but-not-android/9341/11 "2022-02-14T20:48:40Z")

</div>

Closed on 14 February 2022 20:48 UTC