# Private cert possible causing "unable to get issuer cert locally" error

**URL:** <https://discourse.nodered.org/t/private-cert-possible-causing-unable-to-get-issuer-cert-locally-error/71221>\
**Category:** General\
**Created:** [25 November 2022 00:53 UTC](https://discourse.nodered.org/t/private-cert-possible-causing-unable-to-get-issuer-cert-locally-error/71221 "2022-11-25T00:53:58Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ftabat](https://avatars.discourse-cdn.com/v4/letter/f/a9a28c/32.png) [@ftabat](https://discourse.nodered.org/u/ftabat)\
**Post date:** [25 November 2022 00:53 UTC](https://discourse.nodered.org/t/private-cert-possible-causing-unable-to-get-issuer-cert-locally-error/71221/1 "2022-11-25T00:53:58Z")

</div>

Hi,

We had a perfectly working flow(in test) until last month when corporate issued us a new cert for our test server. Our prod will still be using a public cert until it expires.  
Now that we're having this issue, we're suspecting that it's because the newly issued cert is a self signed cert while the one we had when our flow was still working was a public cert.  
Can anyone confirm whether there is actually a limitation in node-red caused by the type of cert being used?

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [25 November 2022 01:15 UTC](https://discourse.nodered.org/t/private-cert-possible-causing-unable-to-get-issuer-cert-locally-error/71221/2 "2022-11-25T01:15:35Z")

</div>

> [@ftabat](#):
>
> Can anyone confirm whether there is actually a limitation in node-red caused by the type of cert being used?

I don't believe that Node-RED has any such limitations. However, browsers can certainly not be happy about invalid or local certs (one's not certified by a public CA).

---

<div class="post-metadata">

**Author:** ![ftabat](https://avatars.discourse-cdn.com/v4/letter/f/a9a28c/32.png) [@ftabat](https://discourse.nodered.org/u/ftabat)\
**Post date:** [25 November 2022 10:35 UTC](https://discourse.nodered.org/t/private-cert-possible-causing-unable-to-get-issuer-cert-locally-error/71221/3 "2022-11-25T10:35:04Z")

</div>

Because we didn't change anything except the certs, that's the only culprit we can think about. What would you recommend we should check?

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [25 November 2022 11:36 UTC](https://discourse.nodered.org/t/private-cert-possible-causing-unable-to-get-issuer-cert-locally-error/71221/4 "2022-11-25T11:36:43Z")

</div>

It does, the http request node used to have an option to ignore cert issues, not sure why this was removed. Now you need to inject rejectUnauthorized:false to skip verification. See the payload options in the help tab.

---

<div class="post-metadata">

**Author:** ![ftabat](https://avatars.discourse-cdn.com/v4/letter/f/a9a28c/32.png) [@ftabat](https://discourse.nodered.org/u/ftabat)\
**Post date:** [27 November 2022 09:46 UTC](https://discourse.nodered.org/t/private-cert-possible-causing-unable-to-get-issuer-cert-locally-error/71221/5 "2022-11-27T09:46:01Z")

</div>

This worked! Thank you!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [11 December 2022 09:46 UTC](https://discourse.nodered.org/t/private-cert-possible-causing-unable-to-get-issuer-cert-locally-error/71221/6 "2022-12-11T09:46:34Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.