• State Suggested Answer
  • Replies 16 replies
  • Answers 2 answers
  • Subscribers 65 subscribers
  • Views 2819 views
  • Users 0 members are here
Attachments (4) Download All
Nordic Case Info
  • Case ID: 276673
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Problems with programming device certificates from the AWS IoT console.

Jacek Majda

I did download the device certificates from the AWS IoT console into a directory: C:\Nordic  on my PC.

However, my attempts to copy and paste these device certificates from the directory C:\Nordic on my PC to the respective entries (CA Certificate, Client Certificate and Private Key) on the Certificate Manager of the LTE Link Monitor were unsuccessful. No response at all...

Also, when you open the Certificate Manager in the LTE Link Monitor, you see the following note: "Use security tag 16842753 to manage nRF Connect for Cloud certificate, otherwise pick a different tag".   So, which security tag shall be used to manage the AWS IoT certificates?

I am using:

1. nRF9160DK v1.0.1

2. Windows 10 Pro OS, version: 20H2, OS build:19042.631

3. nRF Connect v 3.7.0

4. nRF Connect SDK v1.6.1

Regards,

Jacek

Parents
  • 0

    1. what kind of SIM card are you using in the device?     A Vodacom SIM card, enabled for NB-IoT in the Republic of South Africa.

    2. did you activate the SIM card?    Yes

    3. did you double check that you have sufficient data available on the SIM card?  Yes

    I was able to successfully run and test the application: asset_tracker , connecting successfully to the nrfcloud.com but I could not connect to www.example.com when I tried to run and test the sample: https_client.

    I was told that when I ran the sample: https_client, it  was unsuccessfully trying to establish a TCP connection via port 443 (which is the HTTPS port number) because server was denying the request with a TCP RST (reset of TCP connection). 

    On the other hand, when I ran the sample:asset_tracker, it was running via MQTTS on port 8883 and it did successfully connect to  nrfcloud.com.

    Could the problem that I am experiencing with connecting to the internet while running sample: AWS_IoT be similar to the one that I experienced with sample: https_client?

    Does the sample: AWS_IoT require establishing a TCP connection via port 443 (which is the HTTPS port number)?

Reply
  • 0

    1. what kind of SIM card are you using in the device?     A Vodacom SIM card, enabled for NB-IoT in the Republic of South Africa.

    2. did you activate the SIM card?    Yes

    3. did you double check that you have sufficient data available on the SIM card?  Yes

    I was able to successfully run and test the application: asset_tracker , connecting successfully to the nrfcloud.com but I could not connect to www.example.com when I tried to run and test the sample: https_client.

    I was told that when I ran the sample: https_client, it  was unsuccessfully trying to establish a TCP connection via port 443 (which is the HTTPS port number) because server was denying the request with a TCP RST (reset of TCP connection). 

    On the other hand, when I ran the sample:asset_tracker, it was running via MQTTS on port 8883 and it did successfully connect to  nrfcloud.com.

    Could the problem that I am experiencing with connecting to the internet while running sample: AWS_IoT be similar to the one that I experienced with sample: https_client?

    Does the sample: AWS_IoT require establishing a TCP connection via port 443 (which is the HTTPS port number)?

Children
Related