HTTPS client connect fails with Error 45 with 1nce sim card in France

[Saketaram]

Hi,

I used 3HK sim card on NB-IoT in Hong Kong, and I could run GET and POST instructions to any cloud with the right certificate.

Recently, I moved to France, and I switched to 1nce MVNO and now the connection fails with error 45. The certificate hasn't changed.

We also tried to connect to google, using google certificate. That also fails. TLS socket setup with TLS_HOSTNAME option with host google.com didn't help either.

ncs 1.5.1
modem fw 1.2.3


Attached is the build files and the modem trace.

Could you help on this urgent matter, please?

Saketaram

https_client.7z

[Heidi]

Hi!

I apologize for the delayed response. The person that your case was originally assigned to left for vacation this week, so it has been assigned to me.

The trace you provided in your ticket is unfortunately empty. Please try to take one again, and make sure that the number indicating the size of the trace in the Trace Collector application is increasing as the application is running.

[Saketaram]

Hi Heidi,

Here is the new trace. Let us know your comments and advice.

trace-2021-08-04T19-22-43.580Z.bin

Saketaram

[Heidi]

Hi, thank you. The modem team will take a look at this trace.

In the mean time, I know other customers have had success using Orange France as the network provider with the nRF9160 DK. 

[Heidi]

Hi again,

The modem API traces are totally missing from the trace you provided.

Did you make sure to add CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y in your application? And that UART1 isn't being used by something else?

Additionally, have you verified with your network provider that the SIM card you are using should work in the area you are? And that there should be NB-IoT or LTE-M coverage in the area?

[Saketaram]

Hi Heidi,
We checked again:

. CONFIG_NRF_MODEM_LIB_TRACE+ENABLED=y is well positionned. You can also see that in the zipped file we provided initially.

. UART1 is not used at all

I attach a new trace file. Let me know if you see what the problem is with those 1nce sim cards or on anything else.

trace-2021-08-19T10-32-32.536Z.bin

[Heidi]

Thank you. We will take a look. 

Did you verify with your network provider that the SIM card should work in your area?

[Heidi]

From the log, we can see an attempt to establish a TLS session with no success. The server certificate is not as expected and the client stops the TLS handshake.

Can you could double check the certificates? It's currently using the root CA from sec_tag 42. Should this match the one the server is using?

[Saketaram]

Hi Heidi,

The certificate is the same from the https_client sample example provided. The sec tag was also changed to other values. It didn't change the behavior. Any number other than 42 didn't help.

We also manually deleted all the certificates from the modem including the nrf cloud certificate and allowed the fw to provision the certificate with the sec tag 42. Nothing better neither.

[Saketaram]

Hi Heidi,

Do you have any feedback on our logs? We are blocked in our product launch as this is the last piece of software that is preventing the full test of firmware. We already delayed by 1 month
We have been waiting for one month and see no progress on your support so far.

Which sim do you recommend, so we can sort out if it's related to the 1nce sim or to another software or parameter part.

Your help both on the log (where we use the sample with the latest modem firmware) and on the sim card is much appreciated.

Thanks