How to check EHOSTUNREACH for MQTT-Explorer

[djiwondee]

Hello @thomasnordquist,

first. let me say a big Thanks for your work on this very good utility. I'm using it for a while to administer and identify issues for my smartphone setup.

Since a couple of weeks (probably update my Desktop Mac to macOS Sequoia), I'm not longer able to connect to a broker running on a device acting as smartphone hub. The only symptom I see on my Mac is an incrementing port number shown on the GUI of the explorer, every time I hit the "Connect" button to connect to the broker.

I would like to look somewhere into a log, MQTT-explorer may use to get some more details about the connectivity. Is there a way/a feature of MQTT explorer to enable this?

I have already checked the following things and tested them elsewhere:

• the broker I can't connect to with MQTT-explorer is up and running and reachable in my infrastructure setup.
• now mistake in username, password and port
• using the IP address instead of host name in the connection settings: results in EHOSTUNREACH as well as
• connecting to a different broker configured in the connection settings (see screenshot): being able to connect to
• running MQTT-Explorer 0.4.0 beta 6 on a different Mac (checked on two different laptops running Sequoia and Sonoma: being able to connect to the broker
• Removed MQTT-Explorer completely from my Mac, reboot and reinstalled MQTT-Explorer: results in EHOSTUNREACH as well
• Using the former MQTT-Explorer officially available in Apple App Store: not able to connect, but the error message show on the MQTT-Explorer GUI is more generic.

I assume there is problem with my Mac network connection or security. This is what I would like primarily to check. In addition to that, since the re-installation of MQTT-explorer, MQTT explorer appears twice in the Data privacy & Security Settings of the MacOS System Preferences:

Any idea of how to proceed with the investigation is highly appreciated. Thanks in advance!

[metawops]

I, too, can't reach my Home Assistant MQTT server anymore with version 0.4.0.
Version 0.3.5 works still fine.
When I try to connect to the same address with 0.4.0 (beta 6) I get the EHOSTUNREACH error:

So 0.4.0 is a no go for me, unfortunately. 🤷‍♂️

[mpellatt]

Same here!

[djiwondee]

Just a non-educated guess: could it be caused by some issues with the local network (address resolution, port mapping, ...)? In my case, my Mac is connected with both, wired LAN and wifi. But otherwise, the problem doesn't disappear, if I disconnect one of the network connectors, w/ and w/o reboot after that.

In the meantime 0.4.0 is working for me, but the way to this point was not foreseeable and really undesirable. the fusion disk on my Mac got in trouble, an therefore I needed to completely reinstall macOS from scratch. After finishing this and installing the 0.4.0 version it works.

@thomasnordquist: However, the key questions still remain, is there a log, MQTT-explorer may use to get some more details about the connectivity. Why does the port number count upwards? (see m y screenshots at the top of this issue: #854 (comment))

[melyux]

Big issue. Can't connect to any MQTT servers anymore.