feather nrf9151 and HTTPS example

marjonz · 2025-12-05T08:06:04+00:00

I’ve followed the instructions in https://docs.circuitdojo.com/nrf9151-feather/using-vscode.html and need to build the “https” example. When generating the b...

marjonz

jaredwolff Yes, I have a shell doing a tail on the caddy logs, when it fails, there is nothing, when it succeeds, I do get an entry with the proper timestamp. I will try and increase the timeout, start at doubling it and see how reliable that gets to.

marjonz

jaredwolff
1) Yes, I am using a dynamic IP, but that rarely changes even with the router reboots. My URL is setup to update if and when the router reboots (daily at 3am). And I don’t really test until about 9am or so. I think that should have given enough time (if the IP did change) for the DNS entries to have been updated.
And as you mentioned, the Certificate matches entry, so it looks to have been happy.
2) Router (also has a firewall) -> port forward to a local machine running linux -> machine running caddy and node.js server. And Let’s Encrypt for the DNS.
3) If the timeout change does not improve things, I will comment out the verify line to test. I will post results here (for the next person that encounters these issues).

jaredwolff

Sounds good! Good luck.

marjonz

jaredwolff Do you know if there is an API to make sure the modem has received a valid (public) IP address prior to doing the publish? I’m concerned that there is race condition before being assigned an IP and attempting to publish (without a valid IP yet).

marjonz

jaredwolff I did a test, the original https example, just some minor additional prints (when the socketopts are successful), and changed the timer in the main.c from 1440 to every 1 minute wakeup. I also moved as close (as safe) to the cell tower that the SIM was connecting to, I was within 80m line of sight of the tower.

I get the weird logs as below:

