-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Replies: 1 comment · 7 replies
-
I think it's related to CONFIG_NET_SOCKETS_CONNECT_TIMEOUT, default is 3000, you should increase it. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi @rerickson1 Here is the log after enabling the mbedtls
|
Beta Was this translation helpful? Give feedback.
All reactions
-
There is an issue verifying your TLS certificate. Is TLS SNI and/or peer verification enabled? Are you using self signed certs? |
Beta Was this translation helpful? Give feedback.
All reactions
-
These are the configs I am using.
@rerickson1 I am not an expert on the network side, so some of the information I provide may not be relevant. I apologize for that. From what I understand, you are asking about... Yes peer verification is enabled.
No, I downloaded and hardcoded the AWS certs (CA, private key, and certificate) into the application in this example. I am using the exact same application and compiling it with Zephyr 3.6.0. It works. |
Beta Was this translation helpful? Give feedback.
All reactions
-
I bet the default ciphers enabled with 4.x changed. Compare your mbedtls kconfigs from 3.6 and 4.0 to see what are enabled. |
Beta Was this translation helpful? Give feedback.
All reactions
-
@zafersn I believe this is directly related to #81672 (comment) I am looking into what changed and how to fix. |
Beta Was this translation helpful? Give feedback.
-
My application was working with zephyrV3.6-Branch revision. I tested my app with zephyr4.0-Branch and getting this error now:
mqtt_connect, error: -11
[00:02:23.171,000] aws_iot: AWS broker connect failed -11
just before failing: zsock_connect return -1.
Can anyone please help on this.
here is full log:
I put some additional logs to trace what exactly issue:
Beta Was this translation helpful? Give feedback.
All reactions