mqtt-in node constantly not connected, when i check the setting i found password has been modify. the length of origin setting pw is 23, when i check it, it become 6. is there limit on pw length on mqtt-in node?
The password is stored encrypted server side in a node-red config file and is NOT returned to the client side (frontend) editor. You are shown the dots/stars ONLY to represent a password is actually set.
If the password really is being changed, check your logs for suspicious activity. Is you node-red accessible over the internet (i.e. can the editor be accessed outside of your LAN)?
Do you mean this field in the MQTT-In node?
That is what it is supposed to show.
Have you tried a simple back-to-back test with MQTT-Out and MQTT-In ?
thanks for the answer. if the pw is correct then i have no idea what go wrong that rendering fail to connect mqtt server. the server is available i connected it using other tool. but the node-red node fail.
thanks for your answer. since the pw is correct then i lost what go wrong rendering fail to connect the server. the server is attested.
where is node-red installed (direct on OS? inside docker? HA plug in?)
where is the broker installed (same computer/device? in a docker container? somewhere else on your network or the internet?)
does the broker expect a specific client ID?
Try connecting to an online test broker: blog/en/202111/popular-online-public-mqtt-brokers.md at main · emqx/blog · GitHub
Try installing node-red-node-ping & see if your node-red can ping the IP/hostname of the broker.
o i made a silly mistake. the pw input is wrong. i copy the pw from somewhere and it was wrong. i try to copy from origin text, it work now. thanks alot. by the way i install node-red on OS.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
