getaddrinfo, error -2

[Capt. Flatus O'Flaherty]

Error:

*** Booting Zephyr OS build v3.3.99-ncs1 ***
*** Booting Zephyr OS build v3.3.99-ncs1 ***
I: The AWS IoT sample started, version: v1.0.0
+CEREG: 2,"E03C","0012FE1E",7
I: LTE cell changed: Cell ID: 1244702, Tracking area: 57404
+CSCON: 1
I: RRC mode: Connected
%XTIME: ,"32609251520440","01"
+CEREG: 5,"E03C","0012FE1E",7,,,"11100000","11100000"
I: Network registration status: Connected - roaming
I: Date I: PSM parameter update: TAU: 6480, Active time: -1
time obtained
I: Next connection retry in 30 seconds
I: AWS_IOT_EVT_CONNECTING
E: getaddrinfo, error -2
E: client_broker_init, error: -10
I: AWS_IOT_EVT_CONNECTING

From: ncs/v2.4.0/nrf/samples/nrf9160/aws_iot

The first error is: "getaddrinfo, error -2"

Please advise how I can fix this !!!

Thank you.

[Capt. Flatus O'Flaherty]

@Øyvind ..... any thoughts on this issue?

[Øyvind]

Hi, 

Capt. Flatus O'Flaherty said:

All good, except there's no mention of where to put the certificates and policy,

What sample documentation are you following? In the NCS v.2.4.0 - AWS IoT sample docs it states, under Setup, that you must complete the setup as described under AWS IoT documentation. This includes fairly good steps on how to provision the certificates on your device and how the add the policy in AWS.

Let me know if anything is unclear. 

Kind regards,
Øyvind

[Capt. Flatus O'Flaherty]

Thanks for reply Øyvind  ...

I've followed the instructions you high lighted and added configs to both kconfig and prj.conf:

config AWS_IOT_SEC_TAG
	int "7564564566456"

config AWS_IOT_BROKER_HOST_NAME_APP
	bool "AWS IoT sever hostname provided by application run-time"

config AWS_IOT_BROKER_HOST_NAME
	string "aix9xe3pan9ob-ats.iot.eu-north-1.amazonaws.com"
	depends on !AWS_IOT_BROKER_HOST_NAME_APP

config AWS_IOT_PORT
	int "AWS server port"
	default 8883

config AWS_IOT_MQTT_RX_TX_BUFFER_LEN
	int "Buffer sizes for the MQTT library"
	default 1000
	help
	  Specifies maximum message size can be transmitted/received through
	  MQTT (exluding MQTT PUBLISH payload).

config AWS_IOT_MQTT_PAYLOAD_BUFFER_LEN
	int "Size of the MQTT PUBLISH payload buffer (receiving MQTT messages)"
	default 2304

config AWS_IOT_IPV6
	bool "Configure AWS IoT library to use IPv6 addressing. Otherwise IPv4 is used"

config AWS_IOT_APP_SUBSCRIPTION_LIST_COUNT
	int "Amount of entries in the application subscription list"
	default 0

config AWS_IOT_BROKER_HOST_NAME_MAX_LEN
	int "Maximum length of broker host name"
	default 64

config AWS_IOT_CLIENT_ID_MAX_LEN
	int "Maximum length of cliend id"
	default 30

config AWS_IOT_PROVISION_CERTIFICATES
	bool "Run-time provisioning of certificates"
	default y if BOARD_QEMU_X86
	imply MBEDTLS_PEM_CERTIFICATE_FORMAT if MBEDTLS
	help
	  Enable run-time provisioning of certificates from the
	  certificates header file selected by using AWS_IOT_CERTIFICATES_FILE
	  This option is only available for QEMU x86 build targets.

config AWS_IOT_CERTIFICATES_FILE
	string "AWS IoT certificates"
	depends on AWS_IOT_PROVISION_CERTIFICATES
	default "../include/aws-certs.h"
	help
	  The default path for a header file that contains definitions for certificates that are
	  used during run-time provisioning of TLS credentials.
	  By default, the library expects the credentials to be in
	  Privacy Enhanced Mail (PEM) format. See "aws-certs.h" for a template.

config AWS_IOT_CLIENT_ID_STATIC
	string "test_thing"
	default "my-thing"

# AWS IoT library
CONFIG_AWS_IOT=y
CONFIG_AWS_IOT_CLIENT_ID_STATIC="test_thing"
CONFIG_AWS_IOT_BROKER_HOST_NAME="aix9xe3pan9ob-ats.iot.eu-north-1.amazonaws.com"
CONFIG_AWS_IOT_SEC_TAG=7564564566456
CONFIG_AWS_IOT_APP_SUBSCRIPTION_LIST_COUNT=2
CONFIG_AWS_IOT_TOPIC_UPDATE_DELTA_SUBSCRIBE=y
CONFIG_AWS_IOT_LAST_WILL=y
CONFIG_AWS_IOT_TOPIC_GET_ACCEPTED_SUBSCRIBE=y
CONFIG_AWS_IOT_TOPIC_GET_REJECTED_SUBSCRIBE=y

I selected prj.conf for the build.

I got the AWS certificates and tried to use Certificate manager to upload them.

I was able to turn off the modem ok.

I'm seeing 3 certificate fields: 1. CA cert, 2. Client cert and 3. Private key.

Amazon has given me 5 files, kdjakajhkjhk-certificate.pem.crt, which presumably goes in field 1, sdfjskfskjhkj-private.pem.key - presumably to field 3 and  kslfldkfjlskjf-public.pem.key which presumably goes into field 2. Is this correct?

The other two files are AmazonRootCA1.pem and AmazonRootCA3.pem.

There's also 2 other fields called 'Pre-shared key' and PSK identity which are just empty at present.

Here's a copy of the upload certificates log:

2023-06-30T14:17:29.555Z DEBUG Application data folder: /home/flatus/.config/nrfconnect/pc-nrfconnect-cellularmonitor
2023-06-30T14:17:29.723Z INFO Using nrf-monitor-lib-js version  0.8.0-pre3
2023-06-30T14:17:29.725Z INFO Using nrf-monitor-lib version 0.13.1
2023-06-30T14:17:29.730Z INFO Using nrf-device-lib-js version: 0.6.12
2023-06-30T14:17:29.730Z INFO Using nrf-device-lib version: 0.15.3
2023-06-30T14:17:29.731Z INFO Using nrfjprog DLL version: 10.19.1
2023-06-30T14:17:29.732Z INFO Using JLink version: JLink_V7.88i
2023-06-30T14:17:29.803Z DEBUG App pc-nrfconnect-cellularmonitor v1.0.2 local
2023-06-30T14:17:29.803Z DEBUG App path: /home/flatus/.nrfconnect-apps/node_modules/pc-nrfconnect-cellularmonitor
2023-06-30T14:17:29.803Z DEBUG nRFConnect 4.1.2, required by the app is (>=4.1.0)
2023-06-30T14:17:29.803Z DEBUG nRFConnect path: /tmp/.mount_nrfconkympf2/resources/app.asar
2023-06-30T14:17:29.804Z DEBUG HomeDir: /home/flatus
2023-06-30T14:17:29.804Z DEBUG TmpDir: /tmp
2023-06-30T14:17:29.805Z INFO Installed JLink version does not match the provided version (V7.80c)
2023-06-30T14:17:30.545Z INFO Getting serialport options from persistent store 000960072311.pc-nrfconnect-cellularmonitor
2023-06-30T14:21:19.169Z INFO Updating CA certificate...
2023-06-30T14:21:19.170Z ERROR Unable to Write TLS credential
2023-06-30T14:21:19.170Z INFO Updating client certificate...
2023-06-30T14:21:19.170Z ERROR Unable to Write TLS credential
2023-06-30T14:21:19.170Z INFO Updating private key...
2023-06-30T14:21:19.171Z ERROR Unable to Write TLS credential
2023-06-30T14:21:19.171Z INFO Certificate update completed
2023-06-30T14:21:31.409Z INFO Selected device with s/n 000960072311
2023-06-30T14:21:31.437Z INFO Opened port with options: {"path":"/dev/ttyACM0","baudRate":115200}
2023-06-30T14:21:31.451Z INFO Device is in line mode.
2023-06-30T14:21:40.292Z INFO Updating CA certificate...
2023-06-30T14:21:40.414Z DEBUG Failed to execute the AT command: AT%CMNG=0,7564564566456,0,"-----BEGIN CERTIFICATE-----
MIIDQTCCAimgAwIBAgITBmyfz5m/jAo54vB4ikPmljZbyjANBgkqhkiG9w0BAQsF
ADA5MQswCQYDVQQGEwJVUzEPMA0GA1UEChMGQW1hem9uMRkwFwYDVQQDExBBbWF6
b24gUm9vdCBDQSAxMB4XDTE1MDUyNjAwMDAwMFoXDTM4MDExNzAwMDAwMFowOTEL
MAkGA1UEBhMCVVMxDzANBgNVBAoTBkFtYXpvbjEZMBcGA1UEAxMQQW1hem9uIFJv
b3QgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALJ4gHHKeNXj
ca9HgFB0fW7Y14h29Jlo91ghYPl0hAEvrAIthtOgQ3pOsqTQNroBvo3bSMgHFzZM
9O6II8c+6zf1tRn4SWiw3te5djgdYZ6k/oI2peVKVuRF4fn9tBb6dNqcmzU5L/qw
IFAGbHrQgLKm+a/sRxmPUDgH3KKHOVj4utWp+UhnMJbulHheb4mjUcAwhmahRWa6
VOujw5H5SNz/0egwLX0tdHA114gk957EWW67c4cX8jJGKLhD+rcdqsq08p8kDi1L
93FcXmn/6pUCyziKrlA4b9v7LWIbxcceVOF34GfID5yHI9Y/QCB/IIDEgEw+OyQm
jgSubJrIqg0CAwEAAaNCMEAwDwYDVR0TAQH/BAUwAwEB/zBgNVHQ8BAf8EBAMC
AYYwHQYDVR0OBBYEFIQYzIU07LwMlJQuCFmcx7IQTgoIMA0GCSqGSIb3DQEBCwUA
A4IBAQCY8jdaQZChGsV2USggNiMOruYou6r4lK5IpDB/G/wkjUu0yKGX9rbxenDI
U5PMCCjjmCXPI6T53iHTfIUJrU6adTrCC2qJeHZERxhlbI1Bjjt/msv0tadQ1wUs
N+gDS63pYaACbvXy8MWy7Vu33PqUXHeeE6V/Uq2V8viTO96LXFvKWlJbYK8U90vv
o/ufQJVtMVT8QtPHRh8jrdkPSHCa2XV4cdFyQzR1bldZwgJcJmApzyMZFo6IQ6XU
5MsI+yMRQ+hDKXJioaldXgjUkK642M4UwtBV8ob2xJNDd2ZhwLnoQdeXeGADbkpy
rqXRfboQnoZsG4q5WTP468SQvvG5
-----END CERTIFICATE-----": (ERROR
)
2023-06-30T14:21:40.415Z ERROR Unable to Write TLS credential
2023-06-30T14:21:40.415Z INFO Updating client certificate...
2023-06-30T14:21:40.468Z DEBUG Failed to execute the AT command: AT%CMNG=0,7564564566456,1,"-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqwzz6wyydTNlo7Xsousk
X3GqEqJSykB+DXo+HfKj3IBWHxrJN13yuRzjZqCacgul0IQTqJxNIXbcPqi0AFwm
YHnGO4q4wZza+J4o8hbo6HZhHhdD2Wh/oQYESE/58cE/T40iz+7vH8QOebNygW
t53iXwoMa57VgPkgFPJ2YlX4jt5XIIl9xdVF1mqwEwge/bdERLWUIqzRw3J/P/da
ECnE59c5Jmab7BeLLvEKtl3sitL2ZkymaD770MdGoY1xPrjJ8NyhhpCgHbsB0AHD
Ew2K7Q5zPkxoy2ndZ1H9jAYdfFPJda8tgVbQzKY49DItaOaTtHwVQM1hj9yIbdyL
hwIDAQAB
-----END PUBLIC KEY-----": (ERROR
)
2023-06-30T14:21:40.468Z ERROR Unable to Write TLS credential
2023-06-30T14:21:40.468Z INFO Updating private key...
2023-06-30T14:21:40.646Z DEBUG Failed to execute the AT command: AT%CMNG=0,7564564566456,2,"-----BEGIN RSA PRIVATE KEY-----
MIIEpAIBAAKCAQEAqwzz6wyydTNlo7XsouskX3GqEqJSykB+DXo+HfKj3IBWHxrJ
N13yuRzjZqCacgul0IQTqJxNIXbcPqi0AFwmYHnGO4q4wZza+J4o8hbo6HZhHhdD
2Wh/oQYESE/5Ol8cE/T40iz+7vH8QOebNygWt53iXwoMa57VgPkgFPJ2YlX4jt5X
IIl9xdVF1mqwEwge/bdERLWUIqzRw3J/P/ECnE59c5Jmab7BeLLvEKtl3sitL2
ZkymaD770MdGoY1xPrjJ8NyhhpCgHbsB0AHDEw2K7Q5zPkxoy2ndZ1H9jAYdfFPJ
da8tgVbQzKY49DItaOaTtHwVQM1hj9yIbdyLhwIDAQABAoIBADaafu8k8X8adjLJ
q43ilIznYwxpxxYLenHg+R1kTMziJxvs2BkVo5tWTn1/fW40q60hzIjBxJmPMQXL
oxKOWC3qEc8GHK6p3PkKvDVz/MvgpmYNtToc8sk7e3h+Fyh8HiF8zUWC2ar7krRB
ezojUQUyoIYIViiw3qU6YfRt5j7Dfx5u8s057FVML2vL1wAlOe4SFpviv2zAkdNQ
OTIeY4GXrqKF/+tLKqbx3hxsKfJ8QWf4K3hZn/ZEyejb9xbe1QqbVqJ8cXuBycGD
7nSxm8ZhbWbqBMyIKo3r4aAstARhc7HkRzJgfGKaD4mMDM22FmNOSzXYlb0DDbe2
lGI4N1ECgYEA33Kp9dFZGxOqB6UjpEWOkYtOmde0fc8m27N/oVdhp+fGL0mz8xbZ
sbI9w9pYAh4x5/5SWn6+LHjmpU6VY8NqNnPJKV3PUHkyERGr3O4zL3Aa/Yj+PBUD
UZRXLrAbvz3PNy5UwtnJ/2J0VaBlgbsYrSy3uhM4N3kfzR5Z1n4F6R8CgYEAw/gq
0g3sPu0LbnQZEFSQJwYRC0QOeFvq58JeXt1q+50ffEkffLe3Or2n8Et0KRMMaYWR
yJ9ia8p0ffBcl51+O9Cx3dtkr4fqKXGTuhxh38KNSR6EoxriMV0MvbeJyrsNbd5m
SeO3FpB1YPRvVSA5YDUT1nvDQONu2LnZYJdMyJkCgYEAwlgvvS8VSjijNT0Lr/AT
nUFF3wa+5IHM8V/AzWp79JbhR/XZvr+MHkLB99urmkP68iXAKRd9fp61NOgRhRDN
C4lPWFxQWVTgF/p/uYuwFz1xLDz/qvA3z7eu0Fu59m7jEMKKVGMqjqZqOqNkRh6d
ytlO/1eCGLWP1E7momk/6M8CgYAgTykYKq15jnFlUaWSbPGEP1HIpaM6VeAoC2
mUDLLROE1TV4xX1TFPO8PWRwZTCVsSzg6845QU7FeLx7Tr8CM50vm71U506m+I/H
jmhgkN3kYUCy93q1csbn/HueTgqfw5wPsJh+AuEnVAWK/l4XS4jywsLlTtn2p2V8
dFV3eQKBgQDJjhX5M63Hk1yJ8YlIk5erMj9HneMh3FjR3LZfC3MaGGOK4pXzmqVp
IHI2LbAvNy7zduRKjoZMRBXPZO5FyNw18JCxYPFUxTguM2vfe7E6Cdowb0nHr5Is
OrXy04l3J2r9rAOMsKNSImKX7oKgZiIeT8oNP9V5t8kYKpJqzUPiPg==
-----END RSA PRIVATE KEY-----": (ERROR
)
2023-06-30T14:21:40.646Z ERROR Unable to Write TLS credential
2023-06-30T14:21:40.646Z INFO Certificate update completed
2023-06-30T14:25:10.208Z DEBUG Could not locate Wireshark executable
2023-06-30T14:25:11.039Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.5-FOTA-TEST_trace-db.json
2023-06-30T14:25:11.039Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.5_trace-db.json
2023-06-30T14:25:11.039Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.4-FOTA-TEST_trace-db.json
2023-06-30T14:25:11.039Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.4_trace-db.json
2023-06-30T14:25:11.039Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.3-FOTA-TEST_trace-db.json
2023-06-30T14:25:11.039Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.3_trace-db.json
2023-06-30T14:25:11.040Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.2-FOTA-TEST_trace-db.json
2023-06-30T14:25:11.040Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.2_trace-db.json
2023-06-30T14:25:11.040Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.1-FOTA-TEST_trace-db.json
2023-06-30T14:25:11.040Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.1_trace-db.json
2023-06-30T14:25:11.040Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.0-FOTA-TEST_trace-db.json
2023-06-30T14:25:11.040Z DEBUG Trace database already downloaded: mfw_nrf9160_1.3.0_trace-db.json
2023-06-30T14:25:11.040Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.8-FOTA-TEST_trace-db.json
2023-06-30T14:25:11.040Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.8_trace-db.json
2023-06-30T14:25:11.040Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.7-FOTA-TEST_trace-db.json
2023-06-30T14:25:11.040Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.7_trace-db.json
2023-06-30T14:25:11.040Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.3-FOTA-TEST_trace-db.json
2023-06-30T14:25:11.041Z DEBUG Trace database already downloaded: mfw_nrf9160_1.2.3_trace-db.json
2023-06-30T14:25:11.041Z DEBUG Trace database already downloaded: mfw_nrf9160_1.1.5-FOTA-TEST_trace-db.json
2023-06-30T14:25:11.041Z DEBUG Trace database already downloaded: mfw_nrf9160_1.1.5_trace-db.json
2023-06-30T14:25:11.041Z DEBUG Trace database already downloaded: mfw_nrf9160_1.1.4-FOTA-TEST_trace-db.json
2023-06-30T14:25:11.041Z DEBUG Trace database already downloaded: mfw_nrf9160_1.1.4_trace-db.json
2023-06-30T14:25:43.650Z INFO Updating CA certificate...
2023-06-30T14:25:44.028Z INFO Successfully deleted TLS credential
2023-06-30T14:25:44.029Z INFO Updating client certificate...
2023-06-30T14:25:45.477Z INFO Successfully deleted TLS credential
2023-06-30T14:25:45.478Z INFO Updating private key...
2023-06-30T14:25:45.684Z INFO Successfully deleted TLS credential
2023-06-30T14:25:45.684Z INFO Certificate update completed
2023-06-30T14:27:19.754Z INFO Deselected device
2023-06-30T14:27:19.754Z INFO Closing device
2023-06-30T14:45:49.267Z INFO Getting serialport options from persistent store 000960072311.pc-nrfconnect-cellularmonitor
2023-06-30T14:45:49.943Z INFO Getting serialport options from persistent store 000960072311.pc-nrfconnect-cellularmonitor
2023-06-30T15:12:13.975Z INFO Updating CA certificate...
2023-06-30T15:12:13.989Z ERROR Unable to Write TLS credential
2023-06-30T15:12:13.989Z INFO Updating client certificate...
2023-06-30T15:12:13.989Z ERROR Unable to Write TLS credential
2023-06-30T15:12:13.989Z INFO Updating private key...
2023-06-30T15:12:13.989Z ERROR Unable to Write TLS credential
2023-06-30T15:12:13.989Z INFO Certificate update completed
2023-06-30T15:12:38.677Z INFO Getting serialport options from persistent store 000960072311.pc-nrfconnect-cellularmonitor
2023-06-30T15:12:38.687Z INFO Getting serialport options from persistent store 000960072311.pc-nrfconnect-cellularmonitor
2023-06-30T15:13:52.866Z INFO Updating CA certificate...
2023-06-30T15:13:52.866Z ERROR Unable to Write TLS credential
2023-06-30T15:13:52.867Z INFO Updating client certificate...
2023-06-30T15:13:52.867Z ERROR Unable to Write TLS credential
2023-06-30T15:13:52.867Z INFO Updating private key...
2023-06-30T15:13:52.867Z ERROR Unable to Write TLS credential
2023-06-30T15:13:52.867Z INFO Certificate update completed
2023-06-30T15:14:18.241Z INFO Updating CA certificate...
2023-06-30T15:14:18.241Z ERROR Unable to Write TLS credential
2023-06-30T15:14:18.241Z INFO Updating client certificate...
2023-06-30T15:14:18.242Z ERROR Unable to Write TLS credential
2023-06-30T15:14:18.242Z INFO Updating private key...
2023-06-30T15:14:18.242Z ERROR Unable to Write TLS credential
2023-06-30T15:14:18.242Z INFO Certificate update completed
2023-06-30T15:14:21.801Z INFO Updating CA certificate...
2023-06-30T15:14:21.802Z ERROR Unable to Write TLS credential
2023-06-30T15:14:21.802Z INFO Updating client certificate...
2023-06-30T15:14:21.802Z ERROR Unable to Write TLS credential
2023-06-30T15:14:21.802Z INFO Updating private key...
2023-06-30T15:14:21.802Z ERROR Unable to Write TLS credential
2023-06-30T15:14:21.802Z INFO Certificate update completed
2023-06-30T15:14:22.927Z INFO Updating CA certificate...
2023-06-30T15:14:22.927Z ERROR Unable to Write TLS credential
2023-06-30T15:14:22.927Z INFO Updating client certificate...
2023-06-30T15:14:22.927Z ERROR Unable to Write TLS credential
2023-06-30T15:14:22.927Z INFO Updating private key...
2023-06-30T15:14:22.927Z ERROR Unable to Write TLS credential
2023-06-30T15:14:22.928Z INFO Certificate update completed

