Hi folks, A few months ago @Paul-Reed shared with us a very interesting article about automatic renewal of certificates using Letsencrypt. However from that article it appeared that you have to restart Node-RED, every time a certificate is renewed (in the key file): [image] Would be nice if we c…

[image] BartButenaers: It is a pity that the existing ' https ' property isn't a function. Because now you have to specify both file paths (privkey.pem and cert.pem) twice in the settings Please disregard if this is an ill-thought-out suggestion, but can't the certs be retrieved from settings…

Paul, Currently the 'https' has been setup like this: https: { key: fs.readFileSync('privkey.pem'), cert: fs.readFileSync('cert.pem') }, As soon as the settings.js file is read by Node-RED, all the code inside will be executed (a.o. the readFileSync functions). From then …

In case you have a custom developed node, you have access to the RED object which contains the server (RED.server). So you could implement certificate updates there... The RED object also holds the settings. You could even create a simple custom node just for that purpose - Such a node wouldn't eve…

[image] pelis: The RED object also holds the settings. Hi @pelis , Yes that indeed was a problem in my first proposal: All the nodes received (at startup) a RED.settings instance, which contained the original (pre-loaded) content of the certificate.pem and privatekey.pem files. When I loade…

I assume that if this PR was added to node-RED, it would then open the door for the development that you hinted at in this post; [image] Node-RED SSL using Letsencrypt & Certbot Share Your Projects Hi Ioan, I have no knowledge about certbot, but I'm about to announce a n…

It’s half term down here, so Nick is on vacation for a while

At this point, there has been no pr raised for us to review or discuss. The proposal still doesn't quite fit the "clean API" test for me. I don't see why a user should provide the certs in two different ways - both under the HTTPS property and the proposed new refresh function. I think it would be …

[image] knolleary: both under the HTTPS property and the proposed new refresh function Hey Nick, Seems that I have not interpreted your "I'd suggest a design that allows the user to provide a function that Node-RED will call at the desired" correctly. Thought you meant a separate function. …

[image] knolleary: I think it would be better if it were all under the https setting and the cert properties can either be the cert content itself (as is today), or a function. If it's a function and a refresh interval is also specified under the HTTPS property, then we will call it as needed. …

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 …

Node-RED

Node-RED Forum

Pull request proposal: automatic certificate renewal

Core Development Feature Requests

Topic		Replies	Views
Node-RED SSL using Letsencrypt & Certbot Share Your Projects security	52	22036	9 May 2021
[ANNOUNCE] node-red-contrib-letsencrypt : beta version Share Your Nodes	64	4532	4 June 2020
Unable to secure Node-RED General	16	2478	23 October 2018
[ANNOUNCE] node-red-contrib-certificate-grabber: beta Share Your Nodes	18	843	17 July 2022
Updating settings.js General	4	1464	26 February 2020

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Pull request proposal: automatic certificate renewal

Related topics