Unable to recover Argon - bad key? (orange blink)

Hi all, I’m in the process of onboarding Argons; so far, out of 10 Argons, I’ve had three of what seems to be “bad key” errors, and can’t seem to recover two of them (particle leys server; particle keys doctor [longalphanumericID]).
I’ve also tried to save the key and send it in per the recovery instructions, with no result.
I’ve previously brought another 5 argons online without issues, so the score currently is about 12 successes without issues, and three failures, with one I eventually recovered.
Any advice on how to proceed and recover these two argons? (And resolve any further key issues?)
Thanks.

Hi James-

Are these devices used by any chance? This issue is not unheard of in used devices. Try the device restore tool and then try keys doctor again. Let me know what happens, specifically if there are any changes.

Hi Colleen, the devices are direct from Particle wholesale; so my assumption is new. Running the web recovery tool and regenerating the keys brought the one device back, but not the other two; but I’ll give it another try in a few hours when I’m back with the devices again.
Thanks,
James

I would run the Web Device Doctor and capture a log of the connection process. This may indicate specifically what is failing during the connection process.

(You can also use the cloud debug firmware, but the two tools have the same connection debugging code.)

Hi Rickkas, unfortunately I can’t seem to get the Doctor tool to use Ethernet, despite selecting it in the advanced options - there is no apparent means to not use Wifi here? I end up with a slew of -230 / DNS errors.

image
image

