Forums - aws returning -19 error for aws_iot_mqtt_connect

3 posts / 0 new
Last post
aws returning -19 error for aws_iot_mqtt_connect
akshay.b
Join Date: 2 Aug 19
Posts: 62
Posted: Mon, 2020-02-03 11:46

Hello,

Facing an issue where after starting sntp server and domain name resolution when aws_iot_mqtt_connect is called it sends error -19 for first 2 attempt and on third attempt it successfully connect to aws_iot_mqtt_connect. What can be the issue?

We know that NETWORK_X509_ROOT_CRT_PARSE_ERROR = -19, means it is CA root file error.

The CA root file that is causing above issue is ECC 256 bit key: Amazon Root CA 3.

Other Root CA file like, RSA 2048 bit key: VeriSign Class 3 Public Primary G5 root CA certificate and RSA 2048 bit key: Amazon Root CA 1 are not at all working and throws -19 error every time continuously.

It takes almost 2 minutes to connect to aws server after entering the wifi ssid and password. Our aim is to reduce this time.

AWS sdk version is 3.1.

Please suggest what xan be the issue.

 

Thank you,

Akshaay

  • Up0
  • Down0
c_rpedad
Profile picture
Join Date: 18 Jun 18
Location: San Jose
Posts: 317
Posted: Tue, 2020-02-11 10:14

Can you provide us the sniffer capture during the issue to verify the reason for failure in first 2 attempts?

We recommend using RSA 2048 bit key: Amazon Root CA 1 rootCA for connection to download on the device using certcs server. Also, kinldy let us know if the same behaviour is seen with our QCLI_demo -- Ecosystem -- AWS commands.

Please provide the sequence of instructions, how you are verifying the connection sequence ?
 

  • Up0
  • Down0
raniglas
Join Date: 21 Jan 20
Posts: 7
Posted: Fri, 2020-02-14 17:34

Hi,

We maanged to resolve the issue by using Amazon Root Certificate CA 3. It is not clear to us why, but we're glad it works. The only thing right now is that we need to wait for the system to get time from sntpc, or otherwise it fails on certificate verification - but this makes sense and works well for us.

Thank you,

Rani

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.