[00:00:15.579,132] <inf> cloud: Publish path: <my url>/api/device/da                                      ta
[00:00:15.579,315] <inf> cloud: Payload: {"do_something":true}
[00:00:15.579,345] <inf> cloud: Looking up <my url>
[00:00:16.121,734] <inf> cloud: getaddrinfo() successful.
[00:00:16.122,100] <inf> cloud: Socket created.
[00:00:16.122,131] <inf> cloud: Socket options set.
[00:00:16.122,161] <inf> cloud: Socket TX successful.
[00:00:16.122,436] <inf> cloud: TLS setup complete.
[00:00:20.588,500] <inf> cloud: Connected!
[00:00:20.588,500] <inf> cloud: Free addr info
[00:00:20.588,562] <inf> cloud: Socket setup complete
[00:00:21.955,871] <inf> cloud: HTTP Status 200
[00:00:21.956,024] <inf> cloud: HTTP Status 200
[00:00:21.956,085] <inf> cloud: Response data
                                22 73 74 61 74 75 73 22  3a 22 73 75 63 63 65 73 |"status" :"succes
                                73 22 2c 22 74 69 6d 65  73 74 61 6d 70 22 3a 22 |s","time stamp":"
                                32 30 32 35 2d 31 32 2d  31 33 54 30 36 3a 32 38 |2025-12- 13T06:28
                                3a 32 35 2e 34 31 32 5a  22 7d 65 6e 67 74 68 3a |:25.412Z "}ength:
                                20 35 39 0d 0a 43 6f 6e  74 65 6e 74 2d 54 79 70 | 59..Con tent-Typ
                                65 3a 20 61 70 70 6c 69  63 61 74 69 6f 6e 2f 6a |e: appli cation/j
                                73 6f 6e 3b 20 63 68 61  72 73 65 74 3d 75 74 66 |son; cha rset=utf
                                2d 38 0d 0a 44 61 74 65  3a 20 53 61 74 2c 20 31 |-8..Date : Sat, 1
                                33 20 44 65 63 20 32 30  32 35 20 30 36 3a 32 38 |3 Dec 20 25 06:28
                                3a 32 35 20 47 4d 54 0d  0a 45 74 61 67 3a 20 57 |:25 GMT. .Etag: W
                                2f 22 33 62 2d 67 30 65  30 45 2b 50 6c 68 4b 4d |/"3b-g0e 0E+PlhKM
                                4a 77 4c 74 53 62 61 6b  39 52 55 57 31 67 36 49 |JwLtSbak 9RUW1g6I
                                22 0d 0a 56 69 61 3a 20  31 2e 31 20 43 61 64 64 |"..Via:  1.1 Cadd
                                79 0d 0a 58 2d 50 6f 77  65 72 65 64 2d 42 79 3a |y..X-Pow ered-By:
                                20 45 78 70 72 65 73 73  0d 0a 43 6f 6e 6e 65 63 | Express ..Connec
                                74 69 6f 6e 3a 20 63 6c  6f 73 65 0d 0a 0d 0a 7b |tion: cl ose....{
[00:00:21.956,085] <inf> main: Cloud callback
[00:00:21.958,190] <inf> cloud: Data sent to cloud
[00:01:15.559,020] <inf> main: Timeout
[00:01:15.559,112] <inf> cloud: Publish path: <my url>/api/device/data
[00:01:15.559,234] <inf> cloud: Payload: {"do_something":true}
[00:01:15.559,295] <inf> cloud: Looking up <my url>
[00:01:15.568,389] <inf> cloud: getaddrinfo() successful.
[00:01:15.568,664] <inf> cloud: Socket created.
[00:01:15.568,664] <inf> cloud: Socket options set.
[00:01:15.568,695] <inf> cloud: Socket TX successful.
[00:01:15.575,408] <inf> cloud: TLS setup complete.
[00:01:18.785,278] <inf> cloud: Connected!
[00:01:18.785,308] <inf> cloud: Free addr info
[00:01:18.785,339] <inf> cloud: Socket setup complete
[00:01:21.784,942] <err> cloud: Unable to send data to cloud. Err: -116
[00:01:21.787,078] <inf> cloud: Data sent to cloud
[00:02:15.559,051] <inf> main: Timeout
[00:02:15.559,143] <inf> cloud: Publish path: <my url>/api/device/data
[00:02:15.559,265] <inf> cloud: Payload: {"do_something":true}
[00:02:15.559,326] <inf> cloud: Looking up <my url>
[00:02:15.560,943] <inf> cloud: getaddrinfo() successful.
[00:02:15.561,218] <inf> cloud: Socket created.
[00:02:15.561,218] <inf> cloud: Socket options set.
[00:02:15.561,248] <inf> cloud: Socket TX successful.
[00:02:15.567,962] <inf> cloud: TLS setup complete.
[00:02:20.567,871] <err> cloud: Unable to connect. Err: -116 - Connection timed out
[00:02:20.567,901] <inf> cloud: Free addr info
[00:02:20.569,274] <err> cloud: Unable to setup socket. Err: -116
[00:02:20.569,305] <err> main: Unable to publish. Err: -116
[00:03:15.559,020] <inf> main: Timeout
[00:03:15.559,112] <inf> cloud: Publish path: <my url>/api/device/data
[00:03:15.559,234] <inf> cloud: Payload: {"do_something":true}
[00:03:15.559,295] <inf> cloud: Looking up <my url>
[00:03:15.568,359] <inf> cloud: getaddrinfo() successful.
[00:03:15.568,634] <inf> cloud: Socket created.
[00:03:15.568,634] <inf> cloud: Socket options set.
[00:03:15.568,664] <inf> cloud: Socket TX successful.
[00:03:15.575,378] <inf> cloud: TLS setup complete.
[00:03:17.258,239] <inf> cloud: Connected!
[00:03:17.258,270] <inf> cloud: Free addr info
[00:03:17.258,300] <inf> cloud: Socket setup complete
[00:03:19.094,543] <inf> cloud: HTTP Status 200
[00:03:19.094,696] <inf> cloud: HTTP Status 200
[00:03:19.094,726] <inf> cloud: Response data
                                22 73 74 61 74 75 73 22  3a 22 73 75 63 63 65 73 |"status" :"succes
                                73 22 2c 22 74 69 6d 65  73 74 61 6d 70 22 3a 22 |s","time stamp":"
                                32 30 32 35 2d 31 32 2d  31 33 54 30 36 3a 33 31 |2025-12- 13T06:31
                                3a 32 32 2e 31 31 30 5a  22 7d 65 6e 67 74 68 3a |:22.110Z "}ength:
                                20 35 39 0d 0a 43 6f 6e  74 65 6e 74 2d 54 79 70 | 59..Con tent-Typ
                                65 3a 20 61 70 70 6c 69  63 61 74 69 6f 6e 2f 6a |e: appli cation/j
                                73 6f 6e 3b 20 63 68 61  72 73 65 74 3d 75 74 66 |son; cha rset=utf
                                2d 38 0d 0a 44 61 74 65  3a 20 53 61 74 2c 20 31 |-8..Date : Sat, 1
                                33 20 44 65 63 20 32 30  32 35 20 30 36 3a 33 31 |3 Dec 20 25 06:31
                                3a 32 32 20 47 4d 54 0d  0a 45 74 61 67 3a 20 57 |:22 GMT. .Etag: W
                                2f 22 33 62 2d 73 35 33  6d 71 2f 62 65 51 4b 6f |/"3b-s53 mq/beQKo
                                2b 43 4b 6f 79 62 35 4d  44 63 49 2b 53 41 30 6f |+CKoyb5M DcI+SA0o
                                22 0d 0a 56 69 61 3a 20  31 2e 31 20 43 61 64 64 |"..Via:  1.1 Cadd
                                79 0d 0a 58 2d 50 6f 77  65 72 65 64 2d 42 79 3a |y..X-Pow ered-By:
                                20 45 78 70 72 65 73 73  0d 0a 43 6f 6e 6e 65 63 | Express ..Connec
                                74 69 6f 6e 3a 20 63 6c  6f 73 65 0d 0a 0d 0a 7b |tion: cl ose....{
[00:03:19.094,757] <inf> main: Cloud callback
[00:03:19.096,679] <inf> cloud: Data sent to cloud
[00:04:15.559,020] <inf> main: Timeout
[00:04:15.559,112] <inf> cloud: Publish path: <my url>/api/device/data
[00:04:15.559,234] <inf> cloud: Payload: {"do_something":true}
[00:04:15.559,295] <inf> cloud: Looking up <my url>
[00:04:17.972,778] <inf> cloud: getaddrinfo() successful.
[00:04:17.973,388] <inf> cloud: Socket created.
[00:04:17.973,419] <inf> cloud: Socket options set.
[00:04:17.973,419] <inf> cloud: Socket TX successful.
[00:04:17.973,724] <inf> cloud: TLS setup complete.
[00:04:22.973,693] <err> cloud: Unable to connect. Err: -116 - Connection timed out
[00:04:22.973,724] <inf> cloud: Free addr info
[00:04:22.975,067] <err> cloud: Unable to setup socket. Err: -116
[00:04:22.975,097] <err> main: Unable to publish. Err: -116
[00:05:15.559,020] <inf> main: Timeout
[00:05:15.559,112] <inf> cloud: Publish path: <my url>/api/device/data
[00:05:15.559,234] <inf> cloud: Payload: {"do_something":true}
[00:05:15.559,295] <inf> cloud: Looking up <my url>
[00:05:15.568,359] <inf> cloud: getaddrinfo() successful.
[00:05:15.568,634] <inf> cloud: Socket created.
[00:05:15.568,664] <inf> cloud: Socket options set.
[00:05:15.568,664] <inf> cloud: Socket TX successful.
[00:05:15.575,378] <inf> cloud: TLS setup complete.
[00:05:19.433,258] <inf> cloud: Connected!
[00:05:19.433,288] <inf> cloud: Free addr info
[00:05:19.433,319] <inf> cloud: Socket setup complete
[00:05:20.837,127] <inf> cloud: HTTP Status 200
[00:05:20.837,280] <inf> cloud: HTTP Status 200
[00:05:20.837,310] <inf> cloud: Response data
                                22 73 74 61 74 75 73 22  3a 22 73 75 63 63 65 73 |"status" :"succes
                                73 22 2c 22 74 69 6d 65  73 74 61 6d 70 22 3a 22 |s","time stamp":"
                                32 30 32 35 2d 31 32 2d  31 33 54 30 36 3a 33 33 |2025-12- 13T06:33
                                3a 32 34 2e 32 37 36 5a  22 7d 65 6e 67 74 68 3a |:24.276Z "}ength:
                                20 35 39 0d 0a 43 6f 6e  74 65 6e 74 2d 54 79 70 | 59..Con tent-Typ
                                65 3a 20 61 70 70 6c 69  63 61 74 69 6f 6e 2f 6a |e: appli cation/j
                                73 6f 6e 3b 20 63 68 61  72 73 65 74 3d 75 74 66 |son; cha rset=utf
                                2d 38 0d 0a 44 61 74 65  3a 20 53 61 74 2c 20 31 |-8..Date : Sat, 1
                                33 20 44 65 63 20 32 30  32 35 20 30 36 3a 33 33 |3 Dec 20 25 06:33
                                3a 32 34 20 47 4d 54 0d  0a 45 74 61 67 3a 20 57 |:24 GMT. .Etag: W
                                2f 22 33 62 2d 6a 37 69  4d 52 4c 30 66 6b 67 6d |/"3b-j7i MRL0fkgm
                                70 71 2b 4f 42 50 50 52  6a 4b 59 7a 53 4e 30 41 |pq+OBPPR jKYzSN0A
                                22 0d 0a 56 69 61 3a 20  31 2e 31 20 43 61 64 64 |"..Via:  1.1 Cadd
                                79 0d 0a 58 2d 50 6f 77  65 72 65 64 2d 42 79 3a |y..X-Pow ered-By:
                                20 45 78 70 72 65 73 73  0d 0a 43 6f 6e 6e 65 63 | Express ..Connec
                                74 69 6f 6e 3a 20 63 6c  6f 73 65 0d 0a 0d 0a 7b |tion: cl ose....{
[00:05:20.837,341] <inf> main: Cloud callback
[00:05:20.839,416] <inf> cloud: Data sent to cloud
[00:06:15.559,051] <inf> main: Timeout
[00:06:15.559,143] <inf> cloud: Publish path: <my url>/api/device/data
[00:06:15.559,265] <inf> cloud: Payload: {"do_something":true}
[00:06:15.559,326] <inf> cloud: Looking up <my url>
[00:06:15.568,389] <inf> cloud: getaddrinfo() successful.
[00:06:15.568,664] <inf> cloud: Socket created.
[00:06:15.568,695] <inf> cloud: Socket options set.
[00:06:15.568,695] <inf> cloud: Socket TX successful.
[00:06:15.575,408] <inf> cloud: TLS setup complete.
[00:06:20.575,286] <err> cloud: Unable to connect. Err: -116 - Connection timed out
[00:06:20.575,317] <inf> cloud: Free addr info
[00:06:20.584,320] <err> cloud: Unable to setup socket. Err: -116
[00:06:20.584,320] <err> main: Unable to publish. Err: -116
[00:07:15.559,020] <inf> main: Timeout
[00:07:15.559,112] <inf> cloud: Publish path: <my url>/api/device/data
[00:07:15.559,234] <inf> cloud: Payload: {"do_something":true}
[00:07:15.559,295] <inf> cloud: Looking up <my url>
[00:07:15.568,359] <inf> cloud: getaddrinfo() successful.
[00:07:15.568,634] <inf> cloud: Socket created.
[00:07:15.568,664] <inf> cloud: Socket options set.
[00:07:15.568,664] <inf> cloud: Socket TX successful.
[00:07:15.575,042] <inf> cloud: TLS setup complete.
[00:07:17.926,269] <inf> cloud: Connected!
[00:07:17.926,300] <inf> cloud: Free addr info
[00:07:17.926,330] <inf> cloud: Socket setup complete
[00:07:20.926,483] <err> cloud: Unable to send data to cloud. Err: -116
[00:07:20.936,950] <inf> cloud: Data sent to cloud
[00:08:15.559,051] <inf> main: Timeout
[00:08:15.559,143] <inf> cloud: Publish path: <my url>/api/device/data
[00:08:15.559,265] <inf> cloud: Payload: {"do_something":true}
[00:08:15.559,326] <inf> cloud: Looking up <my url>
[00:08:15.568,389] <inf> cloud: getaddrinfo() successful.
[00:08:15.568,664] <inf> cloud: Socket created.
[00:08:15.568,695] <inf> cloud: Socket options set.
[00:08:15.568,725] <inf> cloud: Socket TX successful.
[00:08:15.575,073] <inf> cloud: TLS setup complete.
[00:08:20.575,317] <err> cloud: Unable to connect. Err: -116 - Connection timed out
[00:08:20.575,347] <inf> cloud: Free addr info
[00:08:20.575,805] <err> cloud: Unable to setup socket. Err: -116
[00:08:20.575,805] <err> main: Unable to publish. Err: -116
[00:09:15.559,051] <inf> main: Timeout
[00:09:15.559,143] <inf> cloud: Publish path: <my url>/api/device/data
[00:09:15.559,265] <inf> cloud: Payload: {"do_something":true}
[00:09:15.559,326] <inf> cloud: Looking up <my url>
[00:09:16.792,266] <inf> cloud: getaddrinfo() successful.
[00:09:16.792,877] <inf> cloud: Socket created.
[00:09:16.792,907] <inf> cloud: Socket options set.
[00:09:16.792,907] <inf> cloud: Socket TX successful.
[00:09:16.793,182] <inf> cloud: TLS setup complete.
[00:09:18.152,343] <inf> cloud: Connected!
[00:09:18.152,374] <inf> cloud: Free addr info
[00:09:18.152,404] <inf> cloud: Socket setup complete
[00:09:21.151,855] <err> cloud: Unable to send data to cloud. Err: -116
[00:09:21.162,292] <inf> cloud: Data sent to cloud
[00:10:15.559,051] <inf> main: Timeout
[00:10:15.559,143] <inf> cloud: Publish path: <my url>/api/device/data
[00:10:15.559,265] <inf> cloud: Payload: {"do_something":true}
[00:10:15.559,326] <inf> cloud: Looking up <my url>
[00:10:15.568,389] <inf> cloud: getaddrinfo() successful.
[00:10:15.568,664] <inf> cloud: Socket created.
[00:10:15.568,695] <inf> cloud: Socket options set.
[00:10:15.568,725] <inf> cloud: Socket TX successful.
[00:10:15.575,073] <inf> cloud: TLS setup complete.
[00:10:19.129,241] <inf> cloud: Connected!
[00:10:19.129,272] <inf> cloud: Free addr info
[00:10:19.129,302] <inf> cloud: Socket setup complete
[00:10:20.587,158] <inf> cloud: HTTP Status 200
[00:10:20.587,249] <err> cloud: Unable to send data to cloud. Err: -104
[00:10:20.589,202] <inf> cloud: Data sent to cloud

1) I got three successful transmits.
2) It will sometimes succeed in the “connect()” call but fail in the transmission of the data.
3) The last log entry shows “HTTP Status 200” but still failed to transmit the data.

