Problems with setting up https client

[veli-pekka]

Hello,

We have started to develop a new sw using nRF9160. We have pretty bad problems with setting up http(s) connection. In the end I needed up trying with https client sample application. On dev board it somewhat works (name resolution fails, but at least it runs until it. This is not a problem atm). Then I removed I2C and SPI, button and led controls shouldn't do any harm, and flashed the sw to our custom board. Now the sw fails in lte_lc.c with

[00:00:00.374,664] <inf> modem: Bringing network interface up

[00:00:00.603,149] <err> lte_lc: nrf_modem_at_printf failed, reported error: 65536

Any idea what might cause this? This is our first project with nRF9160, so there might be something trivial we just are not aware of.

Our toolchain and SDK version are 2.5.2

[veli-pekka]

The problem seems to be AT command AT+CPSMS=  which returns an error. Otherwise AT commands seem to be working, for example AT+CGMR returns "mfw-pti_nrf9160_1.1.6"

[veli-pekka]

btw. the dev board seems to have revision "mfw_nrf9160_1.3.5". Could this be the reason?

[veli-pekka]

This in fact was the reason. For some reason we got modules with very old modem fw version.

[Naeem Maroof]

Hi veli-pekka 

Did you update to the latest MFW? Do you still have issues as previously? what is current status of your project?

Also, are there any issues on the dev-kit running the project?

[veli-pekka]

Yes, we are now using version 1.3.6. Next problem seems to be that the connection to example.com fails:

[00:00:00.624,176] <inf> modem: Provisioning certificate

[00:00:00.624,206] <inf> modem: Connecting to the network

[00:00:04.496,520] <inf> modem: Network connectivity established and IP address assigned

[00:00:04.496,582] <inf> modem: Looking up example.com

[00:00:04.615,234] <inf> modem: Resolved 93.184.215.14 (AF_INET)

[00:00:04.615,600] <inf> modem: Connecting to example.com:443

[00:00:04.871,520] <inf> modem: connect() failed, err: 111

What should I check next? Example.com sertificate seems to have changed in the end of January and I updated it, but it didn't help.

[Naeem Maroof]

Hi,

The error 111 means the connection is refused.

Searching for connection refused, the common issue can be when the SSL certificates are invalid or incorrectly configured.

So the suggestion would be to check the certificates; otherwise get a modem trace.

You may also look at these tickets as they talk about same/similar issues:

CONNECT Client 111 Error

Connect Error 45 Certificates