nRF Cloud provisioning stuck - Server Certificate failed, Client Certificate pending

RE: nRF Cloud provisioning stuck - Server Certificate failed, Client Certificate pending

Juha Y — Fri, 23 Jan 2026 11:16:48 GMT

You can also get attestation token when running nrf_provisioning sample. Just enter command nrf_provisioning token to serial terminal.

Have you tried to use the REST API to unclaim the device? This will delete all provisioning related states and commands from the server. Below is an example for linux. You need to add the nRFCloud API_KEY from your User Account (Don't expose the key here)

export API_HOST=https://api.provisioning.nrfcloud.com
export DEV_UUID=50343959-3733-433f-80d9-161fa7776bfc
export API_KEY=

curl -X DELETE $API_HOST/v1/claimed-devices/$DEV_UUID -H "Authorization: Bearer $API_KEY"

Link to the API document https://api.provisioning.nrfcloud.com/v1/

BR,

Juha

RE: nRF Cloud provisioning stuck - Server Certificate failed, Client Certificate pending

pearcestephen — Fri, 23 Jan 2026 09:07:44 GMT

I have been unable to get an attestation token. I can load my own app and anything from samples including AT but that command to get the token simply never returns anything. But then I said all this in my e-mail above so please could you look at the last line Request and tell me whether you can actually do that because literally everything else was already tried. For completeness here is the request again:

Request: Please manually delete all provisioning records, certificates, and device state associated with UUID 50343959-3733-433f-80d9-161fa7776bfc so I can provision fresh.

RE: nRF Cloud provisioning stuck - Server Certificate failed, Client Certificate pending

Juha Y — Fri, 23 Jan 2026 08:45:31 GMT

[quote userid="145365" url="~/f/nordic-q-a/126558/nrf-cloud-provisioning-stuck---server-certificate-failed-client-certificate-pending/559423"]AT%ATTESTTOKEN returns a token, but I have nowhere to use it since the device isn't in Claimed Devices[/quote]

Hi,

Attestation token is used to claim the device. Have you tried to claiming from the Security Services → Claimed Devices?
* Click the Claim Device button.
* Copy and paste the attestation token into the Claim token text box.

BR,
Juha

RE: nRF Cloud provisioning stuck - Server Certificate failed, Client Certificate pending

pearcestephen — Fri, 23 Jan 2026 02:32:14 GMT

Hi,

I've exhausted all device-side and self-service options. The device does not appear in:

Security Services → Claimed Devices
Security Services → Provisioning

Device Identifiers:

UUID: 50343959-3733-433f-80d9-161fa7776bfc
IMEI: 359404230238199

What I've tried:

Full J-Link recover (west flash --recover)
Wiped credentials via AT%CMNG commands on sec_tag 16842753
Manually wrote Amazon Root CA 1
Ran nrf_provisioning sample (returns "Bad request" / "Invalid exchange")
AT%ATTESTTOKEN returns a token, but I have nowhere to use it since the device isn't in Claimed Devices

Current state:

Device boots and runs firmware normally
LTE connects successfully (CEREG: 5)
MQTT connection to mqtt.nrfcloud.com:45858 fails with error -111 (connection refused)

The provisioning state for this device appears to be stuck/corrupted on the nRF Cloud backend in a way that isn't exposed through the portal.

Request: Please manually delete all provisioning records, certificates, and device state associated with UUID 50343959-3733-433f-80d9-161fa7776bfc so I can provision fresh.

Thank you.

RE: nRF Cloud provisioning stuck - Server Certificate failed, Client Certificate pending

dejans — Fri, 16 Jan 2026 13:40:28 GMT

Hi,

For reference, here are relevant documentation links
managing provisioning commands
finding and resolving failed commands using nrfcloud portal

Best regards,
Dejan

RE: nRF Cloud provisioning stuck - Server Certificate failed, Client Certificate pending

Juha Y — Fri, 16 Jan 2026 12:03:09 GMT

Hi, you should be able to reset the provisioning state from nrfcloud.com portal. Click Security Services and then Claimed Devices or try this link https://app.nrfcloud.com/#/claimed-devices

Best Regards,
Juha