I am finally trying to get my feet wet in node-red. Setting up our AR1/S1 has been… interesting…
Anyway, I think I have all of the api keys and SSL certificates created/installed, but now I am stuck. I have followed all of the directions that I could find (some of which are wrong/incomplete) and am now stuck at "cannot open file at '/home/dev/.node-red/certs/cert.192.168.1.240.crt'."
Please help.
There is several things possible, but the name of the certificate is a bit troubling for me because of the many dots it may be reading “cert.192” instead of a dot cert or pem file, try renaming cert to “cert1921681240.crt”
Let us know…
And it says should be pem format, which I have used with no issues, I haven’t used a cert file…
I actually followed these instructions:
SNAP PAC Security Certificates for Node-RED
and these:
SNAP PAC SSL Certificate Installation
Is there any special reason you are using HTTPS?
If they are on the same network, you could just use HTTP and the key pair?
Just trying to follow directions…
Yeah, try http instead of HTTPS, that solved a lot of “issues” in our rough start with node red, now we use node red in the PR1 for several things.
So… set controller TCP port back to 80, https: disabled?
That’s the way I usually get it going. Its always on the same network and I don’t need the overhead of HTTPS, so yeah, in PAC Manager, turn of HTTPS, set the port back to 80, save to flash, then restart the PAC Controller.
Then in Node-RED just set it to HTTP and put the key in and you should be up and running.
This may be very basic but worth asking… did you verified the certificate path? are you 100% is there?
Try uploading the certificates through Node-RED admin. Go to https://192.168.1.121:3000, select Certificates on the left hand side, then upload your files there. This should put the file on the correct path, then we can check to make sure the certificates were generated as expected.
http is working. I might give https another shot later, but it’s not really necessary (it’s all on an internal network).
Just like Nick said, I followed the instructions and just like him, I got the green text OK and then when rebooted, it comes back showing the same files I had browsed for, but says in red, “Not loaded using default.”
I am doing this for a PC to PC node red install. I have NR installed on a Linux distro with ARC and Grafana, and then I have a Pac S2 that I am configuring and programming with a seperate windows machine. I went through the whole cert/key generation process, and that worked fine, then when I tried to install the certs on S2, the preceding happens. NR works perfect when the S2 is http, but when I change to https and 443 and save it and reboot, I cannot connect to it from same windows PC to see the certs page as a test of SSL.
Here is the text from the command window I used:
…+++++++++++++++++++++++++++++++++++++++…+…+…+…+…+++++++++++++++++++++++++++++++++++++++…+…+…+..+…+…+…+…+…+…+…+…+.+…+…+…++++++
…+.+…+…+…+…+…+…+…+.+..+.+++++++++++++++++++++++++++++++++++++++…+…+.+…+…+.+…+…+..+++++++++++++++++++++++++++++++++++++++…+…+…+…+.+..+…+…+…+.+…+…+…+…+…+…+.+…+…+…+…+.+…+…+..+…+…+…+…+…+…+…+…+…+…+.+…+.+…+…+…+…+.+…+…+…+…+…+…+…+…+.+..+…+.+…+…+…+..+…+.+…+…+…+..+…+.+…+…+…+…+…+..+…+.+…+…+…+..+…+…+…+…+…+…+…+.+..+…+…+.+..+…+…+…+…+…+…+…+..+…+…+…+…+…+…+…+.+…+…+…+..+.+…+…+…+…+…+…+…+…+.+..+…+.+…+..+.+…+…+…+…+…+…+…+..+…+…+…+…+…+.+…+.+…+…+..+…+…+..+.+…+…+…+…+…+…+…+…+.+…+..+…+…+…+…+.+…+…+…+…+…+.+..+…+…+..+…+..+…+…+…+…+…+…+..+…+.+…+..+…+…+…+…+…+…+…+..+.+…+.+…+…+.+…+…+…+..+…+.+…+…+.+…+…+…+…+…+…+…+…+..+…+…+…+..+…+.+…+…+…+…+…+…+…+..+…+.+…+.+…+…+…+…+…+.+..+…+..+…+…+…+…+…+…+…+…+…+…+…+…++++++
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter ‘.’, the field will be left blank.
Country Name (2 letter code) [AU]:US
State or Province Name (full name) [Some-State]:MO
Locality Name (eg, city) :Pacific
Organization Name (eg, company) [Internet Widgits Pty Ltd]:The Automate Co.
Organizational Unit Name (eg, section) :Engineering
Common Name (e.g. server FQDN or YOUR name) :172.16.255.10
Email Address :barrett@automateco.com
C:\Users\barre\Documents\DownLoad\Open SSL Certs>“C:\Program Files\OpenSSL-Win64\bin\openssl.exe” rsa -in privkey.172.16.255.10.key -out privkey.172.16.255.10.key
writing RSA key
Finally got it…
After numerous attempts and searching all over the place, I finally managed to get the SSL cert/key pair installed on an Pac S2.
Turns out if you go to OpenSSL, they do have ver1.1 available, but not windows friendly and you have to search for it…I found the windows version 1.1 at:
https://download.firedaemon.com/FireDaemon-OpenSSL/openssl-1.1.1w.zip
If you just goto OpenSSL and download any other version, such as 3 or 4, the certs will not load in Pac. They will appear to load, and you’ll get the green OK after clicking submit, but after it automatically reboots, the text turns red as if you hadn’t submitted it yet. The files you just pointed to will still be loaded in the file browser boxes, but they never actually loaded during the reboot.
Another thing to be aware of, is they recently fixed the more recent pac fw versions where there was a bug preventing the loading as well. It is fixed in fw 10.7a and now works, once you realize you’re trying to load the wrong version of OpenSSL for instance.
It turns out that tech support tested this on fw 10.7 and found that OpenSSL 4.01 indeed did have a problem loading. He sent this into developers to check out.