I've changed the certs slightly for security.

Current printout in terminal is:

*** Booting Zephyr OS build v3.3.99-ncs1 ***
*** Booting Zephyr OS build v3.3.99-ncs1 ***
I: The AWS IoT sample started, version: v1.0.0
+CEREG: 2,"E03C","0012FE1E",7
I: LTE cell changed: Cell ID: 1244702, Tracking area: 57404
+CSCON: 1
I: RRC mode: Connected
%XTIME: ,"32600351245340","01"
+CEREG: 5,"E03C","0012FE1E",7,,,"11100000","11100000"
I: Network registration status: Connected - roaming
I: DaI: PSM parameter update: TAU: 6480, Active time: -1
te time obtained
I: Next connection retry in 30 seconds
I: AWS_IOT_EVT_CONNECTING
E: mqtt_connect, error: -111
I: AWS_IOT_EVT_CONNECTING

Main error seems to be mqtt_connect, error: -111

Any clues as to what I'm doing wrong?

[Capt. Flatus O'Flaherty]

Most recently:

16:52:57.548	Updating CA certificate...
16:52:59.265	Successfully deleted TLS credential
16:52:59.265	Updating client certificate...
16:52:59.490	Successfully deleted TLS credential
16:52:59.491	Updating private key...
16:52:59.704	Successfully deleted TLS credential
16:52:59.704	Certificate update completed
16:55:07.548	Deselected device
16:55:07.548	Closing device
16:55:07.581	Closed port: /dev/ttyACM0

.... but still same error.

[Capt. Flatus O'Flaherty]

Still got same mqtt error.

Just wondering if I'm uploading certificates properly. Should the headers be included eg. "-----BEGIN CERTIFICATE-----"?

Still not sure which CA certificate from AWS to upload as the are two diff versions ie AmazonRootCA1.pem and AmazonRootCA3.pem

But if there was a certificate error would it give me mqtt error?

[Capt. Flatus O'Flaherty]

Just looking through 'problems' list  in Visual Studio and I dont see any major problems other than this:

"CMake Error at /usr/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:230 (message):Could NOT find Python3 (missing: Interpreter) (Required is exact version
"3.10")

    Reason given by package:
        Interpreter: Cannot run the interpreter "/home/flatus/ncs/toolchains/1f9b40e71a/usr/local/bin/python3""

Although:

flatus@flatus:~/ncs/v2.4.0/nrf/modules/cjson/include$ python3 --version
Python 3.10.6

???

[Capt. Flatus O'Flaherty]

Certificates upload:
    Text block 1.The root CA (choose the Amazon Root CA 1, AmazonRootCA1.pem)
    Text block 2.Thing certificate (*-certificate.pem.crt)
    Text block 3.The private key (*.private.pem.key)