Hi!
I have an NRF9151LACA AEA device and I'm trying to get it to work. Got the IMEI and the device successfully connects to cellular network.
However, I can't get HTTPS to work - giving error 111
I see this on my custom firmware, but also on the official https_client:
*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 *** *** Using Zephyr OS v3.6.99-100befc70c74 *** HTTPS client sample started Bringing network interface up Provisioning certificate Provisioning certificate Connecting to the network +CGEV: EXCE STATUS 0 +CEREG: 2,"1CCA","05D14079",7 +CSCON: 1 +CGEV: ME PDN ACT 0,0 +CNEC_ESM: 50,0 +CEREG: 5,"1CCA","05D14079",7,,,"11100000","11100000" Network connectivity established and IP address assigned Looking up example.com Resolved 23.215.0.138 (AF_INET) Connecting to example.com:443 +CSCON: 0 +CSCON: 1 +CSCON: 0 +CSCON: 1 +CSCON: 0 +CSCON: 1 +CSCON: 0 +CSCON: 1 +CSCON: 0 +CSCON: 1 connect() failed, err: 111 +CSCON: 0 +CSCON: 1 +CEREG: 0 +CGEV: ME DETACH +CSCON: 0 Network connectivity lost Disconnected from the network
I'm using NCS 2.7.0 and modem 2.0.2. The same code running on nrf9160 devices works fine.
Might it be caused by AEA revision limitations?
