MQTT_Connect -45 when connecting to AWS

RE: MQTT_Connect -45 when connecting to AWS

dtquang89 — Fri, 01 May 2020 13:26:13 GMT

Hi, I think the answer of Didrik Rokhaug is correct.

Just to make sure the certificates are insert correctly in certificates.h.

In addition, there are 3 certificates you need to obtain: Client certificate, client private key, and cloud certificate.

Good luck.

RE: MQTT_Connect -45 when connecting to AWS

Didrik Rokhaug — Mon, 23 Sep 2019 13:08:35 GMT

Hi.

1. When you are using the asset_tracker sample application, then the device generates its own client ID (nrf-<IMEI>). You can override this behavior by defining NRF_CLOUD_CLINET_ID.

If you are not using the nrf_cloud library, you have to define the client ID yourself. When using a cloud service, the device ID usually has to correspond to the device ID defined in the cloud.

2. Yes, the certificates in certificates.h is PEM formatted, e.g.:

#define NRF_CLOUD_CLIENT_PRIVATE_KEY \
	"-----BEGIN RSA PRIVATE KEY-----\n" \
	"NRF_CLOUD_CLIENT_PRIVATE_KEY\n" \
	"-----END RSA PRIVATE KEY-----\n"

#define NRF_CLOUD_CLIENT_PUBLIC_CERTIFICATE \
	"-----BEGIN CERTIFICATE-----\n" \
	"NRF_CLOUD_CLIENT_PUBLIC_CERTIFICATE\n" \
	"-----END CERTIFICATE-----\n"

#define NRF_CLOUD_CA_CERTIFICATE \
	"-----BEGIN CERTIFICATE-----\n" \
	"NRF_CLOUD_CA_CERTIFICATE\n" \
	"-----END CERTIFICATE-----\n"

Best regards,

Didrik

RE: MQTT_Connect -45 when connecting to AWS

stevenlin — Sat, 21 Sep 2019 10:48:48 GMT

hi dyres,

what is client id ? it generating by self ,? bind with Policies

certificates.h

it is PEM formatted

RE: MQTT_Connect -45 when connecting to AWS

Didrik Rokhaug — Wed, 14 Aug 2019 09:36:42 GMT

Hi.

Error code 2 is ENOENT, meaning that it could not find the file. This is the expected result if the certificates did not exist.

When I use your main file, trying to connect to nRF Cloud (which is built on AWS) it works fine on my end. However, if I delibeartly give it invalid certificates I get -45.

You can check what certificates are written to the modem using the procedure explained in this comment:

https://devzone.nordicsemi.com/f/nordic-q-a/49650/asset_tracker-does-not-work-with-firmware-v1-0-0/199421#199421

RE: MQTT_Connect -45 when connecting to AWS

dyres004 — Tue, 13 Aug 2019 14:42:52 GMT

I have verified my certificates and client ID are correct.

I tried deleting all 5 types. for index 3 and 4 I get a result of 2 from nrf_inbuilt_key_delete. I was unable to determine what that result code signifies.

RE: MQTT_Connect -45 when connecting to AWS

Didrik Rokhaug — Mon, 12 Aug 2019 11:46:50 GMT

Then it's probably some issue with the authentication. Please make sure that your certificates and client ID are correct.

You might also want to delete all 5 types of credentials on the modem, in case you have written some of the last two using the same sec_tag.

RE: MQTT_Connect -45 when connecting to AWS

dyres004 — Fri, 09 Aug 2019 18:48:31 GMT

That has the same outcome.

Thanks

RE: MQTT_Connect -45 when connecting to AWS

Didrik Rokhaug — Fri, 09 Aug 2019 11:28:05 GMT

Hi.

Try to enable peer and hostname verification by un-commenting lines 400 and 405 (and commenting lines 407 and 412).

Best regards,

Didrik