# Let's encrypt root certificate change

**URL:** <https://discourse.nodered.org/t/lets-encrypt-root-certificate-change/45866>\
**Category:** General\
**Created:** [18 May 2021 15:52 UTC](https://discourse.nodered.org/t/lets-encrypt-root-certificate-change/45866 "2021-05-18T15:52:47Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [18 May 2021 18:33 UTC](https://discourse.nodered.org/t/lets-encrypt-root-certificate-change/45866/6 "2021-05-18T18:33:21Z")

</div>

> [@BartButenaers](#):
>
> both the server certificate and the Letsencrypt intermediate certificate are stored into the cert.pem file. I should have a look whether clients with a new/old root certificate would run into troubles, due to an incomplete chain...

Yes, I had similar problems about 18 months ago, [so I always advise users](https://discourse.nodered.org/t/node-red-ssl-using-letsencrypt-certbot/17606/58) to use the `fullchain.pem` certificate instead of the `cert.pem` to complete the chain.  
The Letsencrypt Leader - Juergen Auer, said why this was necessary (for node-RED users) [in this thread.](https://community.letsencrypt.org/t/letsencrypt-chain-pem-or-trusted-root-list-cert/105921/10)

---

_[View the full topic](https://discourse.nodered.org/t/lets-encrypt-root-certificate-change/45866)._