# SSl (Certificate Validation)

**URL:** <https://wazo-platform.discourse.group/t/ssl-certificate-validation/1486>\
**Category:** Development: API/Events\
**Created:** [April 20, 2024, 6:28am UTC](https://wazo-platform.discourse.group/t/ssl-certificate-validation/1486 "2024-04-20T06:28:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sri\_555](https://avatars.discourse-cdn.com/v4/letter/s/dec6dc/32.png) [@Sri\_555](https://wazo-platform.discourse.group/u/Sri_555)\
**Post date:** [April 20, 2024, 6:28am UTC](https://wazo-platform.discourse.group/t/ssl-certificate-validation/1486/1 "2024-04-20T06:28:27Z")

</div>

Hi There:  
I am developing a softphone using react native with the help of [GitHub - wazo-platform/wazo-react-native-demo: A simple demonstration of Wazo's SDK with React Native](https://github.com/wazo-platform/wazo-react-native-demo) this wazo demo project.  
When I tried to hit the

```
Wazo.Auth.init();
Wazo.Auth.setHost("192.168.87.135");
try {     
  session = await Wazo.Auth.logIn("root", "sri55533");
} catch (e) {
  console.log("Err",e)      
}  

```

**session = await Wazo.Auth.logIn(“root”, “sri55533”);**

API responds with a catch error that

**LOG Err [TypeError: Network request failed]**

While debugging it in the network, the results are

 ![network_image_01](https://global.discourse-cdn.com/free1/uploads/wazo_platform/original/1X/cd433655e67dee469b9dd0563cdb7822c7282ff6.jpeg)  
 ![network_image_02](https://global.discourse-cdn.com/free1/uploads/wazo_platform/original/1X/a49c35f7e3d9ce752a2a29e4cd97a45599401109.jpeg)

**What might have gone wrong, and how to resolve it?**  
I also added a self-signed SSL certificate but it does not work

---

<div class="post-metadata">

**Author:** ![julienfr](https://yyz2.discourse-cdn.com/free1/user_avatar/wazo-platform.discourse.group/julienfr/32/797_2.png) [@julienfr](https://wazo-platform.discourse.group/u/julienfr)\
**Post date:** [April 20, 2024, 9:22am UTC](https://wazo-platform.discourse.group/t/ssl-certificate-validation/1486/2 "2024-04-20T09:22:36Z")

</div>

Hi,

I use VirtualBox to have a Wazo platform server, for test and dev.

I have a web app, using quite the same code for auth.

I start my Wazo server, i start my dev app.

When i try to log to my web app (with chrome), i got:

 ![image](https://global.discourse-cdn.com/free1/uploads/wazo_platform/original/1X/a4187600318bc03ad33f67f55333fdc217dc680a.png)

then, i open a new tab in chrome, go to the wazo ip server address:

 ![image](https://global.discourse-cdn.com/free1/uploads/wazo_platform/original/1X/17ab02cf27a037fa91da96906d305a266272acab.png)

Then click on “avanced parameters”, then,

 ![image](https://global.discourse-cdn.com/free1/uploads/wazo_platform/original/1X/c801a47e4bc6008f3f17f21fd4974189437d32c4.png)

i click “continue to the website”

i go back to my dev app, and tada, auth is working !

---

<div class="post-metadata">

**Author:** ![Sri\_555](https://avatars.discourse-cdn.com/v4/letter/s/dec6dc/32.png) [@Sri\_555](https://wazo-platform.discourse.group/u/Sri_555)\
**Post date:** [April 20, 2024, 10:32am UTC](https://wazo-platform.discourse.group/t/ssl-certificate-validation/1486/3 "2024-04-20T10:32:30Z")

</div>

Hi there:

Sorry for creating multiple topics!!!.  
Anyway, thanks for your reply😊

This article helps me to overcome the issue of SSL validation in my app.

> **[How to Ignore SSL for React Native (Android/iOS)](https://medium.com/@rushitjivani/how-to-ignore-ssl-for-react-native-android-ios-4942e10ea667)**
>
> Secure data transfer over the Internet is a modern need for mobile data, SSL pinning is a mechanism used to satisfy this requirement: It…

---

<div class="post-metadata">

**Author:** ![quintana](https://yyz2.discourse-cdn.com/free1/user_avatar/wazo-platform.discourse.group/quintana/32/916_2.png) [@quintana](https://wazo-platform.discourse.group/u/quintana)\
**Post date:** [April 22, 2024, 11:53am UTC](https://wazo-platform.discourse.group/t/ssl-certificate-validation/1486/5 "2024-04-22T11:53:27Z")

</div>

It’s not possible to have websocket connexion without a valid certificate.