# Issue with SSL Certificate

**URL:** <https://forum.inductiveautomation.com/t/issue-with-ssl-certificate/87936>\
**Category:** Ignition\
**Created:** [March 27, 2024, 12:39am UTC](https://forum.inductiveautomation.com/t/issue-with-ssl-certificate/87936 "2024-03-27T00:39:24Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![jlteel](https://avatars.discourse-cdn.com/v4/letter/j/c67d28/32.png) [@jlteel](https://forum.inductiveautomation.com/u/jlteel)\
**Post date:** [March 27, 2024, 12:39am UTC](https://forum.inductiveautomation.com/t/issue-with-ssl-certificate/87936/1 "2024-03-27T00:39:24Z")

</div>

I'm having trouble getting my system to recognize a valid SSL certificate. You can see from the image that the certificate is installed and valid, but my browser does not trust it for some reason. I know I dealt with this a couple years ago when I went through the cert process, but I can't remember what I need to do to resolve this. Any help?

 ![Xnip2024-03-26_17-36-43](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/5/f57bdd3e057f576b3431e91dcc0499db98000bc8.png)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 27, 2024, 12:47am UTC](https://forum.inductiveautomation.com/t/issue-with-ssl-certificate/87936/2 "2024-03-27T00:47:49Z")

</div>

Can you upload the certificate here so we can look at it?

Looking at the URL you're accessing the Ignition Gateway at I'm skeptical that it's listed in the certificate.

---

<div class="post-metadata">

**Author:** ![jlteel](https://avatars.discourse-cdn.com/v4/letter/j/c67d28/32.png) [@jlteel](https://forum.inductiveautomation.com/u/jlteel)\
**Post date:** [March 27, 2024, 2:20pm UTC](https://forum.inductiveautomation.com/t/issue-with-ssl-certificate/87936/3 "2024-03-27T14:20:58Z")

</div>

Thanks, @Kevin.Herron. Forgive my ignorance, but I installed the certificate a year and a half ago, and can't remember how to go about retrieving it so I can post it here. Can you please point me in the right direction?

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [March 27, 2024, 2:24pm UTC](https://forum.inductiveautomation.com/t/issue-with-ssl-certificate/87936/4 "2024-03-27T14:24:32Z")

</div>

Does your computer trust the CA (nwasco-SRV-CERT-CA)? I'd check the not-secure icon in the browser and my guess is that your computer doesn't trust the root CA, so inherently it won't trust the certificate either. If the CA root certificate is pushed out to you through group policy on the domain server (assuming this is Windows), make sure your system is getting it (may have to reach out to IT if they manage it).

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 27, 2024, 2:39pm UTC](https://forum.inductiveautomation.com/t/issue-with-ssl-certificate/87936/5 "2024-03-27T14:39:33Z")

</div>

You should be able to just pull it out of the browser. You should also be able to click around somewhere to find out more about what it doesn't like about this certificate.

> [@michael.flagler](#):
>
> Does your computer trust the CA (nwasco-SRV-CERT-CA)? I'd check the not-secure icon in the browser and my guess is that your computer doesn't trust the root CA,

I think Michael is on to something here. I didn't notice at first that your certificate is signed by an internal CA and not a public CA, so this is also worth looking into.

---

<div class="post-metadata">

**Author:** ![jlteel](https://avatars.discourse-cdn.com/v4/letter/j/c67d28/32.png) [@jlteel](https://forum.inductiveautomation.com/u/jlteel)\
**Post date:** [March 27, 2024, 3:42pm UTC](https://forum.inductiveautomation.com/t/issue-with-ssl-certificate/87936/6 "2024-03-27T15:42:21Z")

</div>

Ok, I think you guys are on to something here. Thanks for your help. I'll probably just get new certificates from a public CA.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 27, 2024, 3:53pm UTC](https://forum.inductiveautomation.com/t/issue-with-ssl-certificate/87936/7 "2024-03-27T15:53:32Z")

</div>

> [@jlteel](#):
>
> I'll probably just get new certificates from a public CA.

You can only do this for a server accessible at a public address; the one in your screenshot appears to be internal.

---

<div class="post-metadata">

**Author:** ![jlteel](https://avatars.discourse-cdn.com/v4/letter/j/c67d28/32.png) [@jlteel](https://forum.inductiveautomation.com/u/jlteel)\
**Post date:** [March 27, 2024, 4:26pm UTC](https://forum.inductiveautomation.com/t/issue-with-ssl-certificate/87936/8 "2024-03-27T16:26:17Z")

</div>

Ok, it sounds like the issue is that my computer doesn't trust the root CA. But I have no idea what to do about that.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 27, 2024, 4:27pm UTC](https://forum.inductiveautomation.com/t/issue-with-ssl-certificate/87936/9 "2024-03-27T16:27:08Z")

</div>

It sounds like you need to work with your IT department. They would have been in the loop to issue this certificate in the first place.

---

<div class="post-metadata">

**Author:** ![jlteel](https://avatars.discourse-cdn.com/v4/letter/j/c67d28/32.png) [@jlteel](https://forum.inductiveautomation.com/u/jlteel)\
**Post date:** [March 27, 2024, 5:36pm UTC](https://forum.inductiveautomation.com/t/issue-with-ssl-certificate/87936/10 "2024-03-27T17:36:39Z")

</div>

Got it, thanks.

---

<div class="post-metadata">

**Author:** ![jlteel](https://avatars.discourse-cdn.com/v4/letter/j/c67d28/32.png) [@jlteel](https://forum.inductiveautomation.com/u/jlteel)\
**Post date:** [March 27, 2024, 5:43pm UTC](https://forum.inductiveautomation.com/t/issue-with-ssl-certificate/87936/11 "2024-03-27T17:43:09Z")

</div>

I'm using a Mac. All I had to do was export the certificate from my browser, import it into my System Keychain, and trust it. Thanks to everyone for pointing me in the right direction.
