For my previous node-red-contrib-ui-web-push node, Chrome requires me to have an SSL connection to Node-RED with a trusted certificate.
So I really needed to use LetsEncrypt, to have free trusted certificates. There are a lot of ways to do that... However I wanted to have a way to allow users (with less technical background) to request LetsEncrypt certificates, fully integrated into their familiar Node-RED environment.
But near the end of my developments of node-red-contrib-acme-client, unfortunately suddenly it started becoming complex
So this this node is NOT READY FOR USAGE, since some fundamental issues need to be solved and simplified somehow. But I'm stuck, so I would really appreciate if some folks with technical background could read through my readme page. It contains a lot of exclamation marks...
The two major issues summarized:
For Node-RED installations that are public accessible, a HTTP-01 challenge is being used. To implement that challenge, I need to make a file (which I have received from Letsencrypt) available for Letsencrypt again at port 80 (see last section in my readme page) :
For Node-RED installations that are only private accessible, I should implement a DNS-01 challenge. The good news is that Acme.js (which I use under the cover) should support this, but the bad news is that I have no clue at all how I could integrate this in a solution without manual user interactions. Perhaps not possible?? No idea again, even after some explanation from @TotallyInformation
So all help is welcome for this node, which would assist users in securing their environment...
!!! THANKS A LOT !!!