So my main problem now is reliability, are there any APIs in the lte and modem library used in the example that can help me verify the state/status of the connection so that I can realiably say that I have sent the data (and hopefully get a response back to confirm?

marjonz

Increasing timeout seemed to be worse
The connection dropped pretty quickly

AchimKraus

marjonz Do you know if there is an API to make sure the modem has received a valid (public) IP address

Even DNS is using the device IP address. So, if DNS works, your device has an address.
Depending on the network setup of your provider, that ip address maybe assigned to a temporary public ip address by a NAT. That’s “transparent” and doesn’t need to be handled on the device side other, that obeying a potential timeout of that NAT, if no traffic is transferred.

I use a AT cmd to get the local ip-address (“AT+CGDCONT?”) and the “modem_info” module has also a function for that (MODEM_INFO_IP_ADDRESS).

marjonz

I’ve got a weird behavior after adding retries. For this code:

static bool connection_successful = false;
static int connect_to_remote_server(int fd, struct addrinfo *res)
{
    /* Connect */
    int err = connect(fd, res->ai_addr, sizeof(struct sockaddr_in));
    if (err < 0)
    {
        err = -errno;
        LOG_ERR("Unable to connect. Err: %i - %s", err, strerror(errno));
    }
    else
    {
        LOG_INF("Connected!");
    }
    return err;
}
...
    while(!connection_successful)
    {
        err = connect_to_remote_server(fd, res);
        if (err == 0)
        {
            connection_successful = true;
        }
        else
        {
            LOG_INF("Re-attempting connection in 5 seconds...");
            k_sleep(K_SECONDS(5));
        }
    }

I am getting:

[00:00:16.762,847] <inf> main: LTE network status: 0
[00:00:16.762,908] <inf> cloud: Publish path: <my url>/api/device/da                                            ta
[00:00:16.763,061] <inf> cloud: Payload: {"do_something":true}
[00:00:16.763,092] <inf> cloud: Looking up <my url>
[00:00:18.205,810] <inf> cloud: getaddrinfo() successful.
[00:00:18.206,207] <inf> cloud: Socket created.
[00:00:18.206,237] <inf> cloud: Socket options set.
[00:00:18.206,237] <inf> cloud: Socket TX successful.
[00:00:18.206,512] <inf> cloud: TLS setup complete.
[00:00:23.206,909] <err> cloud: Unable to connect. Err: -116 - Connection timed out
[00:00:23.206,970] <inf> cloud: Re-attempting connection in 5 seconds...
[00:00:28.207,122] <err> cloud: Unable to connect. Err: -127 - Socket is already connected
[00:00:28.207,153] <inf> cloud: Re-attempting connection in 5 seconds...
[00:00:33.207,305] <err> cloud: Unable to connect. Err: -127 - Socket is already connected
[00:00:33.207,336] <inf> cloud: Re-attempting connection in 5 seconds...
[00:00:38.207,489] <err> cloud: Unable to connect. Err: -127 - Socket is already connected
[00:00:38.207,519] <inf> cloud: Re-attempting connection in 5 seconds...
[00:00:43.207,672] <err> cloud: Unable to connect. Err: -127 - Socket is already connected
[00:00:43.207,702] <inf> cloud: Re-attempting connection in 5 seconds...

Instead of calling the connect() function once and failing. The second attempt complains that the socket is already “connected”??? Looks like something in the lower layers needs to be checked prior to calling the connect() function. Otherwise, it’s a roll of the dice if it succeeds or not.

AchimKraus

Maybe, before you focus too much on the wrong end, did you check, if your device is able to connect to an other https/tls endpoint? e.g. “https://www.example.com/” using “nrf/samples/net/https_client” (not sure if that still works, it’s years ago that I’ve been testing that).

And still my recommendation: try to get some numbers about the RSRP/RSRQ.

Though my “kick-off” was some years ago, I tend to use at-cmds.
So for that I use “AT+CEINFO?”. Works only, if the device is in “RRC active” (not “idle” nor “sleeping”). That provides also the “repitition factors” (1 to 128, large number indicate a extra long RTT) and the RSRP. The CINR will then provide something about the “quality”, as RSRQ or SNR will also do but the number slightly differ.
An other good command maybe “lte_lc_neighbor_cell_measurement” to get a list of network and signal strength. That works only in “sleep” :-) and you will need to “dump” the result.

