May-15th-2018, 02:55 PM
Meanwhile I made tests across the web site https://test.mosquitto.org/ which hosts a secured and public MQTT server for everybody that can be used for test purposes.
In accordance with the description provided on this page I configured my MQTT node-red node that comes in the "hilschernetpi/netpi-nodered-fieldbus" by default. I generated a client.key file on my windows machine as described using openssl and I used it on the web page to generate the certificate file "client.crt" and I was using the provided CA certificate "mosquitto.org.crt" as well and inserted all 3 files in the upload dialog and configured the server as "test.mosquitto.org:8883"
Immediately after deploy the node-red MQTT output node goes into connected state. I also configured a input node as well and send data to a topic "test" which I was receiving back to my flow in this input node when I injected a test pattern.
So I cannot confirm what you are seeing.
In accordance with the description provided on this page I configured my MQTT node-red node that comes in the "hilschernetpi/netpi-nodered-fieldbus" by default. I generated a client.key file on my windows machine as described using openssl and I used it on the web page to generate the certificate file "client.crt" and I was using the provided CA certificate "mosquitto.org.crt" as well and inserted all 3 files in the upload dialog and configured the server as "test.mosquitto.org:8883"
Immediately after deploy the node-red MQTT output node goes into connected state. I also configured a input node as well and send data to a topic "test" which I was receiving back to my flow in this input node when I injected a test pattern.
So I cannot confirm what you are seeing.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
