First HTTPS socket connect() success, subsequent connect always hangs

RE: First HTTPS socket connect() success, subsequent connect always hangs

psychogenic — Tue, 17 Mar 2020 15:30:04 GMT

Yes, that does the trick. Thank you much.

Can you point me to the place where know issues are listed?

RE: First HTTPS socket connect() success, subsequent connect always hangs

anicare-tero — Mon, 16 Mar 2020 13:30:55 GMT

[quote userid="81181" url="~/f/nordic-q-a/59108/first-https-socket-connect-success-subsequent-connect-always-hangs/239996"]Are you certain that you close your sockets properly? It sounds a bit like you are running out of sockets.[/quote]

Yep, that was the problem. I had earlier modified the code to open and close socket differently, but I changed the code back to how it is in https_client sample and not it works. Thanks a lot, Didrik!

RE: First HTTPS socket connect() success, subsequent connect always hangs

Didrik Rokhaug — Mon, 16 Mar 2020 12:36:22 GMT

Hi anicare-tero.

It does not sound like you have the same problem as the original post. That problem would occur every time on the second connection, with connect not returning instead of giving an error.

Are you certain that you close your sockets properly? It sounds a bit like you are running out of sockets.

If that does not help you either, I recommend you open a new ticket where you provide a modem trace.

Best regards,

Didrik

RE: First HTTPS socket connect() success, subsequent connect always hangs

anicare-tero — Mon, 16 Mar 2020 12:13:51 GMT

Hi Didrik,

[quote userid="81181" url="~/f/nordic-q-a/59108/first-https-socket-connect-success-subsequent-connect-always-hangs/239974"]As a workaround, you can either disable TLS session caching using socket options:[/quote]

That didn't help me. I'm still getting same errors. Could the problem be that I'm using setsockopt() for peer verification (that is also used in https_client sample) and your suggestion uses nrf_setsockopt()?

RE: First HTTPS socket connect() success, subsequent connect always hangs

Didrik Rokhaug — Mon, 16 Mar 2020 11:47:24 GMT

Hi.

Bsdlib v0.6.1 enabled TLS session caching by default. However, this triggers a bug in the modem when trying to re-connect to a server.

As a workaround, you can either disable TLS session caching using socket options:

nrf_sec_session_cache_t session_cache = 0;

nrf_setsockopt(socket, NRF_SOL_SECURE,

        NRF_SO_SEC_SESSION_CACHE, &session_cache,

        sizeof(session_cache));

Or, you can go back to the previous version of bsdlib (v0.6.0) by changing the revision checked out by west in the ncs/nrf/west.yml file on line 72 to 3e381d09f1d305e230435f5b6e4c9ef928b6a697, and running west update.

We are working on fixing the bug.

Best regards,

Didrik

RE: First HTTPS socket connect() success, subsequent connect always hangs

anicare-tero — Mon, 16 Mar 2020 08:41:55 GMT

I'm having this same problem, except I have this error message: "Error: connect() failed, errno: 12"

Usually, I'm getting 3-4 successful connections but then I will always have those connect errors.

I would really need help with this too.