AWS_IoT mqtt_connect,error: -111

RE: AWS_IoT mqtt_connect,error: -111

Markus Tacker (he/him) — Mon, 16 Aug 2021 07:58:09 GMT

Yes, they are absolutely needed.

RE: AWS_IoT mqtt_connect,error: -111

jake11212 — Sun, 15 Aug 2021 18:19:08 GMT

I found the problem actually it was quite basic. When I added the certificates I had removed the -----BEGIN RSA PRIVATE KEY----- and -----END RSA PRIVATE KEY----- portions as I thought the certificate was only comprised on the information between these two strings. I added them again without cutting anything out and was able to connect to AWS, so this seems to have been the issue!

RE: AWS_IoT mqtt_connect,error: -111

Markus Tacker (he/him) — Sun, 15 Aug 2021 12:58:49 GMT

Can you double check that the AWS IoT thing was assigned the policy, as outlined in step 11 here?

RE: AWS_IoT mqtt_connect,error: -111

jake11212 — Fri, 13 Aug 2021 19:03:54 GMT

Hello, here are the logs:

devzone.nordicsemi.com/.../AT_2B00_CFUNoutput.txt

I am using NCS V1.6.0.

My 9160DK has the firmware 1.3.0 from the 2021-06-25_7a076c22 download.

Also I should note that I have successfully connected with asset tracker to the nRF cloud website, the LTE device/SiM are verified on the site, and asset tracker was able to update a simulated flip by toggling switch 1 on the 9160DK so this seems to point to an issue with the AWS connection.

I also tried checking the certificates by adding CONFIG_AT_CMD_RESPONSE_MAX_LEN=2560 to the prj.config file and then running the AT%CMNG=1 command and got this response:

devzone.nordicsemi.com/.../logCertificateCheck.txt

RE: AWS_IoT mqtt_connect,error: -111

Øyvind — Fri, 13 Aug 2021 10:42:24 GMT

Hello,

Can you share a full log output with output from "AT+CFUN?". What version of NCS are you working with?

Kind regards,
Øyvind