Argon - connecting to the Particle cloud failing

argon
Tags: #<Tag:0x00007fe21ee20448>

#1

We are trying to use an Argon board at a customer site and we are having trouble connecting to the Particle cloud. The chip blinks cyan quickly but never connects. We thought it was a firewall issue so we had the customer open ports 53 & 5684. I put debug logging on in the application by calling:

SerialLogHandler g_logSerial(LOG_LEVEL_ALL);

On a call to Particle.connect(); - we get the following errors:

0000060401 [comm.dtls] ERROR: handshake failed -6800

0000060403 [comm.protocol.handshake] ERROR: handshake failed with code 17

The protocol the customer is using is a hidden network with a specific port to allow us access to the internet instead of their standard WPA2 enterprise authentication which is not allowed using Argon.

The full log for the session is below, any help you can give us would be appreciated, we at a standstill with this customer now.

Attempting to connect to the Particle cloud…

0000014961 [system] INFO: Cloud: connecting

0000014963 [system] INFO: Read Server Address = type:1,domain:$id.udp-mesh.particle.io

0000014963 [system] ERROR: Failed to load session data from persistent storage

0000014964 [system] INFO: Discarding session data

0000014966 [system] TRACE: Resolving e00fce6874abb64447808eb1.udp-mesh.particle.io#5684

0000015093 [system] TRACE: Address type: 3

0000015094 [system] TRACE: Cloud socket=0, family=2, type=2, protocol=17

0000015094 [system] INFO: Cloud socket=0, connecting to 18.214.75.38#5684

0000015095 [system] TRACE: Cloud socket=0, connected to 18.214.75.38#5684

0000015095 [system] TRACE: Updating cloud keepalive for AF_INET: 30000 -> 30000

0000015097 [system] TRACE: Applying new keepalive interval now

0000015097 [system] INFO: Cloud socket connected

0000015098 [system] INFO: Starting handshake: presense_announce=0

0000015098 [comm.protocol.handshake] INFO: Establish secure connection

0000015362 [ncp.at] TRACE: > AT+MVER

0000015393 [ncp.at] TRACE: < 5

0000015394 [ncp.at] TRACE: < OK

0000015396 [comm.dtls] INFO: (CMPL,RENEG,NO_SESS,ERR) restoreStatus=2

0000060401 [comm.dtls] ERROR: handshake failed -6800

0000060403 [comm.protocol.handshake] ERROR: handshake failed with code 17

0000060403 [system] WARN: Cloud handshake failed, code=17

0000060654 [system] INFO: Cloud: disconnecting

0000060654 [system] INFO: Cloud: disconnected

0000061454 [system] INFO: Cloud: connecting


#2

Does the device occasionally blink red in between the cyan blinks?


#3

Yes it does…


#4

Can you try

particle keys doctor <device id> 
particle keys server

and then see if it connects?


#5

You should see something like this for a successful connection (the IP address will be different):

0000412266 [system] TRACE: Cloud socket=0, family=2, type=2, protocol=17
0000412267 [system] INFO: Cloud socket=0, connecting to 52.44.106.75#5684
0000412444 [system] TRACE: Cloud socket=0, connected to 52.44.106.75#5684
0000412446 [system] TRACE: Updating cloud keepalive for AF_INET: 30000 -> 30000
0000412578 [system] TRACE: Applying new keepalive interval now
0000412580 [system] INFO: Cloud socket connected
0000412711 [system] INFO: Starting handshake: presense_announce=0
0000412713 [comm.protocol.handshake] INFO: Establish secure connection
0000413298 [ncp.at] TRACE: > AT+MVER
0000413314 [ncp.at] TRACE: < 5
0000413315 [ncp.at] TRACE: < OK
0000413321 [comm.dtls] INFO: (CMPL,RENEG,NO_SESS,ERR) restoreStatus=2
0000414968 [comm.protocol.handshake] INFO: Sending HELLO message
0000415265 [comm.protocol.handshake] INFO: Handshake completed

#6

I will need to schedule to back back into the customer network, but trying this in our office network and the command fails

Still does not connect and here is the output from putty
0000020088 [system] TRACE: Address type: 3
0000020088 [system] TRACE: Cloud socket=0, family=2, type=2, protocol=17
0000020089 [system] INFO: Cloud socket=0, connecting to 3.229.54.1#5684
0000020089 [system] TRACE: Cloud socket=0, connected to 3.229.54.1#5684
0000020090 [system] TRACE: Updating cloud keepalive for AF_INET: 30000 -> 30000
0000020090 [system] TRACE: Applying new keepalive interval now
0000020091 [system] INFO: Cloud socket connected
0000020091 [system] INFO: Starting handshake: presense_announce=0
0000020092 [comm.protocol.handshake] INFO: Establish secure connection
0000020354 [ncp.at] TRACE: > AT+MVER
0000020388 [ncp.at] TRACE: < 5
0000020388 [ncp.at] TRACE: < OK
0000020390 [comm.dtls] INFO: (CMPL,RENEG,NO_SESS,ERR) restoreStatus=2
0000020790 [comm.protocol.handshake] INFO: Sending HELLO message
0000088726 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 0
0000088727 [comm.protocol.handshake] ERROR: Could not send HELLO message: 10
0000088728 [system] WARN: Cloud handshake failed, code=10
0000088978 [system] INFO: Cloud: disconnecting
0000088978 [system] INFO: Cloud: disconnected
0000089778 [system] INFO: Cloud: connecting
0000089780 [system] INFO: Read Server Address = type:1,domain:$id.udp-mesh.particle.io


#7

Hi there! I don’t believe this is a keys issue. We will likely have to ask a number of questions about your network in order to get this sorted. Would you mind opening up a support ticket (support.particle.io) and we’ll dive in deeper?