This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 69%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKW%3C/text%3E%3C/svg%3E)
Hello,
I am using the SAMV71Q19B board to connect to the IoT hub using the iot_hub_client (https://github.com/azure-rtos/netxduo/blob/master/addons/azure_iot/docs/azure_rtos_iot_hub_client.md). I am connecting to the hub through an IoT edge device. I am sending some telemetry messages to the hub. The device connects to the hub without any issues and start sending telemetry messages. However, after an hour I receive a FIN ACK from the server , then the board send an encrypted alert followed by a FIN ACK, which reset the connection.
The board never reconnect again. Does anyone know the reason for this behavior?
One other thing, this issue happens almost at the same timestamp in wireshark in each trial.
I have attached below a screenshot of the wireshark capture.
Thanks,
Karim
Hi @Karim Walid Abdelazim Elhammady ,
I would like to understand better your environment. You referenced Azure RTOS netxduo as your iot_hub_client . And then you mentioned that this device is connecting through an IoT Edge device - Is the IoTEdge Device acting as a transparent gateway?
Assuming SAMV71Q19B is a child device of your IoT Edge Transparent Gateway, when you receive the FIN ACK from the server, did you check the IoT Edge device for any errors? If you restart IoTEdge, is the connection reestablished? See Troubleshoot your IoT Edge device for more steps to check.
I would suggest you also try connecting SAMV71Q19B directly to IoTHub, so we can confirm if the issue is in IoTEdge or not.
Thanks!
Hello @António Sérgio Azevedo ,
yes, I am using the edge as a transparent gateway. I haven't checked the errors or tried restarting the IoTEdge, maybe I will check that. I will try to directly connect to the IoTHub and let you know.
Thanks,
Karim
Hello @António Sérgio Azevedo ,
I tested by connecting directly to the IoThub. I still get the FIN ACK from the server in the same amount of time. Also, I disabled the telemetry messages being sent by the device so it is not related to the issue. seems like it is not a problem with the IoT edge that I were using as well.
still trying to investigate the error logs on the hub. Please let me know your thoughts and if there is any other thing that I should try.
Thanks,
Karim
after checking the error logs on IoTHub:
This is the error: 401003 IoTHubUnauthorized , seems it is related to SAS token generation after expiry.
I found the error description here:
https://learn.microsoft.com/en-us/azure/iot-hub/troubleshoot-error-codes#401003-iothubunauthorized
@Karim Walid Abdelazim Elhammady thanks for trying connecting it directly to IoTHub. The error you are receiving helps us understand better what may be hapenning.
Are you setting the connection status callback function like this?
UINT nx_azure_iot_hub_client_connection_status_callback_set(NX_AZURE_IOT_HUB_CLIENT *hub_client_ptr,
VOID (*connection_status_cb)(
struct NX_AZURE_IOT_HUB_CLIENT_STRUCT
*hub_client_ptr, UINT status));
This routine sets the connection status callback. This callback function is invoked when the IoT Hub status is changed. For example following status will be returned on disconnection: NXD_MQTT_ERROR_NOT_AUTHORIZED or NX_AZURE_IOT_SAS_TOKEN_EXPIRED . If you have the callback function enabled can you confirm you receive a status change and which one?
As a next step can you as well please open a new issue in the netxduo repo? I don't have the device to reproduce myself and I will call the attention of the Product Team once you share the issue link here.
Thank you so much!
Hi @Karim Walid Abdelazim Elhammady Yes, the timeout for connection is 1 hour by default here. You may redefine NX_AZURE_IOT_HUB_CLIENT_TOKEN_CONNECTION_TIMEOUT to extend the connection timeout. Thanks.