marjonz

AchimKraus Thank you for the suggestions. I have been trying to build the https_client since the other day to try with an nrfthingy 9151 board that I have, But I keep running into the error:
C:\ncs\toolchains\0b393f9e1b\opt\bin\cmake.exe -E true"" c:/ncs/toolchains/0b393f9e1b/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr/drivers/flash/libdrivers__flash.a(spi_nor.c.obj):(. rodata.spi_nor_0_config+0x0): undefined reference to__device_dts_ord_130′`

This was the build config I had, which I am assuming should be correct, but please, point out my mistake:

For the RSRP/RSRQ, I found the modules that had those APIs available, was not part of the config, and even the ones with the AT commands, I have to try and enable/add them in the prj.conf to even access the APIs.

I am sorry that I’m a beginner with nRF and zephyr, tbh, I’ve had a total of about 7 days experience with it to the day. I am glad there are people like you and Jared, who invest time in support others, and that’s why I would like to also share this journey for the next person that might come into this thread and have the same issues.

AchimKraus

The idea to use the other server was more to exclude some server issues. If that causes then other issues, it may be the wrong path.

Anyway:
On NCS 3.1.0, the http_client doesn’t support the Thingy:91X out of the box. I copied the nrf9151dk_nrf9151_ns.conf into thingy91x_nrf9151_ns.conf and also renamed the sysbuild folder into sysbuildx to disable the specific mcuboot setup, which wasn’t working in my case. The I build from the command line with

west build -b thingy91x/nrf9151/ns -p
west flash

I also added a loop and a 30s sleep around the send_http_request()

That result:

*** Booting nRF Connect SDK v3.1.0-n-b92157217c9c ***
*** Using Zephyr OS v4.1.99-ecccacad8c3a ***
HTTPS client sample started

Bringing network interface up
[00:00:00.547,668] <inf> lte_lc: XSYSTEMMODE=1,1,1,3
Provisioning certificate
Certificate match
Connecting to the network
+CGEV: EXCE STATUS 0

+CEREG: 2,"67B9","01CC2B00",7

%MDMEV: PRACH CE-LEVEL 0

+CSCON: 1

+CGEV: ME PDN ACT 0,0

+CNEC_ESM: 50,0

%MDMEV: SEARCH STATUS 2

+CEREG: 5,"67B9","01CC2B00",7,,,"00000000","00111000"

Network connectivity established and IP address assigned
Looking up example.com
Resolved 23.215.0.136 (AF_INET)
Connecting to example.com:443
Sent 61 bytes
Received 266 bytes

>	 HTTP/1.1 200 OK


Finished, closing socket.
+CSCON: 0

Looking up example.com
Resolved 23.215.0.136 (AF_INET)
Connecting to example.com:443
%MDMEV: SEARCH STATUS 2

%MDMEV: PRACH CE-LEVEL 0

+CSCON: 1

Sent 61 bytes
Received 266 bytes

>	 HTTP/1.1 200 OK


Finished, closing socket.
+CSCON: 0

Looking up example.com
Resolved 23.215.0.136 (AF_INET)
Connecting to example.com:443
%MDMEV: SEARCH STATUS 2

%MDMEV: PRACH CE-LEVEL 0

+CSCON: 1

Sent 61 bytes
Received 266 bytes

>	 HTTP/1.1 200 OK


Finished, closing socket.
+CSCON: 0

My current radio level at my location:
CE: down: 8, up: 1, RSRP: -111 dBm, CINR: 3 dB

marjonz

AchimKraus Thank you very much for giving this a try, which SDK and toolchain did you use to create/use the https_client example please? I have tried that, and found that as you mentioned, it does not work out of the box. I’m running out of options on how to get a “stable” https connection working.

I’ve added a call to k_sleep(K_MSEC(5)) before the call to connect() and that worked 2 out of 5 tries, had a successful connection. I was only pressing the reset button on the feather board, and looking at the serial debug output. But 40% success is still pretty bad in my opinion (sample size of 5 only too).

AchimKraus

marjonz which SDK and toolchain did you use

AchimKraus NCS 3.1.0

I use the Nordic Connect SDK 3.1.0.

AchimKraus

Anyway, the idea using an other https endpoint was based on that this would be easier to do. If you stuck with it, just try to get some more insights with your client. There are also some nice tools as the “Cellular Monitor”, but I’m afraid that this would also require to get some support.

marjonz

AchimKraus I followed the circuit dojo’s instruction page. I also tried manually updating the “submodule” for nrf to the 3.1.0, I think it wouldn’t build the configuration.

AchimKraus

On the picture your antenna cable seems show a 90° corner, is that just optical or real? if it’s real, AFAIK, don’t do that.

marjonz

AchimKraus it’s slightly bent, not 90 degrees. I was just trying to point the antenna and the board was resting on the white table

AchimKraus

I’ve spend some time into testing with a new nRF9151 feather and nfed v3.1.x (commit e8ea8be61212879c1f04b30).

I modified the samples/https to use GET requests against “example.com”. I use 1 minute send interval.
On “my feather” that runs now for a couple of minutes with all successful requests. Maybe you try that as well?

sources:
https://community.circuitdojo.com/assets/files/2025-12-14/1765700345-794095-https.zip

prebuild hex:
https://community.circuitdojo.com/assets/files/2025-12-14/1765700560-268059-merged.txt

It’s now 15 minutes up and all 15 https requests have been successful.

To flash the prebuild hex:

probe-rs download --chip nRF9151_xxAA --binary-format hex build/merged.hex
probe-rs reset --chip nRF9151_xxAA

marjonz

Thank you. I will do that today. This will eliminate the problem if it is my server ( which I doubt) is the issue. I understand it is just GET, but if the problem was the POST, I’ll need to figure out why. Thank you very much for the help

AchimKraus

You’re welcome.

marjonz

AchimKraus A quick test on my bench, yielded horrible results, nothing connected. I will go drive again to the place where i’m within 100m of the cell tower it was connecting to. Thank you again. I will report back results later.

« Previous Page Next Page »