# 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:** 1\
**Showing post:** 5

<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`

---

_[View the full topic](https://discourse.joplinapp.org/t/self-signed-ssl-certificate-ok-on-desktop-but-not-android/9341)._