HTTPS Get request with nrf9160. TSL problems.

RE: HTTPS Get request with nrf9160. TSL problems.

Didrik Rokhaug — Mon, 21 Mar 2022 14:01:15 GMT

Unfortunately, this trace is not valid.

All the bytes in the trace are 0.

You can get the modem fw version wither via AT commands (e.g. AT%SHORTSWVER) or from the modem_info library (which also uses AT commands internally).

RE: HTTPS Get request with nrf9160. TSL problems.

Sindre Nordtveit — Mon, 21 Mar 2022 13:22:36 GMT

I've tried updating the firmware, is there any way I can confirm this myself?

Here is the new RAW file.

devzone.nordicsemi.com/.../trace_2D00_2022_2D00_03_2D00_21T12_2D00_50_2D00_55.042Z.bin

RE: HTTPS Get request with nrf9160. TSL problems.

Didrik Rokhaug — Mon, 21 Mar 2022 12:18:06 GMT

[quote user="s_nord"]Edit: I get something in this RAW file, maybe it contains something of relevance.[/quote]

Looking at the trace file, it looks like you are using modem FW v1.2.0, which is not supported by the trace collector v2.

I would highly recommend you update the modem FW to either 1.2.7 (if you have a rev 1 SiP, marked B0) or 1.3.1 (if you have a rev 2 SiP, marked B1).

Note that trace collector v2 also doesn't have a trace DB for mfw v1.2.7 yet, but it is included in the modem FW .zip file, so you should be able to decode those by selecting the trace DB manually.

The old modem FW also gives me a theory about why you are not able to connect: The Server Name Indication TLS extension was not supported until mfw v1.2.1. If your server requires SNI support to connect (e.g. if multiple servers are hosted on the same IP address), the old modem FW and lack of SNI support will be the reason for your failed connection attempts.

RE: HTTPS Get request with nrf9160. TSL problems.

Sindre Nordtveit — Mon, 21 Mar 2022 09:43:35 GMT

Thanks for the advice Didrik.

Yes, the certificate is written to the modem, and it seems to accept it. The application still fails when calling the connect function and returns the 111 error.

I tried enabling the Trace Collector, but Im not getting any packets out. I've followed the steps in the guide very closely, yet something has gone wrong. The CONFIG_NRF_MODEM_LIB_TRACE_ENABLED is set to "y" in my config file, and its also present in the build files.

I tried tracing with the working example file, but no packets are collected. Any advice on what the cause could be, or again, how to debug it? I'm getting a response from the server and the application is connecting and working.

I don't know if this is relevant, but if I do not select a trace database manually, the auto-detect does not stop. It seems to be loading forever. It suggest restarting the device, which I tried without any luck. Could this be a part of the issue?

Best regards,

Sindre

Edit: I get something in this RAW file, maybe it contains something of relevance.

devzone.nordicsemi.com/.../trace_2D00_2022_2D00_03_2D00_21T09_2D00_50_2D00_21.847Z.bin

RE: HTTPS Get request with nrf9160. TSL problems.

Didrik Rokhaug — Thu, 17 Mar 2022 13:14:07 GMT

Hi,

[quote user=""]Could someone please give me some direction in how to debug this?[/quote]

In addition to logs (e.g. does the application write the certificates to the modem?), one of the most useful tool is to look at the traffic between the device and the server.

You can do that by enabling modem tracing, and use the Trace Collector V2 Preview application in nRF Connect for Desktop to either store the trace in a Wireshark file, or display it live in Wireshark.

For more information on how to take a modem trace, see: https://infocenter.nordicsemi.com/topic/ug_trace_collector/UG/trace_collector/intro.html

The documentation is for Trace Collector v1, which doesn't let you see any of the data in the trace, but the v2 should be quite self explanatory. The most important details are how to get the trace off the device.

Best regards,

Didrik