nRF9160 MQTT Connection refused

RE: nRF9160 MQTT Connection refused

mourad — Fri, 26 Aug 2022 14:19:42 GMT

Thanks Charlie for the clarification

RE: nRF9160 MQTT Connection refused

Charlie — Fri, 26 Aug 2022 09:15:19 GMT

Hi Mourad,

Please use your own MQTT broker or a public one like mqtt.eclipseprojects.io to test nRF9160: Simple MQTT.

nRF Cloud has its private MQTT broker for its high-level application usage, it is not fit for the MQTT broker test. Please refer to nRF Cloud based samples to add devices and do tests.

Do you mean you are using an AWS MQTT broker? If so, we have a dedicated sample for this:

nRF9160: AWS IoT — nRF Connect SDK 2.0.0 documentation (nordicsemi.com)

Best regards,

Charlie

RE: nRF9160 MQTT Connection refused

mourad — Thu, 25 Aug 2022 15:41:43 GMT

Hi paul

Thank you for your answer, I have added that line to prj.conf but it still the same problem

RE: nRF9160 MQTT Connection refused

paul.lander — Thu, 25 Aug 2022 14:21:17 GMT

Hi mourad,

We have noticed that it can take a few seconds to connect to AWS with TLS once the connection to the cellular network has been established. Error No. 111, "connection refused" is common. Connection times range from 1 to 20 seconds and seem to depend partly on cellular signal strength. We're using HTTPS and an API Gateway, not MQTT, but our solution was to increase the connection timeout. Perhaps that will help you?

Regards,

Paul

# Extending socket connection timeout from default of 3,000 ms
CONFIG_NET_SOCKETS_CONNECT_TIMEOUT=60000