This bug is completely unexplainable to me…. Could one of you please try to repro it? I think the process would be change those two lines in kconfig to point the example at my server and see if you get the same error. If you get the same behavior, then I think that would mean there is something wrong with the DNS or certs on my server. Maybe? Otherwise, I don’t know what else to do. Maybe it’s a hardware issue?
One other clue is that if I run ngrock and point the nrf9160 to my local server (through the ngrock service) I get a slightly different error (I’ve turned on modem debug output):
Connecting..
Connected to /dev/cu.usbserial-110!
*** Booting Zephyr OS build v3.3.99-ncs1-2 ***
[00:00:00.252,838] <inf> main: HTTPS Sample. Board: circuitdojo_feather_nrf9160
[00:00:00.544,677] <inf> cloud: Certificate match
[00:00:00.554,107] <inf> main: lte init
[00:00:00.554,565] <inf> main: power saving on
+CEREG: 2,"8B3A","0A128E0F",7
+CSCON: 1
+CEREG: 5,"8B3A","0A128E0F",7,,,"00001000","00100110"
%XTIME: "2B","4221324054712B","00"
[00:00:09.058,166] <inf> main: lte connected
[00:00:09.058,319] <inf> cloud: Publish path: 8b47-157-131-113-156.ngrok-free.app/api/test
[00:00:09.058,349] <inf> cloud: Payload: {"do_something": "true"}
[00:00:09.058,380] <inf> cloud: Looking up 8b47-157-131-113-156.ngrok-free.app
It then resets. So, this gets a bit further, but still has issues at the basic level of setting up the socket.
Thanks so much for your help!