Device ID: 
ICCID: 
IMEI: 
Modem Manufacturer: 
Modem Model: 
Modem Firmware Version: 
Power Supply: 
Battery: 
Battery SoC: 
Country: 
Carrier: 
Access Technology: 
Band: 
Cellular Global Identity: 
0000000291 [system.nm] INFO: State changed: DISABLED -> IFACE_DOWN
0000002603 [ncp.esp32.mux] INFO: Starting GSM07.10 muxer
0000002604 [ncp.esp32.mux] INFO: Openning mux channel 0
0000002605 [ncp.esp32.mux] INFO: GSM07.10 muxer thread started
0000002609 [ncp.esp32.mux] INFO: Openning mux channel 1
0000005313 [app] INFO: Auto-connect disabled
0000005989 [app] INFO: doing wifiScan
0000005993 [app] INFO: Doing Wi-fi scan
0000008504 [app] INFO: wiFiScan resultCount=6
0000034111 [app] INFO: setting credentials
0000034186 [system.nm] INFO: State changed: IFACE_DOWN -> IFACE_REQUEST_UP
0000034192 [net.ifapi] INFO: Netif wl3 state UP
0000034193 [system.nm] INFO: State changed: IFACE_REQUEST_UP -> IFACE_UP
0000036710 [ncp.esp32.mux] INFO: Openning mux channel 2
0000040826 [net.ifapi] INFO: Netif wl3 link UP
0000040826 [system.nm] INFO: State changed: IFACE_UP -> IFACE_LINK_UP
0000040878 [hal] INFO: DNS server list changed
0000040880 [system.nm] INFO: State changed: IFACE_LINK_UP -> IP_CONFIGURED
0000040881 [system] INFO: Cloud: connecting
0000040884 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000040886 [system] WARN: Failed to load session data from persistent storage
0000040886 [system] INFO: Discarding session data
0000040921address
0000046138 [system] WARN: Cloud socket connection failed: -230
0000046147 [system] WARN: Internet test failed: DNS
0000046147 [system] WARN: Handling cloud error: 2
d to determine server address
0000042039 [system] WARN: Cloud socket connection failed: -230
0000045092 [system] WARN: Internet test failed: DNS
0000045092 [system] WARN: Handling cloud error: 2
0000045093 [system] INFO: Cloud: connecting
0000045097 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000045098 [system] WARN: Failed to load session data from persistent storage
0000045099 [system] INFO: Discarding session data
0000046138 [system] ERROR: Failed to determine server  [system] ERROR: Failed to determine server address
0000040921 [system] WARN: Cloud socket connection failed: -230
0000040930 [system] WARN: Internet test failed: DNS
0000040931 [system] WARN: Handling cloud error: 2
0000042002 [system] INFO: Cloud: connecting
0000042005 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000042006 [system] WARN: Failed to load session data from persistent storage
0000042007 [system] INFO: Discarding session data
0000042039 [system] ERROR: Faile0000047209 [system] INFO: Cloud: connecting
0000047212 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000047213 [system] WARN: Failed to load session data from persistent storage
0000047214 [system] INFO: Discarding session data
0000047257 [system] ERROR: Failed to determine server address
0000047259 [system] WARN: Cloud socket connection failed: -230
0000047267 [system] WARN: Internet test failed: DNS
0000047267 [system] WARN: Handling cloud error: 2
0000048309 [system] INFO: Cloud: connecting
0000048312 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000048313 [system] WARN: Failed to load session data from persistent storage
0000048314 [system] INFO: Discarding session data
0000048364 [system] ERROR: Failed to determine server address
0000048364 [system] WARN: Cloud socket connection failed: -230
0000048375 [system] WARN: Internet test failed: DNS
0000048375 [system] WARN: Handling cloud error: 2
0000049403 [system] INFO: Cloud: connecting
0000049406 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000049407 [system] WARN: Failed to load session data from persistent storage
0000049408 [system] INFO: Discarding session data
0000049470 [system] ERROR: Failed to determine server address
0000049471 [system] WARN: Cloud socket connection failed: -230
0000049489 [system] WARN: Internet test failed: DNS
0000049489 [system] WARN: Handling cloud error: 2
0000051546 [system] INFO: Cloud: connecting
0000051549 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000051550 [system] WARN: Failed to load session data from persistent storage
0000051551 [system] INFO: Discarding session data
0000051572 [system] ERROR: Failed to determine server address
0000051572 [system] WARN: Cloud socket connection failed: -230
0000051594 [system] WARN: Internet test failed: DNS
0000051594 [system] WARN: Handling cloud error: 2
0000053643 [system] INFO: Cloud: connecting
0000053646 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000053647 [system] WARN: Failed to load session data from persistent storage
0000053648 [system] INFO: Discarding session data
0000053696 [system] ERROR: Failed to determine server address
0000053696 [system] WARN: Cloud socket connection failed: -230
0000053710 [system] WARN: Internet test failed: DNS
0000053710 [system] WARN: Handling cloud error: 2
0000055746 [system] INFO: Cloud: connecting
0000055749 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000055750 [system] WARN: Failed to load session data from persistent storage
0000055751 [system] INFO: Discarding session data
0000055774 [system] ERROR: Failed to determine server address
0000055774 [system] WARN: Cloud socket connection failed: -230
0000055789 [system] WARN: Internet test failed: DNS
0000055789 [system] WARN: Handling cloud error: 2
0000057846 [system] INFO: Cloud: connecting
0000057849 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000057850 [system] WARN: Failed to load session data from persistent storage
0000057851 [system] INFO: Discarding session data
0000057893 [system] ERROR: Failed to determine server address
0000057895 [system] WARN: Cloud socket connection failed: -230
0000057903 [system] WARN: Internet test failed: DNS
0000057903 [system] WARN: Handling cloud error: 2
0000059911 [system] INFO: Cloud: connecting
0000059914 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000059915 [system] WARN: Failed to load session data from persistent storage
0000059916 [system] INFO: Discarding session data
0000059949 [system] ERROR: Failed to determine server address
0000059949 [system] WARN: Cloud socket connection failed: -230
0000059958 [system] WARN: Internet test failed: DNS
0000059958 [system] WARN: Handling cloud error: 2
0000064003 [system] INFO: Cloud: connecting
0000064006 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000064007 [system] WARN: Failed to load session data from persistent storage
0000064008 [system] INFO: Discarding session data
0000064043 [system] ERROR: Failed to determine server address
0000064043 [system] WARN: Cloud socket connection failed: -230
0000064052 [system] WARN: Internet test failed: DNS
0000064052 [system] WARN: Handling cloud error: 2
0000068140 [system] INFO: Cloud: connecting
0000068143 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000068144 [system] WARN: Failed to load session data from persistent storage
0000068145 [system] INFO: Discarding session data
0000068189 [system] ERROR: Failed to determine server address
0000068189 [system] WARN: Cloud socket connection failed: -230
0000068200 [system] WARN: Internet test failed: DNS
0000068200 [system] WARN: Handling cloud error: 2
0000072248 [system] INFO: Cloud: connecting
0000072251 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000072252 [system] WARN: Failed to load session data from persistent storage
0000072253 [system] INFO: Discarding session data
0000072284 [system] ERROR: Failed to determine server address
0000072284 [system] WARN: Cloud socket connection failed: -230
0000072308 [system] WARN: Internet test failed: DNS
0000072308 [system] WARN: Handling cloud error: 2

Ok, one of the devices is now connecting properly. In the process, I have in addition to all of the fun stuff before(via the webtools and command-line both) tried resetting to Tinker on the latest device OS, then back to LTS 4.0.0 - no change - same thing with trying to use keys doctor.

Connection was successful after performing the following:

particle usb dfu
particle keys new
particle keys load device.der
particle keys send -v --product_id <prjID> <deviceID>  device.pub.pem

Then reset the device.

Gooooo figure :stuck_out_tongue:
I’ll try with the other one that is stuck, and see if it also responds can be corrected in the same fashion.

The problem with Wi-Fi setup being shown when using Web Device Doctor in Ethernet mode has been fixed:

When using Web Device Doctor with the Ethernet advanced setup option, it no longer goes into the Wi-Fi setup or Activate SIM screens and instead jumps right to waiting for the device to come online.

Following back up on this: so far, the other problematic device was able to connect without difficulties (without needing to do any further manipulation of keys).