mqtt_connect fails with error -95 aws_fota

[lecozahu]

Hi !

I am working on aws_fota, with a nrf9160 dk, sdk 1.3.0. When I try to connect in mqtt, I get my IPv4 address I get the following message: ERROR - mqtt_connect -95.
When I try to debug myself, I notice that my error appears on line 97 :     ret = connect(client->transport.tls.sock, client->broker, peer_addr_size); 

of the mqtt_transport_socket_tls.c file within its mqtt_client_tls_connect () function.

could you help me ? thanks in advance

[Carl Richard]

Hello, lecozahu!

What sample have you based your project on and what amendments have you made? 

Error -95 is probably EOPNOTSUPP, meaning that the requested operation is not supported on the socket. 

Best regards,
Carl Richard

[lecozahu]

Carl Richard,

I was based on the aws_fota project, I did not touch the main, it is during the initialization of the client that the error appears.
I modified several things:
- I have defined CONFIG_PROVISION_CERTIFICATES
-I modified the certificate with the private, public and CA keys
-I modified in Kconf the address of the broker ending with amazonaws.com
- I modified CONFIG_CLOUD_CLIENT_ID and put it in the name of the object created on aws.
-I kept port 8883

Best regards,

lecozahu

[lecozahu]

Hello again!

Yes, I have "... \ n" \ on each line.

For certificates, I have two non-private keys provided by AWS.
A file: .cert.perm that I put in the zone: CLOUD_CA_CERTIFICATE
an another file :  .public.key file that I put in the zone: CLOUD_CLIENT_PUBLIC_CERTIFICATE

Could my error come from there?

Best regards,

[Carl Richard]

That could be your error, yes.

The CLOUD_CLIENT_PUBLIC_CERTIFICATE should contain the .cert.perm you received. The CLOUD_CA_CERTIFICATE should contain the AWS root certificate which is found here. Hope this helps!

Best regards,
Carl Richard

[lecozahu]

I took the first RSA 2048 certificate (I'm not sure which one exactly to take) but it still doesn't work. I still get the same error...

best regards,

Lecozahu

[lecozahu]

I did not modify the variable: CONFIG_CLOUD_CERT_SEC_TAG. Could this be the explanation?

Best regards,

Lecozahu

[Carl Richard]

That should not be the problem, as I did not modify it either and successfully established a connection. 

However, I managed to get the -95 error by using the wrong certificates (as you did previously), so I just want to ensure that your certificates are correct:

CLOUD_CLIENT_PRIVATE_KEY contains the <unique_id>-private.pem

CLOUD_CLIENT_PUBLIC_CERTIFICATE contains the  <unique_id>-certificate.pem

CLOUD_CA_CERTIFICATE contains AmazonRootCA1.pem

Is this your current certificates.h configuration? 

You have probably followed the readme for the sample, but make sure that every step is correct. 

Best regards
Carl Richard

[lecozahu]

Indeed, I did not take the correct amazon root certificate. I can now connect.

thanks a lot for your help!

Best regards,

Lecozahu

[Carl Richard]

My pleasure! Glad I could help!

Best regards,
Carl Richard