# Pull request proposal: automatic certificate renewal

**URL:** https://discourse.nodered.org/t/pull-request-proposal-automatic-certificate-renewal/21282
**Category:** Feature Requests
**Created:** [4 February 2020 21:26 UTC](https://discourse.nodered.org/t/pull-request-proposal-automatic-certificate-renewal/21282 "2020-02-04T21:26:45Z")
**Posts on this page:** 1
**Showing post:** 15

<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: [19 March 2020 21:36 UTC](https://discourse.nodered.org/t/pull-request-proposal-automatic-certificate-renewal/21282/15 "2020-03-19T21:36:46Z")

</div>

Do we really need the two alternative https settings including in settings.js? Why not just the 'function' version.

Case 1 - New installation  
Any new installation would use the 'new' settings.js file which only contained the 'function https'.

Case 2 - node-RED updates  
Because settings.js is not overwritten when updating or re-running the script, existing users would continue to use the 'none-function' version that remains in their existing settings file.

Users using the 'old' settings file would be able to easily convert to the function version without replacing settings.js, by a simple edit, that could be described in the user guide/blog.

(I just know that the next post will contain Case 3, Case 4, etc 😉)

---

_[View the full topic](https://discourse.nodered.org/t/pull-request-proposal-automatic-certificate-renewal/21282)._