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(48, 38%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
I have a number of cellular devices deployed in Canada (with different mobile operators) and connecting to Azure IoT Hub West US 2 location. They've been working normally for a long time until last Tuesday, when all of them started getting handshake issues with Azure server. Now, they have to retry sometimes to connect to Azure. Looks like a systemic (but intermittent) issue. I'd like to add that the devices deployed on the US mobile networks are working normally.
Are there any diagnostics utilities or error log files in Azure that could help in debugging this issue?
Thanks, @SatishBoddu-MSFT. I don't see any issues on those pages.
I was able to retrieve IoT Hub connectivity error logs under Monitoring->Logs. I see some occasional errors here and there, but none that correspond to the specific time slots for the intermittent connectivity failures that I see. This appears to be either a misconfigured firewall/load balancer on the Azure IoT Hub for certain IP source address range or a general network routing issue somewhere up the stream. Any other ideas how to troubleshoot this further?
![](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(54.400000000000006, 38%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQ%3C/text%3E%3C/svg%3E)
Hi there, @1538d9a3-024a-4f49-89ec-19d604828f4d ,
Sometimes re-configuring the gateway also resolves the issue.
Pointing to the right cert file sometimes resolves this issue from devices.
Some times IoT Hub throttling limits as well.
Switch to use AMPQ to not disconnect when SAS token expire.
Best client SDK keep_alive time setting.
Check the full logs on Device app.
Please don't include any sensitive data in your logs or screen grabs. please mask all PII.
Hello @Star Gazer 1 , Just checking back, could you please let us know if you need further help in this matter.
Hello @StarGazer1-9641 , Just checking back, could you please let us know if you need further help in this matter.
Hi @SatishBoddu-MSFT, sorry for a delay, I was traveling. The problem went away on its own a couple of days ago. It must've been some sort of networking issue that someone has fixed. If it happens again, we'll have to dive deeper into it.
Hello @StarGazer1-9641 , Glad to hear that your transient issue is now resolved, please feel free to comment or post new question in future and we will be glad to discuss more. Please accept the helpful response as 'Answer' so that it may be helping other in future and we can close this thread.
Hello @Star Gazer 1 , Just checking back, feel free to comment on this issue if you need further help!
Hi there @1538d9a3-024a-4f49-89ec-19d604828f4d , Have you checked the Azure Service Status Health ? or General page on Azure status ?
Please check the reported issues on service health page, also check the 'History History' on same page.
Also check the Resource Health section,
Hello @Star Gazer 1 , Just checking back, could you please let us know if you need further help in this matter.
Hello @Star Gazer 1 , Just checking back, feel free to comment on this issue if you need further help!