Windows IoT Provision Error

Question

Windows IoT Provision Error

Suresh Batta 0

While setting up an IoT Edge on Windows with EFLOW, per this page [https://learn.microsoft.com/en-us/azure/iot-edge/how-to-provision-single-device-linux-on-windows-x509?view=iotedge-1.4&tabs=azure-portal%2Cpowershell#provision-the-device-with-its-cloud-identity,

on the Provision step here - [https://learn.microsoft.com/en-us/azure/iot-edge/how-to-provision-single-device-linux-on-windows-x509?view=iotedge-1.4&tabs=azure-portal%2Cpowershell#provision-the-device-with-its-cloud-identity,

running the command is throwing an error:

ssh failed to execute [ERROR: 0x80072741 kex_exchange_identification: Connection closed by remote host] at line 4322

How to resolve this? Did I miss something?

LeelaRajeshSayana-MSFT 17,766 Reputation points Moderator

2023-01-27T19:41:55.26+00:00
Hello SB, Greetings! Welcome to Microsoft Q&A forum! Thank you for posting the question. We would be glad to assist you with the issue. The documentation states you need the following files for manual provisioning with X.509:

Two of device identity certificates with their matching private key certificates in .cer or .pem formats. One set of certificate/key files is provided to the IoT Edge runtime. When you create device identity certificates, set the certificate common name (CN) with the device ID that you want the device to have in your IoT hub.

Thumbprints taken from both device identity certificates. Thumbprint values are 40-hex characters for SHA-1 hashes or 64-hex characters for SHA-256 hashes. Both thumbprints are provided to IoT Hub at the time of device registration.

Could you please let me know if you have used the resource Create demo certificates to test IoT Edge device features to create the test certificates or you have the certificates of your own?
LeelaRajeshSayana-MSFT 17,766 Reputation points Moderator

2023-02-01T22:41:17.3933333+00:00

Hello SB, greetings! I am following up to see if you can share the above requested information to help us better understand and assist you with this issue.

1 answer

Your answer

LeelaRajeshSayana-MSFT 17,766 Reputation points Moderator

2023-01-27T19:41:55.26+00:00

Hello SB, Greetings! Welcome to Microsoft Q&A forum! Thank you for posting the question. We would be glad to assist you with the issue. The documentation states you need the following files for manual provisioning with X.509:

Two of device identity certificates with their matching private key certificates in .cer or .pem formats. One set of certificate/key files is provided to the IoT Edge runtime. When you create device identity certificates, set the certificate common name (CN) with the device ID that you want the device to have in your IoT hub.

Thumbprints taken from both device identity certificates. Thumbprint values are 40-hex characters for SHA-1 hashes or 64-hex characters for SHA-256 hashes. Both thumbprints are provided to IoT Hub at the time of device registration.

Could you please let me know if you have used the resource Create demo certificates to test IoT Edge device features to create the test certificates or you have the certificates of your own?
LeelaRajeshSayana-MSFT 17,766 Reputation points Moderator

2023-02-01T22:41:17.3933333+00:00

Hello SB, greetings! I am following up to see if you can share the above requested information to help us better understand and assist you with this issue.

Answer 1

Hi,
Sorry for the delayed response on this issue!

The error message "ssh failed to execute [ERROR: 0x80072741 kex_exchange_identification: Connection closed by remote host] at line 4322" indicates that the SSH connection to the target device was not successful.

Here are some troubleshooting steps you can try:

Check the network connectivity between your development machine and the target device. Make sure that both devices are on the same network and can communicate with each other.
Verify that the SSH service is running on the target device. You can do this by logging into the device manually using an SSH client, such as PuTTY or OpenSSH.
Check that the firewall on the target device is not blocking SSH connections. You may need to configure the firewall to allow incoming SSH connections.
Verify that the credentials used for the SSH connection are correct. Make sure that you are using the correct username and password for the target device.
If you are using a custom SSH port on the target device, make sure that you specify the correct port number in the command.
Ensure that your Windows 10 IoT Core device has the SSH server feature enabled. You can enable this feature by following these steps: a. Open the "Settings" app on the device. b. Select "Apps". c. Click on "Optional features". d. Click on "Add a feature". e. Scroll down to "OpenSSH Server" and select it. f. Click on "Install".
Try restarting both your development machine and the target device and attempt the connection again.

If none of these steps resolve the issue, please comment in the below section and we are happy to help!!!

Share via

Windows IoT Provision Error

1 answer

Your answer