MQTT Client Connection Closes Immediately #3078
-
Hi, v7.17 I'm having trouble getting the mongoose MQTT client to stay connected. The project I'm working on was built with the Wizard for Nucleo-H743ZI baremetal Make. The ultimate goal is to connect to Azure IoT Hub broker (which requires TLS), but I'm also testing with a HiveMQ Cluster. I haven't had success with the built-in TLS implementation, so I've been using MbedTLS v2.28.2. I've been able to connect and complete authentication for both Azure IoT Hub and the HiveMQ Cluster, but the connection almost always closes immediately after processing the CONNACK despite a return code of 0. I made some modifications to Does anyone have tips on how to troubleshoot this issue? Do my configurations look appropriate? I'm running a separate client on my PC with python and paho.mqtt and haven't had any issues staying connected to either broker. I'm also monitoring the traffic with Wireshark. Please let me know if there is any other information I can provide to contextualize my problem. Thanks in advance for your help! mongoose_config.h
mbedtls_config.h
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Our built-in TLS is 1.3; HiveMQ does not seem to support that Our examples work; MQTT is tested on every change and every night with a CI/CD pipeline. If something does not work for you, then please
|
Beta Was this translation helpful? Give feedback.
Our built-in TLS is 1.3; HiveMQ does not seem to support that
I'm sorry, we are not MbedTLS experts, we can't check your config. There are some of them proven to work in the tutorials section in the repo https://github.com/cesanta/mongoose/blob/master/tutorials/stm32/nucleo-h743zi-make-baremetal-builtin/mbedtls_config.h
Our customers do not need to modify mongoose. No one should need to. Please see our documentation, and follow the guidelines in our tutorials.
Our examples work; MQTT is tested on every change and every night with a CI/CD pipeline. If something does not work for you, then please
sniff your network (using Wireshark, for example) and observe the traffic.
If, after your netwo…