locked
Connection failure to DPS: new iothub region RRS feed

  • Question

  • Hi,

    My device which is using azure iot c sdk DPS code was connecting to iothub and everything ( To & fro device communication ) was running fine. The region for this iothub is East USA

    Next I created a new iothub which is located in SouthAsia region and updated the code accordingly. I am now seeing failure in SSL communication. The failure is related to bad public key. Same iothub can connect to USA region but fails in southAsia region

    Could you suggest what causes this behavior?

    How can I support multiple regions in Azure IoTHub?

    Regards

    Wednesday, October 10, 2018 7:05 AM

All replies

  • Hi,

    Azure team, do you have any suggestions?

    Regards

    Thursday, October 11, 2018 7:32 AM
  • Hello,

    Can you provide more details of the error message and if you are following a tutorial for this? Please note that DPS SDK is used to register your device to an IoTHub, then you need to use IoTHub Device SDK to connect with the IOTHub.

    I am confused with your question, but did you try creating a new deviceId for example?

    Thanks

    Thursday, October 18, 2018 2:07 PM
  • Hi,

    Below is the log

     indicate_open_complete: 
    Provisioning Status: PROV_DEVICE_REG_STATUS_CONNECTED

    PUT /0ne00022DB5/registrations/riot-device-3-cert/register?api-version=2017-08-31-preview HTTP/1.1
    UserAgent: prov_device_client/1.0
    Accept: application/json
    Connection: keep-alive
    Content-Type: application/json; charset=utf-8
    Host: global.azure-devices-provisioning.net:443
    Content-Length: 41



    len: 41
    .*s

    HTTP Status: 202

    Date: Tue, 30 Oct 2018 05:07:37 GMT

    Content-Type: application/json; charset=utf-8

    Transfer-Encoding: chunked

    Location: https://global.azure-devices-provisioning.net:443/0ne00022DB5/registrations/riot-device-3-cert/register

    x-ms-request-id: a88bc3e3-d4c6-4518-a874-0dbfbefa4574

    Strict-Transport-Security: max-age=31536000; includeSubDomains

    .*s
    Provisioning Status: PROV_DEVICE_REG_STATUS_ASSIGNING

    GET /0ne00022DB5/registrations/riot-device-3-cert/operations/4.e439629cba45cd99.d9ce32d9-5cb3-4129-a560-30425f90f144?api-version=2017-08-31-preview HTTP/1.1
    UserAgent: prov_device_client/1.0
    Accept: application/json
    Connection: keep-alive
    Content-Type: application/json; charset=utf-8
    Host: global.azure-devices-provisioning.net:443
    Content-Length: 0



    HTTP Status: 200

    Date: Tue, 30 Oct 2018 05:07:43 GMT

    Content-Type: application/json; charset=utf-8

    Transfer-Encoding: chunked

    x-ms-request-id: dfec0161-9ebc-4018-9405-93e11d662f8a

    Strict-Transport-Security: max-age=31536000; includeSubDomains

    .*s
    Unsuccessful json encountered: {"operationId":"4.e439629cba45cd99.d9ce32d9-5cb3-4129-a560-30425f90f144","status":"failed","registrationStatus":{"registrationId":"riot-device-3-cert","createdDateTimeUtc":"2018-10-30T05:07:39.0506994Z","status":"failed","generationId":null,"errorCode":401001,"errorMessage":"An error occurred while sending the request.","lastUpdatedDateTimeUtc":"2018-10-30T05:07:39.2781219Z","etag":"\u002203009d43-0000-0000-0000-5bd7e71b0000\u0022"}}Failure retrieving data from the provisioning servicewinc1500_close: socket: 0 
    DPS_HSM: hsm_client_x509_deinit: 
    Error: Time:Thu Jan  1 06:31:38 1970 File:../Src/APP/framework/azure/provisioning_client/src/prov_transport_http_client.c Func:prov_transport_http_dowork Line:892 Press any key to continue:

    Tuesday, October 30, 2018 7:42 AM
  • Sorry for late reply but this is another issue I am facing when connecting to an IoTHub in different region
    Tuesday, October 30, 2018 7:47 AM
  • Hi,

    This will require some deeper analysis. Can you please file a support request @ https://aka.ms/azsupt and reference this thread in the description? If you do not have access to a support plan, please reach out @ AZCommunity@microsoft.com with a link to this Issue as well as your subscription ID and we can help get the support ticket opened for this issue.

    Thanks!

    Tuesday, October 30, 2018 12:54 PM
  • Possibly try following this process to roll a new certificate to the IoT Hub but with the existing certificate...to ensure the IoT Hub in South Asia region is using the correct one.

    How to roll X.509 device certificates

     
    Wednesday, October 31, 2018 11:00 PM
  • Thanks Mike

    We are following the same process for adding new certificate

    Friday, November 2, 2018 9:48 AM