WebSocket/TLS Connection Stuck Issue

RE: WebSocket/TLS Connection Stuck Issue

Sigurd Hellesvik — Tue, 26 May 2026 11:48:02 GMT

Checking the files, the USAGE FAULT you posted in the top ticket is from setup_thread_stack, which matches with having allocated too little stack.

[quote user="DipeshParikh_"]My concern is whether this fix will resolve the issue completely ?[/quote]

We can not know exactly how much stack your application will require at build time.
I recommend that you use the Thread Viewer or Thread Analyzerto analyze how much stack your application needs at runtime, and then allocate stack accordingly (and a bit extra as a buffer).

RE: WebSocket/TLS Connection Stuck Issue

DipeshParikh_ — Mon, 25 May 2026 05:03:33 GMT

Hi, Here I'm Providing you to zephyr.elf & zephyr.map files.

devzone.nordicsemi.com/.../7282.zephyr.zip

[quote userid="106736" url="~/f/nordic-q-a/128090/websocket-tls-connection-stuck-issue/566790"]

Can you log the reason why the Wi-Fi lost the stop server?

[/quote]

We are getting the reset reason unspecified.

providing you the logs for reference.

[14:00:24.910,003] <inf> NK_Timer: HubStatus cycle start
00> [14:00:24.910,003] <inf> NK_Timer: Stopping WebSocket
00> [14:00:24.923,400] <inf> nk_ws: WS stopped
00> [14:00:24.923,431] <inf> NK_Timer: WS RX Timer periodic timer stopped
00> [14:00:24.923,431] <inf> NK_Timer: WS Ping periodic timer stopped
00> [14:00:24.923,461] <inf> NK_Timer: HubStatus: resolve server
00> [14:00:24.923,461] <inf> nk_net_conn: ========== DNS RESOLVE START ==========
00> [14:00:24.923,492] <inf> nk_net_conn: Host              : api.nexkey.com
00> [14:00:24.923,522] <inf> nk_net_conn: Port              : 443
00> [14:00:29.929,046] <err> wifi_nrf: nrf_wifi_wpa_supp_signal_poll: Failed to get station info, ret = -11[0m
00> [14:00:29.930,908] <err> wifi_mgr: ========== WIFI DISCONNECTED ==========
00> [14:00:29.930,908] <err> wifi_mgr: Disconnect Count   : 1
00> [14:00:29.930,908] <err> wifi_mgr: Disconnect status  : 0
00> [14:00:29.931,182] <inf> nk_net_conn: RSSI              : -9999
00> [14:00:29.931,213] <inf> nk_net_conn: System Uptime     : 50429 sec
00> [14:00:29.931,243] <inf> nk_net_conn: Thread            : �b
00> [14:00:29.931,243] <inf> nk_net_conn: =======================================
00> [14:00:29.931,243] <inf> nk_net_conn: [DNS] Attempt=1
00> [14:00:29.959,533] <err> wifi_mgr: RSSI Before Drop   : -46
00> [14:00:29.959,564] <err> wifi_mgr: IP Before Drop     : 192.168.201.11
00> [14:00:29.959,594] <err> wifi_mgr: SSID               : Nextkey
00> [14:00:29.959,625] <err> wifi_mgr: System Uptime      : 50429959
00> [14:00:29.959,625] <err> wifi_mgr: ======================================
00> [14:00:29.959,625] <err> wifi_mgr: Disconnect Reason : UNSPECIFIED
00> [14:00:29.959,686] <err> wifi_mgr: Iface State        : 4
00> [14:00:29.959,686] <err> wifi_mgr: Iface RSSI         : 0
00> [14:00:29.959,686] <err> wifi_mgr: Iface Channel      : 0
00> [14:00:29.959,686] <inf> nk_net_mgr: NET Manager stop
00> [14:00:29.959,716] <inf> nk_net_conn: Server disconnected
00> [14:00:29.959,716] <inf> nk_ws: WS stopped
00> [14:00:29.959,716] <inf> NK_Timer: WS RX Timer periodic timer stopped
00> [14:00:29.959,747] <inf> NK_Timer: WS Ping periodic timer stopped
00> [14:00:29.959,747] <inf> wifi_mgr: WiFi Disconnected
00> [14:00:29.959,747] <inf> NK_Timer: HubStatus periodic timer stopped
00> [14:00:30.053,833] <inf> NK_Timer: WiFi monitor timer stopped
00> [14:00:30.058,410] <inf> wifi_mgr: ========== WIFI CONNECTED ==========
00> [14:00:30.058,410] <inf> wifi_mgr: Connect Count      : 2
00> [14:00:30.058,410] <inf> wifi_mgr: Status             : 0
00> [14:00:30.058,441] <inf> wifi_mgr: SSID               : Nextkey
00> [14:00:30.058,441] <inf> wifi_mgr: RSSI               : -46
00> [14:00:30.058,471] <inf> wifi_mgr: MAC                : 00:18:07:01:59:4C
00> [14:00:30.058,502] <inf> wifi_mgr: ====================================
00> [14:00:32.033,813] <inf> nk_net_conn: [DNS] Duration=2102 ms
00> [14:00:32.033,813] <err> nk_net_conn: [DNS] FAILED
00> [14:00:32.033,843] <err> nk_net_conn: [DNS] getaddrinfo err=-3
00> [14:00:32.033,874] <err> nk_net_conn: [DNS] errno=0 (Success)
00> [14:00:32.037,872] <err> nk_net_conn: [DNS] RSSI=-47
00> [14:00:32.037,872] <err> nk_net_conn: [DNS] WiFi Connected=1
00> [14:00:32.037,872] <err> nk_net_conn: [DNS] Retry remaining=2
00> [14:00:34.037,963] <inf> nk_net_conn: [DNS] Attempt=2
00> [14:00:34.038,269] <inf> nk_net_conn: [DNS] Duration=1 ms
00> [14:00:34.038,299] <err> nk_net_conn: [DNS] FAILED
00> [14:00:34.038,299] <err> nk_net_conn: [DNS] getaddrinfo err=-11
00> [14:00:34.038,330] <err> nk_net_conn: [DNS] errno=2 (No such file or directory)
00> [14:00:34.042,327] <err> nk_net_conn: [DNS] RSSI=-51
00> [14:00:34.042,327] <err> nk_net_conn: [DNS] WiFi Connected=1
00> [14:00:34.042,358] <err> nk_net_conn: [DNS] Retry remaining=1
00> [14:00:36.042,419] <inf> nk_net_conn: [DNS] Attempt=3
00> [14:00:36.042,724] <inf> nk_net_conn: [DNS] Duration=0 ms
00> [14:00:36.042,755] <err> nk_net_conn: [DNS] FAILED
00> [14:00:36.042,755] <err> nk_net_conn: [DNS] getaddrinfo err=-11
00> [14:00:36.042,785] <err> nk_net_conn: [DNS] errno=2 (No such file or directory)
00> [14:00:36.046,813] <err> nk_net_conn: [DNS] RSSI=-50
00> [14:00:36.046,813] <err> nk_net_conn: [DNS] WiFi Connected=1
00> [14:00:36.046,813] <err> nk_net_conn: [DNS] Retry remaining=0
00> [14:00:38.046,905] <err> nk_net_conn: ========== DNS RESOLVE FAILED ==========
00> [14:00:38.046,905] <err> nk_net_conn: All retries exhausted
00> [14:00:38.046,936] <inf> nk_net_mgr: NET Manager start
00> [14:00:38.046,936] <inf> nk_ws: WS stopped
00> [14:00:38.046,936] <inf> NK_Timer: WS RX Timer periodic timer stopped
00> [14:00:38.046,936] <inf> NK_Timer: WS Ping periodic timer stopped
00> [14:00:38.046,966] <err> NK_Timer: HubStatus failed → DNS resolve
00> [14:00:38.047,088] <inf> NK_Timer: Watchdog not Feed
00> [14:00:38.049,346] <inf> nk_net_mgr: STATE: RESOLVE
00> [14:00:38.049,346] <inf> nk_net_conn: ========== DNS RESOLVE START ==========
00> [14:00:38.049,377] <inf> nk_net_conn: Host              : api.nexkey.com
00> [14:00:38.049,407] <inf> nk_net_conn: Port              : 443
00> [14:00:38.054,168] <inf> nk_net_conn: RSSI              : -47
00> [14:00:38.054,168] <inf> nk_net_conn: System Uptime     : 50438 sec
00> [14:00:38.054,199] <inf> nk_net_conn: Thread            : �b
00> [14:00:38.054,229] <inf> nk_net_conn: =======================================
00> [14:00:38.054,229] <inf> nk_net_conn: [DNS] Attempt=1
00> [14:00:38.054,534] <inf> nk_net_conn: [DNS] Duration=0 ms
00> [14:00:38.054,565] <err> nk_net_conn: [DNS] FAILED
00> [14:00:38.054,565] <err> nk_net_conn: [DNS] getaddrinfo err=-11
00> [14:00:38.054,595] <err> nk_net_conn: [DNS] errno=2 (No such file or directory)
00> [14:00:38.062,591] <err> nk_net_conn: [DNS] RSSI=-47
00> [14:00:38.062,591] <err> nk_net_conn: [DNS] WiFi Connected=1
00> [14:00:38.062,591] <err> nk_net_conn: [DNS] Retry remaining=2
00> [14:00:38.065,765] <inf> wifi_mgr: DHCP IP: 192.168.201.11
00> [14:00:38.065,765] <inf> wifi_mgr: WiFi ready start server connect
00> [14:00:38.065,765] <inf> NK_Timer: WiFi monitor timer stopped
00> [14:00:38.065,795] <inf> nk_net_mgr: NET Manager start
00> [14:00:38.065,795] <inf> nk_ws: WS stopped
00> [14:00:38.065,795] <inf> NK_Timer: WS RX Timer periodic timer stopped
00> [14:00:38.065,795] <inf> NK_Timer: WS Ping periodic timer stopped
00> [14:00:40.062,652] <inf> nk_net_conn: [DNS] Attempt=2
00> [14:00:40.145,324] <inf> nk_net_conn: [DNS] Duration=83 ms
00> [14:00:40.145,355] <inf> nk_net_conn: [DNS] SUCCESS
00> [14:00:40.145,385] <inf> nk_net_conn: [DNS] Server IP=34.193.34.228
00> [14:00:40.150,115] <inf> nk_net_conn: [DNS] RSSI=-50
00> [14:00:40.150,146] <inf> nk_net_conn: ========== DNS RESOLVE SUCCESS ==========
00> [14:00:40.150,268] <inf> nk_net_mgr: STATE: TLS
00> [14:00:40.150,299] <inf> NK_Timer: Watchdog not Feed
00> [14:00:40.150,329] <inf> nk_net_mgr: STATE: CONNECT
00> [14:00:41.586,456] <inf> nk_net_conn: Server connected (TLS)
00> [14:00:41.586,853] <inf> nk_net_mgr: SERVER CONNECTED
00> [14:00:41.586,883] <inf> nk_net_conn: CLOUD BOOTSTRAP START
00> [14:00:42.319,732] <inf> NK_CLOUD_LOGIN: Login success token stored
00> [14:00:42.823,028] <inf> rtc_pcf85263: RTC time set successfully
00> [14:00:42.823,028] <inf> NK_CLOUD_OBJECTTIME: RTC synced from cloud
00> [14:00:42.823,211] <inf> NK_CLOUD_HUBSTATUS: ====== Calling HUBSTATUS API ======
00> [14:00:42.823,242] <inf> NK_CLOUD_HUBSTATUS: build_hub_status_json START
00> [14:00:42.824,157] <inf> rtc_pcf85263: RTC time read successfully
00> [14:00:42.824,279] <inf> NK_CLOUD_HUBSTATUS: sensorTime=2026-05-23T02:15:18.000Z
00> [14:00:42.834,411] <inf> NK_CLOUD_HUBSTATUS: build_hub_status_json END
00> [14:00:42.834,564] <inf> NK_CLOUD_HUBSTATUS: hub_status_payload : {"APINumber":2,"hubObjectId":"zstoCY93XJ","statusData":{"hub":{"hubObjectId":"zstoCY93XJ","hubId":"55003","description":""},"software":{"app":{"versionName":"0RNT99-EB_3630_PROD-1.0.0.8-beta"}},"hardware":{"device":"Controller B (WT02C40C)","uuid":"0641304100000000460039001851343438333231","rtc":1779502518},"network":{"type":"WIFI","details":{"ip":"192.168.201.11","public_ip":"34.193.34.228","ssid":"Nextkey","mac":"00:18:07:01:59:4C","rssi":-51}},"keypad":{"voltage_mV":0,"battery_percent":0,"temperature_C":0},"locks":[{"bleAddress":"FA:B2:AA:24:23:9B","firmwareVersion":"EB.05.10","lockId":"55003","state":1,"sensorTime":"2026-05-23T02:15:18.000Z","sensor":1}]}}
00> [14:00:42.834,655] <inf> NK_CLOUD_HUBSTATUS: HubStatus request sent
00> [14:00:43.364,471] <inf> NK_CLOUD_HUBSTATUS: HubStatus API response received
00> [14:00:43.364,746] <inf> NK_CLOUD_HUBSTATUS: HubStatus API response received
00> [14:00:43.364,837] <inf> nk_net_conn: CLOUD BOOTSTRAP DONE
00> [14:00:43.364,837] <inf> nk_net_mgr: NET Manager stop
00> [14:00:43.370,056] <inf> nk_net_conn: Server disconnected
00> [14:00:43.370,056] <inf> nk_ws: WS start
00> [14:00:43.402,648] <inf> nk_ws: WS DNS OK (attempt 1)
00> [14:00:43.403,137] <inf> nk_ws: WS TCP connect: spawning thread (attempt 1/3)
00> [14:00:43.403,961] <inf> nk_ws: [WS-TC Thread] connect() started — TLS handshake will happen here
00> [14:00:44.862,335] <inf> nk_ws: [WS-TC Thread] connect() SUCCESS — TCP + TLS done
00> [14:00:44.862,365] <inf> nk_ws: WS TCP connected (attempt 1) — TCP + TLS complete!
00> [14:00:44.862,365] <inf> nk_ws: WS handshake attempt 1
00> [14:00:45.073,364] <inf> nk_ws: WS connected
00> [14:00:45.074,768] <inf> nk_ws: WS ping
00> [14:00:45.074,768] <inf> NK_Timer: WS Ping periodic timer started
00> [14:00:45.075,500] <inf> NK_Timer: WS Rx periodic timer started
00> [14:00:45.075,531] <inf> NK_Timer: HubStatus periodic timer started
00> [14:00:45.075,988] <inf> NK_Timer: Watchdog not Feed
00> [14:00:45.228,363] <inf> NK_Timer: Watchdog not Feed
00> [14:00:45.676,330] <inf> nk_ws: WS RX: {"op":"connected","clientId":"1a8a3c3a-557c-4a5a-9cf9-35fd63b0e807"}
00> [14:00:45.676,391] <inf> nk_ws: Subscribing Hub: zstoCY93XJ
00> [14:00:46.190,032] <inf> nk_ws: WS RX: {"op":"subscribed","clientId":"1a8a3c3a-557c-4a5a-9cf9-35fd63b0e807","requestId":3}
00> [14:00:46.190,063] <inf> nk_ws: WS subscribed OK
00> [14:00:46.326,080] <inf> NK_Timer: Watchdog not Feed

I kept the device powered on since last Friday for long-term testing. During this period, the device disconnected from Wi-Fi 7 times, but the good thing is that it reconnected instantly each time.

I have increased the stack size–related macros in the project configuration file. After this change, the TLS and WebSocket connect API stuck issue has not been observed so far during the weekend long-term testing.

Updated project config file for your reference.

############################################
# Logging
############################################
CONFIG_LOG=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_SEGGER_RTT_BUFFER_SIZE_UP=2048
CONFIG_LOG_MODE_DEFERRED=y
CONFIG_LOG_MODE_IMMEDIATE=n
CONFIG_CBPRINTF_FP_SUPPORT=n

############################################
# DK (LED / Button)
############################################
# CONFIG_DK_LIBRARY=y

############################################
# Hardware Drivers
############################################
CONFIG_I2C=y
CONFIG_ADC=y
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_NVS=y
CONFIG_NVS_LOG_LEVEL_DBG=y
CONFIG_NVS_LOG_LEVEL_INF=y

############################################
# Watchdog
############################################
CONFIG_WATCHDOG=y
CONFIG_WDT_LOG_LEVEL_DBG=y
CONFIG_WDT_DISABLE_AT_BOOT=n

############################################
# Bootloader / OTA (MCUBoot)
############################################
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

# MCUBoot image manager API
CONFIG_IMG_MANAGER=y
CONFIG_MCUBOOT_IMG_MANAGER=y

CONFIG_IMG_ERASE_PROGRESSIVELY=y
CONFIG_PM_SINGLE_IMAGE=n

############################################
# Wi-Fi
############################################
CONFIG_WIFI=y
CONFIG_WIFI_NRF700X=y
CONFIG_WPA_SUPP=y

CONFIG_WIFI_CREDENTIALS=y
CONFIG_WIFI_CREDENTIALS_STATIC=n
CONFIG_WIFI_CREDENTIALS_BACKEND_SETTINGS=y
CONFIG_WIFI_MGMT_EXT=y

CONFIG_NET_CONNECTION_MANAGER=y
CONFIG_L2_WIFI_CONNECTIVITY=y

CONFIG_NRF700X_MAX_TX_AGGREGATION=4

############################################
# Networking Stack
############################################
CONFIG_NETWORKING=y
CONFIG_NET_NATIVE=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_SOCKETS_POSIX_NAMES=y
CONFIG_POSIX_MAX_FDS=16
CONFIG_NET_SOCKETS_POLL_MAX=6

CONFIG_NET_L2_ETHERNET=y
CONFIG_NET_IPV4=y
CONFIG_NET_IPV6=y
CONFIG_NET_TCP=y
CONFIG_NET_DHCPV4=y
CONFIG_DNS_RESOLVER=y
CONFIG_NET_CONFIG_NEED_IPV4=y

############################################
# TLS / Security
############################################
CONFIG_NET_SOCKETS_SOCKOPT_TLS=y
CONFIG_TLS_CREDENTIALS=y

CONFIG_NRF_SECURITY=y
CONFIG_MBEDTLS=y
CONFIG_MBEDTLS_TLS_LIBRARY=y
CONFIG_MBEDTLS_ENABLE_HEAP=y
CONFIG_MBEDTLS_HEAP_SIZE=81920

CONFIG_MBEDTLS_RSA_C=y
CONFIG_MBEDTLS_DHM_C=y
CONFIG_MBEDTLS_SSL_SERVER_NAME_INDICATION=y

CONFIG_PSA_WANT_KEY_TYPE_RSA_PUBLIC_KEY=y
CONFIG_PSA_WANT_RSA_KEY_SIZE_2048=y

CONFIG_NET_SOCKETS_ENABLE_DTLS=n
CONFIG_NET_SOCKETS_TLS_MAX_CONTEXTS=2

############################################
# HTTP / WebSocket
############################################
CONFIG_HTTP_CLIENT=y
CONFIG_WEBSOCKET_CLIENT=y

############################################
# JSON
############################################
CONFIG_CJSON_LIB=y

############################################
# C Library
############################################
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_NANO=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y

############################################
# Memory / Stacks
############################################
CONFIG_MAIN_STACK_SIZE=8192
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=8192
CONFIG_HEAP_MEM_POOL_SIZE=153600

CONFIG_NET_TCP_WORKQ_STACK_SIZE=2048
CONFIG_NET_TX_STACK_SIZE=4096
CONFIG_NET_RX_STACK_SIZE=4096

CONFIG_NET_BUF_RX_COUNT=36
CONFIG_NET_BUF_TX_COUNT=36
CONFIG_NET_BUF_DATA_SIZE=512
CONFIG_NET_TC_TX_COUNT=0

CONFIG_WIFI_INIT_PRIORITY=50

############################################
# Flash / Settings
############################################
CONFIG_FLASH_MAP=y
CONFIG_SETTINGS=y
CONFIG_SETTINGS_NVS=y
CONFIG_SETTINGS_NVS_SECTOR_COUNT=2
CONFIG_PM_PARTITION_SIZE_NVS_STORAGE=0x2000
CONFIG_MPU_ALLOW_FLASH_WRITE=y

############################################
# Bluetooth
############################################
CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_GATT_CLIENT=y
CONFIG_BT_SMP=n

CONFIG_BT_DEVICE_NAME="NKEY eLatch"

CONFIG_BT_USER_PHY_UPDATE=y
CONFIG_BT_USER_DATA_LEN_UPDATE=y

CONFIG_BT_PERIPHERAL_PREF_MIN_INT=15
CONFIG_BT_PERIPHERAL_PREF_MAX_INT=30
CONFIG_BT_PERIPHERAL_PREF_LATENCY=0
CONFIG_BT_PERIPHERAL_PREF_TIMEOUT=3200
CONFIG_BT_GAP_AUTO_UPDATE_CONN_PARAMS=y

# MTU / Data length
CONFIG_BT_CTLR_DATA_LENGTH_MAX=251
CONFIG_BT_BUF_ACL_RX_SIZE=251
CONFIG_BT_BUF_ACL_TX_SIZE=251
CONFIG_BT_L2CAP_TX_MTU=251

# Device Information Service
CONFIG_BT_DIS=y
CONFIG_BT_DIS_PNP=n
CONFIG_BT_DIS_MANUF="Nexkey"
CONFIG_BT_DIS_FW_REV=y
CONFIG_BT_DIS_FW_REV_STR="EB.05.10"

My concern is whether this fix will resolve the issue completely ?

Regards,

Dipesh

RE: WebSocket/TLS Connection Stuck Issue

Sigurd Hellesvik — Fri, 22 May 2026 14:06:03 GMT

For TLS issue:
Can you upload zephyr.elf and zephyr.map files from your build folder? With these, I can try to look into the hard fault and see if I can find anything.

Additionally, to debug the issue, I suggest that you set CONFIG_RESET_ON_FATAL_ERROR=n on a test device. Then it will not reset on the fatal error. When the device is in the fault state, you can attach a debugger. This can for example be done with the CLI command "west attach". Then you can use the GDB command "bt" to get a backtrace of the error. Sometimes this gives more insight into the issue.

[quote user="DipeshParikh_"]

We are facing one more issue related to Wi-Fi disconnects.

I’m providing the log file. You can search for the log:
“WiFi lost stop server”

This issue is happening while running one cycle called HubStatus.

HubStatus cycle flow:

Close WebSocket connection
Connect to TLS server
Perform API call
Close TLS server connection
Re-open WebSocket connection

Can you please help me to debug and resolve this issue.

RTT_Log_20260518_194631.txt

Your support is appreciated.

[/quote]

Can you log the reason why the Wi-Fi lost the stop server?

Ca code:

LOG_INF("wifi_mgr: disconnect reason=%d hubstatus_active=%d net_mgr_state=%d",
          reason, hubstatus_active, nk_net_mgr_state());

RE: WebSocket/TLS Connection Stuck Issue

Sigurd Hellesvik — Thu, 21 May 2026 13:54:58 GMT

For the TLS issue, try to increase CONFIG_NET_MAX_CONTEXTS and CONFIG_NET_SOCKETS_TLS_MAX_CONTEXTS to see if that helps. What are the results of this test?

I will look into your latest comment

RE: WebSocket/TLS Connection Stuck Issue

DipeshParikh_ — Wed, 20 May 2026 12:14:15 GMT

Hello, I’m waiting for your response.

We are facing one more issue related to Wi-Fi disconnects.

I’m providing the log file. You can search for the log:
“WiFi lost stop server”

This issue is happening while running one cycle called HubStatus.

HubStatus cycle flow:

Close WebSocket connection
Connect to TLS server
Perform API call
Close TLS server connection
Re-open WebSocket connection

Can you please help me to debug and resolve this issue.

devzone.nordicsemi.com/.../RTT_5F00_Log_5F00_20260518_5F00_194631.txt

Your support is appreciated.

Regards,
Dipesh

RE: WebSocket/TLS Connection Stuck Issue

DipeshParikh_ — Thu, 14 May 2026 04:21:20 GMT

Hi Sigurd Hellesvik,

Thank you for the response.

Here I'm providing you to my project config file.

############################################
# Logging
############################################
CONFIG_LOG=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_SEGGER_RTT_BUFFER_SIZE_UP=2048
CONFIG_LOG_MODE_DEFERRED=y
CONFIG_LOG_MODE_IMMEDIATE=n
CONFIG_CBPRINTF_FP_SUPPORT=n

############################################
# DK (LED / Button)
############################################
# CONFIG_DK_LIBRARY=y

############################################
# Hardware Drivers
############################################
CONFIG_I2C=y
CONFIG_ADC=y
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_NVS=y
CONFIG_NVS_LOG_LEVEL_DBG=y
CONFIG_NVS_LOG_LEVEL_INF=y

############################################
# Watchdog
############################################
CONFIG_WATCHDOG=y
CONFIG_WDT_LOG_LEVEL_DBG=y
CONFIG_WDT_DISABLE_AT_BOOT=n

############################################
# Bootloader / OTA (MCUBoot)
############################################
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

# MCUBoot image manager API
CONFIG_IMG_MANAGER=y
CONFIG_MCUBOOT_IMG_MANAGER=y

CONFIG_IMG_ERASE_PROGRESSIVELY=y
CONFIG_PM_SINGLE_IMAGE=n

############################################
# Wi-Fi
############################################
CONFIG_WIFI=y
CONFIG_WIFI_NRF700X=y
CONFIG_WPA_SUPP=y

CONFIG_WIFI_CREDENTIALS=y
CONFIG_WIFI_CREDENTIALS_STATIC=n
CONFIG_WIFI_CREDENTIALS_BACKEND_SETTINGS=y
CONFIG_WIFI_MGMT_EXT=y

CONFIG_NET_CONNECTION_MANAGER=y
CONFIG_L2_WIFI_CONNECTIVITY=y

CONFIG_NRF700X_MAX_TX_AGGREGATION=2

############################################
# Networking Stack
############################################
CONFIG_NETWORKING=y
CONFIG_NET_NATIVE=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_SOCKETS_POSIX_NAMES=y
CONFIG_POSIX_MAX_FDS=16
CONFIG_NET_SOCKETS_POLL_MAX=6

CONFIG_NET_L2_ETHERNET=y
CONFIG_NET_IPV4=y
CONFIG_NET_IPV6=y
CONFIG_NET_TCP=y
CONFIG_NET_DHCPV4=y
CONFIG_DNS_RESOLVER=y
CONFIG_NET_CONFIG_NEED_IPV4=y

############################################
# TLS / Security
############################################
CONFIG_NET_SOCKETS_SOCKOPT_TLS=y
CONFIG_TLS_CREDENTIALS=y

CONFIG_NRF_SECURITY=y
CONFIG_MBEDTLS=y
CONFIG_MBEDTLS_TLS_LIBRARY=y
CONFIG_MBEDTLS_ENABLE_HEAP=y
CONFIG_MBEDTLS_HEAP_SIZE=57344

CONFIG_MBEDTLS_RSA_C=y
CONFIG_MBEDTLS_DHM_C=y
CONFIG_MBEDTLS_SSL_SERVER_NAME_INDICATION=y

CONFIG_PSA_WANT_KEY_TYPE_RSA_PUBLIC_KEY=y
CONFIG_PSA_WANT_RSA_KEY_SIZE_2048=y

CONFIG_NET_SOCKETS_ENABLE_DTLS=n
CONFIG_NET_SOCKETS_TLS_MAX_CONTEXTS=1

############################################
# HTTP / WebSocket
############################################
CONFIG_HTTP_CLIENT=y
CONFIG_WEBSOCKET_CLIENT=y

############################################
# JSON
############################################
CONFIG_CJSON_LIB=y

############################################
# C Library
############################################
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_NANO=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y

############################################
# Memory / Stacks
############################################
CONFIG_MAIN_STACK_SIZE=6144
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096
CONFIG_HEAP_MEM_POOL_SIZE=153600

CONFIG_NET_TCP_WORKQ_STACK_SIZE=2048
CONFIG_NET_TX_STACK_SIZE=3072
CONFIG_NET_RX_STACK_SIZE=3072

CONFIG_NET_BUF_RX_COUNT=36
CONFIG_NET_BUF_TX_COUNT=36
CONFIG_NET_BUF_DATA_SIZE=512
CONFIG_NET_TC_TX_COUNT=0

CONFIG_WIFI_INIT_PRIORITY=50

############################################
# Flash / Settings
############################################
CONFIG_FLASH_MAP=y
CONFIG_SETTINGS=y
CONFIG_SETTINGS_NVS=y
CONFIG_SETTINGS_NVS_SECTOR_COUNT=2
CONFIG_PM_PARTITION_SIZE_NVS_STORAGE=0x2000
CONFIG_MPU_ALLOW_FLASH_WRITE=y

############################################
# Bluetooth
############################################
CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_GATT_CLIENT=y
CONFIG_BT_SMP=n

CONFIG_BT_USER_PHY_UPDATE=y
CONFIG_BT_USER_DATA_LEN_UPDATE=y

CONFIG_BT_PERIPHERAL_PREF_MIN_INT=15
CONFIG_BT_PERIPHERAL_PREF_MAX_INT=30
CONFIG_BT_PERIPHERAL_PREF_LATENCY=0
CONFIG_BT_PERIPHERAL_PREF_TIMEOUT=3200
CONFIG_BT_GAP_AUTO_UPDATE_CONN_PARAMS=y

# MTU / Data length
CONFIG_BT_CTLR_DATA_LENGTH_MAX=251
CONFIG_BT_BUF_ACL_RX_SIZE=251
CONFIG_BT_BUF_ACL_TX_SIZE=251
CONFIG_BT_L2CAP_TX_MTU=251

# Device Information Service
CONFIG_BT_DIS=y
CONFIG_BT_DIS_PNP=n
CONFIG_BT_DIS_FW_REV=y

Regardsm,

Dipesh

RE: WebSocket/TLS Connection Stuck Issue

Sigurd Hellesvik — Wed, 13 May 2026 13:37:13 GMT

Hi,

[quote user=""]Are there any known issues with TLS or TCP socket connections in nRF Connect SDK v2.6.2?[/quote]

See https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/known_issues.html

I will get back to the other questions later.

However, as a first step on debugging this, I suggest that you try to increase stack sizes related to TLS and see if that helps.

Can you share your project configuration, specifically the part related to TLS and crypto?

Regards,
Sigurd Hellesvik