search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.25k stars 21.42k forks source link

"Unhandled exception. Microsoft.Azure.Devices.Provisioning.Client.ProvisioningTransportException: MQTT transport exception ---> DotNetty.Transport.Channels.ClosedChannelException: I/O error occurred." #111362

Closed nickjanocik closed 1 year ago

nickjanocik commented 1 year ago

Hi there,

I was following this tutorial (https://learn.microsoft.com/en-us/azure/iot-dps/tutorial-custom-hsm-enrollment-group-x509?tabs=linux&pivots=programming-language-csharp) for provisioning X.509 devices to Azure (C#).

I followed all of the directions, but when I get to step 4 of the "Prepare and run the device provisioning code" section, I get the following error:

Screen Shot 2023-06-23 at 2 51 02 PM

I've searched around for any indications as to why DotNetty would be throwing an I/O error, but to no avail.

I would appreciate any ideas, thanks!

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

Naveenommi-MSFT commented 1 year ago

@nickjanocik Thanks for your feedback! We will investigate and update as appropriate.

LeelaRajesh-Sayana commented 1 year ago

Hello @nickjanocik Can you validate if your Azure Device Provisioning service and IoT Hub are configured to allow Public Access on all networks. You can view this setting from Networking section of the respective services. Please let us know your observations on this.

nickjanocik commented 1 year ago

Hi @LeelaRajesh-Sayana , yes, Public Access is enabled on all networks on both my IoT Hub and DPS instance.

LeelaRajesh-Sayana commented 1 year ago

Hi @nickjanocik thank you for your response.

For a deeper investigation and immediate assistance on this issue, please file a support request @ https://aka.ms/azsupt? If you do not have access to a support plan, could you please send an email to azcommunity@microsoft.com with the below details, so that we can work closely on this matter.

Thread URL: Link to this thread. Azure Subscription ID: Email Subject : Attn Leela

We will now close this issue here. It will be revisited if the documentation needs to be updated after a resolution has been arrived through support issue.