I haven't looked at this for a while, but I seem to recall that the file ownership would not be correct, and could not be read and used by node-RED, that's why they are changed in the script (as the certificates were moved).
Changing the owner in the original location seemed to upset certbot
I'll check tonight, and also have a look at your other point later Brian, when I can get to a laptop.
Hi Brian, just re-read the thread Node-RED SSL using Letsencrypt & Certbot where I wrote some time ago about the ownership issue that I had problems with, and the reason why I used the script. but if creating symlinks to the certificates in the 'live' folder works, then great.
PS remember that the 'certificates' in the 'live' folder are actually symlinks to the actual certificates which are stored in the 'archive' folder
Yes, I mentioned about node-RED no longer needing a restart in the same thread.
I'll edit the post and remove the reference to node-red-restart now that most people are using node-RED v1.1.0 or newer, but keep the script, and at least users will have the option to use it, use symlinks, or whatever.
Yes, I noted that. I did though wonder if something had changed since then. I looked on 2 different systems and the certificates should be readable globally.
Yes, I appreciate the live is just a symlink created by the certbot renewal. Note I create a link to the folder not the files. The system in use is a little 'quirky' so I cannot test if it works for a 'normal' Pi setup.
Sorry, I meant the Symlink I created into the ~/.node-red folder was done as a folder symlink (rather than each file). That worked and I then tried picking up the files directly in settings.js, and that worked as well.