martin bradley

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

7 years, 3 months ago.

mbed-client

I've been using mbed-client/connector for months without issue. The mbed-client/connector is very solid.

A couple days ago 3 of my K64Fs devices stopped connecting to api.connector.mbed.com:5684.

-----------

Using Ethernet

Connected to Network successfully IP address 192.168.1.103

SOCKET_MODE : UDP Connecting to coap:api.connector.mbed.com:5684 Start [ERROR:] M2MInterface::SecureConnectionFailed

-----------

I seem to be getting an address but the devices hang for a while then error. The error message is coming from my device so its not much value. At first I thought it was something with my router or my ISP blocking a port.

I thought about setting up Linux client to test my side but haven't got that far.

Does anyone have any ideas that I might try?

Are there any tools to test a client connection to api.connector.mbed.com?

Thank You,

Martin

Try regenerating your security certificates. As connector is in a public beta currently I believe its security certs reset at the end of every year.

posted by Austin Blackstone 06 Jan 2017

1 Answer

Fred Li
7 years, 3 months ago.

Hi Martin,

I'd suggest you may try with TCP socket mode connection.

Sometimes because of the network limitation or firewall setting, the UDP connection may not stable and easy to met issue.

The socket mode could be changed in the simpleclient.h file. 

M2MInterface::BindingMode SOCKET_MODE = M2MInterface::TCP;

Thanks.

Fred.

Accepted Answer

Following your advice I created a new project in MBED Compiler using the most recent - mbed-os-example-client from git which uses M2MInterface::TCP.

The device registers with MBED Connector OK now.

posted by martin bradley 05 Jan 2017