Hi,
I'm developing a custom board based on nRF9151 (similar to Thingy:91X) and trying to connect to nRF Cloud for location services (A-GNSS, Wi-Fi location, Cellular location).
## Environment
- nRF Connect SDK: v3.1.1
- Modem firmware: mfw_nrf91x1_2.0.4
- Board: Custom board with nRF9151 + nRF7002 (Wi-Fi) + GD25LE255E (external flash)
- nRF Cloud Plan: Developer (free)
## What I've done
1. **Claimed the device** using Attestation Token (`AT%ATTESTTOKEN`)
2. **Created Provisioning Rule** with:
- Client Private Key Generation (Succeeded)
- Certificate Signing Request (Succeeded)
- Server Certificate - AWS Root CA (Succeeded)
- Client Certificate - self-signed with my own CA (Succeeded)
3. **Installed certificates** to modem (security tag 16842753):
AT%CMNG=1,16842753 %CMNG: 16842753,0,"..." ← Server Certificate (AWS Root CA) %CMNG: 16842753,1,"..." ← Client Certificate (self-signed) %CMNG: 16842753,2,"..." ← Public Key
4. **Also tried security tag 16** (factory JITP), but it only has Public Key (Type 2), no Client Certificate.
## Problem
Connection to nRF Cloud CoAP always fails with error -111 (ECONNREFUSED):
transport: Connecting to nRF Cloud CoAP with client ID: 50433155-3335-4269-80e2-1a066ffdc628 nrf_cloud_coap_transport: Could not connect to nRF Cloud CoAP server coap.nrfcloud.com, port: 13334. err: -111
## Configuration (prj.conf)
CONFIG_NRF_CLOUD_CLIENT_ID_SRC_INTERNAL_UUID=y CONFIG_NRF_CLOUD_COAP_SEC_TAG=16842753
## Questions
1. **Is it possible to use a self-signed CA certificate with the Developer (free) plan?**
- Or do I need Pro/Enterprise plan to register my own CA?
2. **What is the correct provisioning workflow for custom boards (not Nordic DKs)?**
- Nordic DKs come with factory-provisioned certificates, but custom boards don't have them.
3. **Is there an alternative way to provision certificates for custom nRF9151 boards?**
Thank you for your help!
