Unable to connect to cloud via Wifi - Rapidly Flashing Cyan

I’m having trouble with an argon board rapidly blinking Cyan. I followed all of the documentation I could find, set the server keys, and the device keys.

I’ve gone through key doctor multiple times and run the cloud debugger restored to different firmwares to no aval.

Has anyone else had similar issues? I get as far as the device trying to send Hello message to the cloud and then it says Internet available, cloud not reachable followed by Cloud handshake failed, code=-160 it seems to stay in a endless loop there…

Longer log below.

0000005354 [ncp.esp32.mux] INFO: Openning mux channel 2
0000006606 [ncp.esp32.client] TRACE: Connecting to “IOT”
0000008516 [ncp.esp32.at] TRACE: < WIFI CONNECTED
0000009451 [ncp.esp32.at] TRACE: < OK
0000009452 [ncp.esp32.client] TRACE: NCP connection state changed: 2
0000009452 [net.esp32ncp] TRACE: NCP event 2
0000009453 [net.esp32ncp] TRACE: State changed event: 2
0000009454 [net.ifapi] INFO: Netif wl3 link UP
0000009454 [system.nm] INFO: State changed: IFACE_UP → IFACE_LINK_UP
0000009482 [ncp.mgr] TRACE: Updated file: /sys/wifi_config.bin
0000010005 [app] INFO: counter=2
0000010585 [hal] INFO: DNS server list changed
0000010585 [hal] INFO: DNS server list changed
0000010586 [net.ifapi] TRACE: Netif wl3 ipv4 configuration changed
0000010587 [system.nm] INFO: State changed: IFACE_LINK_UP → IP_CONFIGURED
0000010593 [system] INFO: Cloud: connecting
0000010594 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io
0000010595 [system] WARN: Failed to load session data from persistent storage
0000010596 [system] INFO: Discarding session data
0000010597 [system] TRACE: Resolving e00fce6806afadd50fa3c6a5.v5.udp.particle.io#5684
0000010794 [system] TRACE: Address type: 3
0000010794 [system] TRACE: Cloud socket=0, family=2, type=2, protocol=17
0000010795 [system] INFO: Cloud socket=0, connecting to 52.5.139.123#5684
0000010796 [system] TRACE: Cloud socket=0, connected to 52.5.139.123#5684
0000010797 [system] TRACE: Updating cloud keepalive for AF_INET: 25000 → 25000
0000010797 [system] TRACE: Applying new keepalive interval now
0000010798 [system] INFO: Cloud socket connected
0000010799 [system] INFO: Starting handshake: presense_announce=0
0000010799 [comm.protocol.handshake] INFO: Establish secure connection
0000010802 [comm.dtls] INFO: (CMPL,RENEG,NO_SESS,ERR) restoreStatus=2
0000011151 [comm.protocol.handshake] INFO: Sending HELLO message
0000086565 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 0
0000086566 [comm.protocol.handshake] ERROR: Could not send HELLO message: 10
0000086864 [serivce.ntp] TRACE: NTP time: 2022-08-30T20:33:22.188170Z
0000086864 [system] WARN: Internet available, cloud not reachable
0000086865 [system] WARN: Cloud handshake failed, code=-160
0000087115 [system] INFO: Cloud: disconnecting
0000087115 [system] INFO: Cloud: disconnected
0000087615 [system] INFO: Cloud: connecting
0000087617 [system] INFO: Read Server Address = type:1,domain:$id.udp.particle.io

We are taking a look, please keep the device attempting to connect and it may auto-resolve.

Much appreciated! I’ve been fighting with this thing all day. I couldn’t find where to submit a support ticket in the support page.

This is definitely the right place to post!

Hey - looks like this device has been unplugged, can you give it a power-cycle and leave it powered on for a bit?

Its still going as far as I can see.

0003294930 [system] WARN: Resetting network interfaces due to failed connection attempts for 5 minutes
0003294931 [system] WARN: Cloud handshake failed, code=-160
0003295181 [system] INFO: Cloud: disconnecting
0003295181 [system] INFO: Cloud: disconnected
0003295182 [system.nm] INFO: State changed: IP_CONFIGURED → IFACE_REQUEST_DOWN
0003295182 [net.ifapi] INFO: Netif wl3 state DOWN
0003295187 [system.nm] INFO: State changed: IFACE_REQUEST_DOWN → IFACE_DOWN

Should I still power cycle? Its back to trying to connect to cloud.
0003377689 [comm.protocol.handshake] INFO: Establish secure connection
0003377692 [comm.dtls] INFO: (CMPL,RENEG,NO_SESS,ERR) restoreStatus=2
0003378036 [comm.protocol.handshake] INFO: Sending HELLO message

I’m off for the day but will leave it attempting to connect.

The fix is live in production.

1 Like

Much appreciated! What happened? Was this specific to a configuration change I unknowingly made?

Nope, there were a very small number of devices struggling with a configuration change on our end. This has since been fixed.

It has indeed improved, I’m no longer having an issue connecting to the cloud. However… Now I am dropping WiFi and unable to reconnect. I pulled the device diagnostics from the cloud and I see that the device.cloud.connection.error has primarily error code -220 with some Error code 10’s.

Everything else seems OK. Unfortunately I have just had this mounted about 25 feet off the ground so connecting via USB will be tricky.