Node-red version 3.1.15 on Dell 9020m running on Mint 20.3
Mosquitto 2,0.11 running on same server as Node-red.
Dell 9020m eth0 192.168.1.4 and wlp2s0 192.168.1.5 both static. Finally Nordlynx for remote access..
This configuration has been has been in place for 6 months with no problems. I found today Node-red can not connect to mqtt using 192.168.1.4 but 127.0.0.1 still works. Remote devices such Android Cell, or Wifi switchs running Tasmota have no issue connecting to the MQTT Broker on 192.168.1.4 The Android device access MQTT broker via Nordlynx it has no problems.
I have tried publishing/subscribing from other clients using mosquito cli interface with no problems.
I am kind of at loss of why node-red on the 9020 can only access mqtt broker via 127.0.0.1, but 24 hours ago it was fine. I could go change all the nodes that use 192.168.1.4 and switch to 127.0.0.1 that would to solve issue but not explain why it occurred in the first place.
Except for reboot of the 9020m no recent changes have been made to the node-red or mosquitto configuration.
Does the Dell have a static IP address? ie is it still 192.168.1.4?
Not suggesting this is the right way to resolve the issue but you should only need to change the mqtt broker config node[s], which there might only be one of, not all the mqtt-in and mqtt-out nodes.
Yes it still has the 192.168.1.14 address...
I am going to make the change to 127.0.0.1 that I will get my automation system back on line. Then come back build a test node to verify that access via 192.168.1.4 still fails. Use that node do some more testing, to see if I can resolve the mystery
I had a similar issue and found listener 1883 was missing from the end of the mosquitto.conf file (even though I thought Mosquitto used port 1883 by default).
listener 1883
allow_anonymous true
If you're using authentication, set allow_anonymous false and configure username/password instead.
You will need to restart Mosquitto after making any changes.
sudo systemctl restart mosquitto
Note:
If you see: bind_address 127.0.0.1 in the conf file then you’re only listening on localhost
You need to remove or comment it out or change it to your LAN IP: bind_address 0.0.0.0
If you are using services on the same device, you absolutely SHOULD be using the localhost address - otherwise, it is likely that you are tromboning your network data out and back in again which will be adding a lot of overhead.
You should also be making sure that nothing from the outside can get in - unless you explicitly want it to.
