When generating certificates according to this guide for the nRF9160 Feather, I noticed that there are two certificates in the clientCert area. Is this expected?
I've yet to be able to connect to nrF Cloud. Here's the error:
[00:00:03.180,694] <dbg> nrf_cloud_transport.nct_mqtt_connect: mqtt_connect requesting persistent session
[00:00:08.192,840] <inf> nrf_cloud_transport: Using non-blocking socket
[00:00:08.200,134] <dbg> nrf_cloud.nrf_cloud_run: Cloud connection request sent.
[00:00:08.511,535] <dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_CONNACK: result -111
[00:00:08.520,965] <dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 1
[00:00:08.528,839] <dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_ERROR: -111
[00:00:08.536,773] <inf> asset_tracker: CLOUD_EVT_ERROR
[00:00:09.042,694] <dbg> nrf_cloud.nrf_cloud_run: Socket error: POLLNVAL
[00:00:09.049,987] <dbg> nrf_cloud.nrf_cloud_run: The cloud socket was unexpectedly closed.
[00:00:09.059,020] <inf> asset_tracker: CLOUD_EVT_DISCONNECTED: 2
[00:00:09.065,673] <inf> asset_tracker: Cloud connection closed.
[00:00:09.072,235] <inf> asset_tracker: This can occur during initial nRF Cloud provisioning.
I've tried this every which way according to the guide above. I'm also making sure the certs are "installed" using AT%CMNG=1
%CMNG: 0,6,"0606060606060606060606060606060606060606060606060606060606060606"
%CMNG: 16842753,0,"0000000000000000000000000000000000000000000000000000000000000000"
%CMNG: 16842753,1,"0101010101010101010101010101010101010101010101010101010101010101"
%CMNG: 16842753,2,"0202020202020202020202020202020202020202020202020202020202020202"
I'm likely doing something very stupid here. I'll come back to it with some fresh eyes in a bit.
