Nodemcu cannot connect to mqtt

General
24

can you suggest me the way to solve this problem.

25

are they set for 192.168.43.160?

What MQTT broker are you running?

26

Hello Friend.

Are you sure the messages have not been exchanged?

Remember that to view the debug node data you need to open the debug node menu.

It is the beetle on the upper right side.

Try this ...

27

Any IP , port set 1883 , mosquitto 2.0.4 for windows 64

28

I changed the mqtt server from my ip to localhost and done the test and its successful

IMG_20210106_100610
IMG_20210106_1006104000Ɨ3000 1.71 MB

29

Thanks Friend .. I was wrong and not checked the debug node menu

30

Looks Mqtt is perfectely working but why my nodemcu is unable to connect to mqtt..
What could be the reason ..

31

If I use the ip address 192.168.43.160 as server then mqtt not connect , but if i use server as localhost the mqtt connected and the test is successful .. How can solve the issue, looks like the something is wrong with ip address , but I checking my ip by cmd ipconfig .. and in firewall also allowed .. what else do i need to check i am not getting .

My ip configuration is set to auto , not manual , if that could be the reason ?

32

Yes, if the IP of the Broker changed then it wouldn't connect and if the IP of the Broker changed and the NodeMCU points to the old IP, then the Nodemcu would not be able to connect.

33

But with the current ip also not connect .. if i modify the ip everywhere (arduino program, node flows) and put the present ip , still can't connect

34

is the broker configured to only listen to local connections ?

35

how to check that ?

36

you need to look at the documentation of mosquitto 2.0.4 for windows 64

I think it may be the listener port option:

listener port [bind address/host/unix socket path]

Listen for incoming network connection on the specified port. A second optional argument allows the listener to be bound to a specific ip address/hostname. If this variable is used and neither the global bind_address nor port options are used then the default listener will not be started.

The bind address/host option allows this listener to be bound to a specific IP address by passing an IP address or hostname. For websockets listeners, it is only possible to pass an IP address here.

On systems that support Unix Domain Sockets, this option can also be used to create a Unix socket rather than opening a TCP socket. In this case, the port must be set to 0, and the unix socket path must be given.

This option may be specified multiple times. See also the mount_point option.

Not reloaded on reload signal.

37 
# listener port-number [ip address/host name/unix socket path]
#listener

# By default, a listener will attempt to listen on all supported IP protocol
# versions. If you do not have an IPv4 or IPv6 interface you may wish to
# disable support for either of those protocol versions. In particular, note
# that due to the limitations of the websockets library, it will only ever
# attempt to open IPv6 sockets if IPv6 support is compiled in, and so will fail
# if IPv6 is not available.
#
# Set to `ipv4` to force the listener to only use IPv4, or set to `ipv6` to
# force the listener to only use IPv6. If you want support for both IPv4 and
# IPv6, then do not use the socket_domain option.
38

It saying it is open to all ip's

39

it is saying it is listening to all ip's

40

have you reveriied that that is still the IP of the windows machine?

41

The Ip changed but I have changed the ip in flow and arduino program also .. i am always using the latest ip in the program to test it ..

42

So with the new ip set in the MQTT nodes does the test flow work?

43

Test flow only works when i set server as "localhost" .. if i set server "192.168 .xx.xx " (my system ip address ) then mqtt only shows connecting and test flow does not work