Can not connect to ThingSpeak MQTT broker using MQTT X Client

Hello,

I have a problem with the connection to thingspeak MQTT broker using MQTT x client. After pressing the "Connect" button after a few seconds connection is not set.

I have followed the instructions described in: https://de.mathworks.com/help/thingspeak/use-desktop-mqtt-client-to-publish-to-a-channel.html.

Below you can see the settings in the MQTT X client. ClientID, Username and Password I took from the credentials file which was created when I add a new MQTT device in thingspeak.

I have already checked the discussion with a similar problem, but I can not figure out what could be the source of the problem.

I would like to ask your help with this problem.

Thank you,

Levani Meskhiya

Answer 1

[Vinod]

If you're connecting over Secure MQTT, you need to use port 8883, not port 1883 as your screenshot shows.

[Levani Meskhiya]

I have also used port 8883, this did not help.

[Vinod]

Can you share the clientID you are using to connect?

[Levani Meskhiya]

Yes I can, Client ID is the same as Username:

Og8mNRUwOzIyDDkWGyohDRE

[Vinod]

What I can see on the server end for this clientID is that the clientID/password being supplied when it attempts connect is incorrect and the connection is being rejected for this reason. The clientID I see on our server end has an extra "-iPhone" tagged on at the end.

Can you regenerate the password and copy the exact clientID and password into your client and try again?

[Levani Meskhiya]

I have regenerated the password and tried again. I have got an error: "connect ETIMEDOUT 18.207.44.162:8883".

I attached the setting in the MQTT client with clientID and Username. I have copied exact clientID from the credentials file.

[Vinod]

Maybe the 8883 port is blocked on your end? Try a websocket connection (ws://) on port 80 with SSL turned off. Does that work?

[Levani Meskhiya]

It works with websocet connection. Could you please tell me where I can check if the 8883 port is blocked on my end?

[Vinod]

If websocket works, I would reccomend secure websocket (wss://) on port 443 with SSL/TLS enabled and CA signed server.

You'd have to check with your IT administrator about outgoing connection and which network ports are allowed, and specifically if outgoing connections on port 8883 are blocked by your firewall.

[Levani Meskhiya]

Ok, I will check. Thank you very much for your help.