# Node-RED SSL using Letsencrypt & Certbot

**URL:** <https://discourse.nodered.org/t/node-red-ssl-using-letsencrypt-certbot/17606>\
**Category:** Share Your Projects\
**Tags:** security\
**Created:** [6 November 2019 20:22 UTC](https://discourse.nodered.org/t/node-red-ssl-using-letsencrypt-certbot/17606 "2019-11-06T20:22:22Z")\
**Posts on this page:** 1\
**Showing post:** 45

<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:** [8 December 2020 22:16 UTC](https://discourse.nodered.org/t/node-red-ssl-using-letsencrypt-certbot/17606/45 "2020-12-08T22:16:28Z")

</div>

As @BartButenaers mentions above, don't forget about the `httpsRefreshInterval` which has been introduced into node-RED since v1.1.0.

A bit of background....

By default, node-RED reads in the SSL certificates **only** when node-RED starts, so even though you have renewed your certificates with certbot. Node-RED will not load them until it has been restarted.

To deal with this, if you use `httpsRefreshInterval` in your `settings.js` file, then the certificates will be reloaded into the running system automatically, avoiding the need to restart the system.

See [Securing Node-RED : Node-RED](https://nodered.org/docs/user-guide/runtime/securing-node-red#refreshing-https-certificates)

---

_[View the full topic](https://discourse.nodered.org/t/node-red-ssl-using-letsencrypt-certbot/17606)._