<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Device onboarding: &amp;quot;certificate already exists&amp;quot;</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127235/device-onboarding-certificate-already-exists</link><description>Hi, 
 We have onboarded several hundred nrRF9151 devices using the nRF Cloud &amp;quot;bulk onboard&amp;quot; UI (preconnect onboarding using device_credentials_installer.py ). Generally, this works fine. 
 However, for two devices we are getting an error during onboarding</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 26 Mar 2026 12:10:19 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127235/device-onboarding-certificate-already-exists" /><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/564094?ContentTypeID=1</link><pubDate>Thu, 26 Mar 2026 12:10:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1a669a54-6fd7-4b85-9762-23c393c81682</guid><dc:creator>teba99</dc:creator><description>&lt;p&gt;Yes, these might be older. Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/564091?ContentTypeID=1</link><pubDate>Thu, 26 Mar 2026 11:28:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:df5532b6-26a8-4785-b9dd-8758763e9ddf</guid><dc:creator>Markku Lehto</dc:creator><description>&lt;p&gt;Hi Terrence,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Looks like these two were created originally in mid February and previous implementation of delete function left them in broken state.&lt;/p&gt;
&lt;p&gt;I have removed both certificates, so you should be ok to onboard them. Again, if you still face this issue, reopen the ticket.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Markku Lehto&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/564090?ContentTypeID=1</link><pubDate>Thu, 26 Mar 2026 10:57:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:599ac488-e1e6-45fd-aa62-51b9612e8def</guid><dc:creator>Markku Lehto</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Ok, just a moment. The fix we implemented previously did not fix this issue or was these two certificates deleted earlier?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Markku Lehto&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/564084?ContentTypeID=1</link><pubDate>Thu, 26 Mar 2026 09:36:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:064e257c-f1ac-4fee-a2c9-d102dfc35854</guid><dc:creator>teba99</dc:creator><description>&lt;p&gt;Hi Markku,&lt;/p&gt;
&lt;p&gt;We have two more certificates with the same issue. Can you please remove these as well?&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/certs3.zip"&gt;devzone.nordicsemi.com/.../certs3.zip&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/563489?ContentTypeID=1</link><pubDate>Tue, 17 Mar 2026 16:26:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:06de90ca-e490-4c3b-ac5f-55aaefc63966</guid><dc:creator>teba99</dc:creator><description>&lt;p&gt;Hi Markku,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Excellent. Thanks for the follow-up. We will let you know if we have issues.&lt;/p&gt;
&lt;p&gt;Best&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/563474?ContentTypeID=1</link><pubDate>Tue, 17 Mar 2026 14:49:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cc357674-7e98-4b81-a59a-6a99c5253d66</guid><dc:creator>Markku Lehto</dc:creator><description>&lt;p&gt;Hi Terrence,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Ok, the team has improved Delete Device API call. It will now have more relaxed retry logic and also more improvements trying to remove the device and the certificate.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m closing this ticket now, but as always if you still see similar issues don&amp;#39;t hesitate to open this ticket again.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you for your patience,&lt;/p&gt;
&lt;p&gt;Markku Lehto&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562741?ContentTypeID=1</link><pubDate>Fri, 06 Mar 2026 15:18:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:473a58a3-55cc-4671-b957-8de46b731307</guid><dc:creator>teba99</dc:creator><description>&lt;p&gt;Hi Markku,&lt;/p&gt;
&lt;p&gt;you&amp;#39;re right, the three that are associated&amp;nbsp;correctly show up&amp;nbsp;in&amp;nbsp;our team, that appears to be a mistake on our side. For the others, thanks, we&amp;#39;ll try to onboard those again.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562740?ContentTypeID=1</link><pubDate>Fri, 06 Mar 2026 15:02:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4f4688f9-8045-4cfa-8f90-880f0c73d79c</guid><dc:creator>Markku Lehto</dc:creator><description>&lt;p&gt;Hi Terrence,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I&amp;nbsp;checked&amp;nbsp;these devices and deleted orphaned certificates. Some of these devices seem to have onboarded just fine, see the list:&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;50343956-3037-411c-8009-091efaf720a7 removed orphaned certificate&lt;br /&gt;50343956-3037-4123-8037-0f1128bba843 associated, looks ok&lt;br /&gt;50343956-3037-43c5-8029-001906c2202a associated, looks ok&lt;br /&gt;50343956-3037-4563-80df-07227ae0c6d6 removed orphaned certificate&lt;br /&gt;50343956-3037-4693-8090-0c16d6b8bf49 removed orphaned certificate&lt;br /&gt;50343956-3037-48c9-8098-211d15f9aff1 removed orphaned certificate&lt;br /&gt;50343956-3037-4d66-808a-16273b09d886 removed orphaned certificate&lt;br /&gt;5034474b-3731-4fb9-8020-0713b6b5484e associated, looks ok&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I didn&amp;#39;t want to do anything for those devices that are with comment &amp;quot;associated, looks ok&amp;quot;. If you have issues with them, let me know. For others, I removed orphaned certificate. You can try to onboard them again. I filed a bug to the team and they will start investigating this. Let&amp;#39;s keep this ticket open until I have further information to tell about this issue or you bump into this again.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Markku Lehto&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562732?ContentTypeID=1</link><pubDate>Fri, 06 Mar 2026 13:39:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:26f8e5f0-48fd-4ddf-910b-095fb1ce6334</guid><dc:creator>Markku Lehto</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;ok, understood. Team will need to investigate this. In the meanwhile I will be removing these certificates for you. I will let you know when they are removed.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;-M&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562730?ContentTypeID=1</link><pubDate>Fri, 06 Mar 2026 13:34:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:470627fa-1ebf-4ff5-bda5-8b399e5966b4</guid><dc:creator>teba99</dc:creator><description>&lt;p&gt;Time between step 3 and 4: I believe at least several hours, if not days.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t think we saw any errors during step 3. First error was in step 4, for a subset of devices.&lt;/p&gt;
&lt;p&gt;I believe we onboarded several dozen devices in step 4.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Certs attached.&lt;/p&gt;
&lt;p&gt;Thanks&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/certs2.zip"&gt;devzone.nordicsemi.com/.../certs2.zip&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562722?ContentTypeID=1</link><pubDate>Fri, 06 Mar 2026 12:47:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:49b3c1ed-70c0-435d-beed-cc5d7bf792e8</guid><dc:creator>Markku Lehto</dc:creator><description>&lt;p&gt;Hi Terrence,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;We need to investigate this with the team. What is the time interval between step 3 and step 4? Did you see any errors? Steps 1 and 4 were done using bulk onboarding with csv, did you see any errors? Bulk onboarding is asynchronous call so it might take some time to complete. Could you estimate how many devices were onboarded at the same time?&lt;/p&gt;
&lt;p&gt;In the meanwhile, you need to send me all these certificates which were reported as a duplicate.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;-M&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562719?ContentTypeID=1</link><pubDate>Fri, 06 Mar 2026 12:20:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:eac70877-5cde-4c1c-8048-69f4cbecac40</guid><dc:creator>teba99</dc:creator><description>&lt;p&gt;Markku,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;we now have more devices where this is happening. What we do is:&lt;/p&gt;
&lt;p&gt;1. Onboard the devices in nRF Cloud teamA&lt;/p&gt;
&lt;p&gt;2. Test and configure the devices in teamA&lt;/p&gt;
&lt;p&gt;3. Delete the devices from teamA&lt;/p&gt;
&lt;p&gt;4. Onboard the devices in nRF Cloud teamB &amp;lt;-- this is where the problem occurs&lt;/p&gt;
&lt;p&gt;It seems, in step 3, for a&amp;nbsp;certain percentage of devices the certificates are not cleanly removed from the system.&lt;/p&gt;
&lt;p&gt;Can you please remove the&amp;nbsp;certificates for the following devices. Also, please let us know how we can avoid this issue going forward.&lt;/p&gt;
&lt;p class="p1"&gt;Thanks!&lt;/p&gt;
&lt;p class="p1"&gt;50343956-3037-4123-8037-0f1128bba843&lt;/p&gt;
&lt;p class="p1"&gt;50343956-3037-4693-8090-0c16d6b8bf49&lt;/p&gt;
&lt;p class="p1"&gt;50343956-3037-43c5-8029-001906c2202a&lt;/p&gt;
&lt;p class="p1"&gt;5034474b-3731-4fb9-8020-0713b6b5484e&lt;/p&gt;
&lt;p class="p1"&gt;50343956-3037-411c-8009-091efaf720a7&lt;/p&gt;
&lt;p class="p1"&gt;50343956-3037-4d66-808a-16273b09d886&lt;/p&gt;
&lt;p class="p1"&gt;50343956-3037-48c9-8098-211d15f9aff1&lt;/p&gt;
&lt;p class="p1"&gt;50343956-3037-4563-80df-07227ae0c6d6&lt;/p&gt;
&lt;p class="p1"&gt;50343956-3037-489d-80a0-0a155ddbaf74&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562543?ContentTypeID=1</link><pubDate>Wed, 04 Mar 2026 12:31:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:53bfd6af-fa4f-4636-b533-144625ec0cbd</guid><dc:creator>Markku Lehto</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;It seems that those two certificates were already registered in our system. For some reason they were orphaned, so no device was attached to them.&lt;/p&gt;
&lt;p&gt;I removed both of those certificates which seems to be from some earlier onboarding session. You should be good to go to onboard these two devices now.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;In case you still have issues, please reopen this ticket.&lt;/p&gt;
&lt;p&gt;Thank you for using nRF Cloud.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Markku Lehto&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562538?ContentTypeID=1</link><pubDate>Wed, 04 Mar 2026 11:47:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4f495f68-fc9f-495a-9225-2a88ef7799a9</guid><dc:creator>Markku Lehto</dc:creator><description>&lt;p&gt;Thanks Terrence,&lt;/p&gt;
&lt;p&gt;I will troubleshoot this further.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;-M&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562520?ContentTypeID=1</link><pubDate>Wed, 04 Mar 2026 09:33:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6a1a8860-ce12-487b-bed4-15f9be1102fa</guid><dc:creator>teba99</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We retried onboarding, but it still fails. Certificates attached.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/certs.zip"&gt;devzone.nordicsemi.com/.../certs.zip&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562518?ContentTypeID=1</link><pubDate>Wed, 04 Mar 2026 09:00:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aa2bf469-b920-4793-8362-2e1e3d2938a9</guid><dc:creator>Markku Lehto</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;ok I will removed&amp;nbsp;&lt;span&gt;50343956-3037-43c5-8029-001906c2202a and&amp;nbsp;&lt;/span&gt;&lt;span&gt;5034474b-3731-4fb9-8020-0713b6b5484e from the our registry again.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If it continues to fail to onboard these devices, could you send those two certificates for these two devices to me? I suspect the issue is related to these certificates.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If you could upload these certificates in PEM format to this ticket, I would be able to check them.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thank you,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Markku Lehto&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562463?ContentTypeID=1</link><pubDate>Tue, 03 Mar 2026 15:56:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:026b9eac-6435-4f05-a088-511da5461eeb</guid><dc:creator>teba99</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;50343956-3037-43c5-8029-001906c2202a: We verified this is correct and tried onboarding again, but&amp;nbsp;it continues to fail.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;5034474b-3731-4fb9-8020-0713b6b5484e: Yes,&amp;nbsp;25c3f2c9-732a-45c6-a580-c3b0f327af99 is one of our teams, but this device is not listed in the team. So we can&amp;#39;t remove it.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562445?ContentTypeID=1</link><pubDate>Tue, 03 Mar 2026 14:02:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:841425a7-8f55-422d-8890-5c6d53292014</guid><dc:creator>Markku Lehto</dc:creator><description>&lt;p&gt;Hi Terrence,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I searched devices from our database:&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;50343956-3037-43c5-8029-001906c2202a - could not be found&lt;/p&gt;
&lt;div&gt;&lt;span&gt;5034474b-3731-4fb9-8020-0713b6b5484e - registered to team id: 25c3f2c9-732a-45c6-a580-c3b0f327af99. Is that yours?&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;Markku Lehto&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562374?ContentTypeID=1</link><pubDate>Tue, 03 Mar 2026 07:10:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:930b3197-b7d0-4f6b-b091-86b721e63d15</guid><dc:creator>teba99</dc:creator><description>&lt;p&gt;Hi Markku,&lt;/p&gt;
&lt;p&gt;Correct, we are using that method to register our devices. The two devices are&amp;nbsp;&lt;span data-teams="true"&gt;50343956-3037-43c5-8029-001906c2202a und 5034474b-3731-4fb9-8020-0713b6b5484e.&lt;br /&gt;&lt;br /&gt;Thanks&lt;br /&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562373?ContentTypeID=1</link><pubDate>Tue, 03 Mar 2026 07:05:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c484375d-3c0b-47c5-80c9-e719bf8796a1</guid><dc:creator>Markku Lehto</dc:creator><description>&lt;p&gt;Hi Terrence,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;We need to investigate what might be the reason for &amp;quot;certificate already exists&amp;quot; error message. Could you give us device UUIDs for those two devices you had issues with it?&lt;/p&gt;
&lt;p&gt;Also, I assume you are using&amp;nbsp;&lt;a href="https://github.com/nRFCloud/utils?tab=readme-ov-file#how-to-registering-devices-quickly"&gt;https://github.com/nRFCloud/utils?tab=readme-ov-file#how-to-registering-devices-quickly&lt;/a&gt;&amp;nbsp;to register your devices. Also, if you could add those certificates to this ticket as well which caused the error message.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Device onboarding: "certificate already exists"</title><link>https://devzone.nordicsemi.com/thread/562352?ContentTypeID=1</link><pubDate>Mon, 02 Mar 2026 17:08:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:67a06603-252d-4306-8e73-0668ef285732</guid><dc:creator>Natasha_C</dc:creator><description>&lt;p&gt;Hi there,&lt;/p&gt;
&lt;p&gt;I’m sorry you’re experiencing this issue.&lt;/p&gt;
&lt;p&gt;We’ll look into it and follow up with you as soon as we have an update.&lt;/p&gt;
&lt;p&gt;Thank you for your understanding&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>