HTTPS connection using AT#XHTTPCCON fails to connect to server

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

Heidi — Tue, 22 Jun 2021 10:51:33 GMT

It seems like Google might not be allowed by the network provider.

Can you confirm with the network provider whether you should be able to connect to Google's server?

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

EmbeddedDan — Mon, 21 Jun 2021 06:22:50 GMT

I can't connect to google.com through http, but I can connect to my development server:

The modem connects and send a POST request with HTTP

AT#XHTTPCCON=1,"******.westeurope.cloudapp.azure.com",8083
#XHTTPCCON: 1
AT#XHTTPCREQ="POST","/nbiot/device","Content-Type: application/json
Content-Length: 104
",104

Please let me know if you need anything else.

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

EmbeddedDan — Mon, 21 Jun 2021 05:50:48 GMT

AT%CMNG=1

AT%CMNG=1
%CMNG: 0,6,"0606060606060606060606060606060606060606060606060606060606060606"
%CMNG: 42,0,"0000000000000000000000000000000000000000000000000000000000000000"
%CMNG: 16842753,0,"0000000000000000000000000000000000000000000000000000000000000000"
%CMNG: 16842753,1,"0101010101010101010101010101010101010101010101010101010101010101"
%CMNG: 16842753,2,"0202020202020202020202020202020202020202020202020202020202020202"
%CMNG: 4294967293,10,"0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A0A"
%CMNG: 4294967292,11,"0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B0B"
OK

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

Heidi — Thu, 17 Jun 2021 12:41:26 GMT

Thanks.

What happens if you try to connect to Google without TLS?

AT#XHTTPCCON=1,"google.com",80

This could tell us if it's a TCP issue, HTTP issue or a TLS issue.

Could you also show me the return of AT%CMNG=1?

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

EmbeddedDan — Thu, 17 Jun 2021 08:16:34 GMT

Thanks yes I caught that typo

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

EmbeddedDan — Thu, 17 Jun 2021 08:16:13 GMT

I'm sending the AT#XHTTPCCON=1,"google.com",443,42 and then wait 30 seconds for a response. After around 10 seconds the application returns with

#XHTTPCCON: 0
ERROR
AT#XHTTPCCON=0
ERROR

I do not deactivate the modem from the AT command side. Is it doing it internally?

I'm trying to test an HTTPS connection to google.com, I do not have access to the server.

Included is a trace file from the modem where I don't send any other AT commands after the AT#XHTTPCCON=1,"google.com",443,42devzone.nordicsemi.com/.../trace_2D00_2021_2D00_06_2D00_17T08_2D00_13_2D00_00.348Z.bin

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

Heidi — Thu, 17 Jun 2021 07:10:39 GMT

Hi,

It looks like you are using the wrong syntax when connecting to the server:

AT#XHTTPCCON=1,"google.com",443,42"

The last quote is not required. It should be

AT#XHTTPCCON=1,"google.com",443,42

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

Heidi — Wed, 16 Jun 2021 08:28:38 GMT

Unfortunately, there's not much information in the log. There are lots of traces missing like before.

1) A TCP connection is attempted and then 300 ms after that modem is deactivated when the response from the server might be still on its way.

Are you deactivating the modem on purpose that quickly?

2) Are you able to log the server-side? Is the TCP SYN from the modem visible in the server log?

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

EmbeddedDan — Tue, 15 Jun 2021 10:05:22 GMT

Thanks Heidi

I have update the sdk & serial_lte_modem application to Tag v1.6.0-rc2 which includes PR4676

I have obtain a new nRF9160 Development Kit with a "B1" = Revision 2 modem and loaded Modem firmware mfw_nrf9160_1.3.0.
I'm running the same AT commands as before but fails when it calls the connect function in the resolve_and_connect function

[00:00:32.326,385] <inf> httpc: Attempting to connect over IPv6
[00:00:32.327,209] <inf> httpc: Setting up TLS credentials
[00:00:32.328,765] <err> httpc: Unable to connect, errno 114
[00:00:32.708,679] <inf> httpc: Attempting to connect over IPv4
[00:00:32.709,991] <inf> httpc: Setting up TLS credentials
[00:00:32.956,939] <err> httpc: Unable to connect, errno 116
[00:00:32.965,850] <err> httpc: Fail to resolve and connect
[00:00:32.965,850] <err> httpc: server_connect fail.

Here is the trace log:devzone.nordicsemi.com/.../trace_2D00_2021_2D00_06_2D00_15T10_2D00_03_2D00_27.815Z.bin

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

Heidi — Tue, 01 Jun 2021 07:44:03 GMT

Hi!

PR 4676 will fix the issue you're seeing.

Best regards,

Heidi

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

Heidi — Wed, 19 May 2021 13:33:06 GMT

Thank you! I have forwarded it to the modem team for analysis.

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

EmbeddedDan — Thu, 13 May 2021 09:20:55 GMT

I have added the AT%XMODEMTRACE=1,2 command to try and get the complete log.

devzone.nordicsemi.com/.../trace_2D00_2021_2D00_05_2D00_13T09_2D00_14_2D00_16.834Z.bin

Here is the trace of the AT commands.

****************
Nordic AT Client
****************
COM /dev/ttyACM0 Open
AT
Ready
OK
AT#XSLMUART?
#XSLMUART: 115200
OK
AT+CFUN=0
OK
AT%XMODEMTRACE=1,2
OK
AT%CMNG=2,42,0
%CMNG: 42,0,"0000000000000000000000000000000000000000000000000000000000000000","-----BEGIN CERTIFICATE-----
MIIDdzCCAl+gAwIBAgIEAgAAuTANBgkqhkiG9w0BAQUFADBaMQswCQYDVQQGEwJJ
RTESMBAGA1UEChMJQmFsdGltb3JlMRMwEQYDVQQLEwpDeWJlclRydXN0MSIwIAYD
VQQDExlCYWx0aW1vcmUgQ3liZXJUcnVzdCBSb290MB4XDTAwMDUxMjE4NDYwMFoX
DTI1MDUxMjIzNTkwMFowWjELMAkGA1UEBhMCSUUxEjAQBgNVBAoTCUJhbHRpbW9y
ZTETMBEGA1UECxMKQ3liZXJUcnVzdDEiMCAGA1UEAxMZQmFsdGltb3JlIEN5YmVy
VHJ1c3QgUm9vdDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKMEuyKr
mD1X6CZymrV51Cni4eiVgLGw41uOKymaZN+hXe2wCQVt2yguzmKiYv60iNoS6zjr
IZ3AQSsBUnuId9Mcj8e6uYi1agnnc+gRQKfRzMpijS3ljwumUNKoUMMo6vWrJYeK
mpYcqWe4PwzV9/lSEy/CG9VwcPCPwBLKBsua4dnKM3p31vjsufFoREJIE9LAwqSu
XmD+tqYF/LTdB1kC1FkYmGP1pWPgkAx9XbIGevOF6uvUA65ehD5f/xXtabz5OTZy
dc93Uk3zyZAsuT3lySNTPx8kmCFcB5kpvcY67Oduhjprl3RjM71oGDHweI12v/ye
jl0qhqdNkNwnGjkCAwEAAaNFMEMwHQYDVR0OBBYEFOWdWTCCR1jMrPoIVDaGezq1
BE3wMBIGA1UdEwEB/wQIMAYBAf8CAQMwDgYDVR0PAQH/BAQDAgEGMA0GCSqGSIb3
DQEBBQUAA4IBAQCFDF2O5G9RaEIFoN27TyclhAO992T9Ldcw46QQF+vaKSm2eT92
9hkTI7gQCvlYpNRhcL0EYWoSihfVCr3FvDB81ukMJY2GQE/szKN+OMY3EU/t3Wgx
jkzSswF07r51XgdIGn9w/xZchMB5hbgF/X++ZRGjD8ACtPhSNzkE1akxehi/oCr0
Epn3o0WC4zxe9Z2etciefC7IpJ5OCBRLbf1wbWsaY71k5h+3zvDyny67G7fyUIhz
ksLi4xaNmjICq44Y3ekQEe5+NauQrz4wlHrQMz2nZQ/1/I6eYs9HRCwBXbsdtTLS
R9I4LtD+gdwyah617jzV/OeBHRnDJELqYzmp
-----END CERTIFICATE-----"
AT%XSYSTEMMODE=0,1,0,2
OK
AT%XBANDLOCK=1,"111000000"
OK
AT%XDEEPSEARCH=1
OK
AT+CGDCONT=0,"IP","nbiot.vodacom.za"
OK
AT+COPS=0
OK
AT+CEREG=5
OK
AT+CFUN=21
OK
AT%XICCID
ERROR
Check SIM
AT+CPIN="3349"
OK
+CEREG: 2,"5209","0A19790D",9,0,0,"11100000","11100000"
+CEREG: 1,"5209","0A19790D",9,,,"11100000","00000110"
AT%XICCID
%XICCID: 89330000000020549718
OK
Waiting 1 sec
AT+CGDCONT?
+CGDCONT: 0,"IP","nbiot.vodacom.za","10.170.41.71",0,0
OK
AT#XHTTPCCON=1,"google.com",443,42"
AT#XHTTPCCON=0
Hit any key: 
AT+CFUN=0

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

Heidi — Wed, 12 May 2021 10:35:01 GMT

Unfortunately, the trace is missing too much data to read anything from it, and it's also very short.

At least you don't get an error anymore. Can you use %CMNG to confirm that there are certificates stored in sec_tag 42?

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

EmbeddedDan — Thu, 06 May 2021 06:27:00 GMT

I've confirmed that the band our local NB-IoT service provider uses is actually Band 8:

I've updated the bandlock command to include Band 7 & 8, but I still receive AT#XHTTPCCON=0 when a try to connect to Google with AT#XHTTPCCON=1,"google.com",443,42"

devzone.nordicsemi.com/.../trace_2D00_2021_2D00_05_2D00_06T06_2D00_20_2D00_49.551Z.bin

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

Heidi — Tue, 04 May 2021 12:39:04 GMT

It could be that you haven't disabled UART1 completely, which is the peripheral used for the traces from the modem.

In any case, if changing the bandlock solves the issue we won't need another trace.

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

EmbeddedDan — Tue, 04 May 2021 11:26:18 GMT

No that is a mistake. The only band we have here is Band 7, The bandlock setting was recommended by the local Nordic supplier. I will change that.

Any recommendation to fix the problem with the incomplete log?

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

Heidi — Tue, 04 May 2021 11:21:56 GMT

The log is not complete. A lot of traces seem to be missing which makes it difficult to analyze.

However, the bandlock setting might be something to check. The permanent bandlock is set to band 8 and band 7 is the only band visible in the log. Is that intentional?

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

Heidi — Mon, 03 May 2021 13:47:19 GMT

Thank you. I'm going to have someone from the modem team take a look at this tomorrow and then I'll get back to you.

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

EmbeddedDan — Fri, 30 Apr 2021 06:35:05 GMT

I'm waiting for either +CEREG:1 or +CEREG: 5. In this case I receive +CEREG: 1 which means 'Registered, home network'.

I have attached the logs with the new log levels enabled.

The first modem trace is with commands entered using the LTE Link Monitor.

devzone.nordicsemi.com/.../trace_2D00_2021_2D00_04_2D00_30T06_2D00_22_2D00_27.472Z.bin devzone.nordicsemi.com/.../2021_2D00_04_2D00_30T06_5F00_08_5F00_10.897Z_2D00_log.txt

The second trace is with the automated script.

devzone.nordicsemi.com/.../trace_2D00_2021_2D00_04_2D00_30T06_2D00_31_2D00_49.640Z.bin

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

Heidi — Thu, 29 Apr 2021 14:43:23 GMT

It looks like you're not waiting for +CEREG to return status 5, Registered, roaming before running the #HTTPCCON command. Could that be right?

Also, could you change this to CONFIG_SLM_LOG_LEVEL_DBG=y to get all log messages and add CONFIG_AT_CMD_LOG_LEVEL_DBG=y as well.

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

EmbeddedDan — Wed, 28 Apr 2021 13:18:55 GMT

mfw_nrf9160_1.2.3

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

Heidi — Wed, 28 Apr 2021 13:16:50 GMT

Thanks. What MFW version are you running?

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

EmbeddedDan — Wed, 28 Apr 2021 05:54:12 GMT

The serial_lte_modem application does have the necessary configurations set:

#
# Copyright (c) 2020 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#
# General config
CONFIG_LOG=y
CONFIG_LOG_DEFAULT_LEVEL=3
CONFIG_STACK_SENTINEL=y
CONFIG_NEWLIB_LIBC=y
CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y
CONFIG_RING_BUFFER=y

# Segger RTT
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_UART=n

# Network
CONFIG_NETWORKING=y
CONFIG_NET_SOCKETS=y
CONFIG_NET_NATIVE=n

# Modem library
CONFIG_NRF_MODEM_LIB=y
# Align the max FD entry to NRF_MODEM_MAX_SOCKET_COUNT(8)
CONFIG_POSIX_MAX_FDS=8
# Enable below for modem trace
CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y

# Use GPIO
CONFIG_GPIO=y
CONFIG_GPIO_NRFX=y
CONFIG_GPIO_NRF_P0=y

# UART interface
CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y
CONFIG_NRFX_TIMER2=y

# LTE link control
CONFIG_LTE_LINK_CONTROL=y
CONFIG_LTE_AUTO_INIT_AND_CONNECT=n

# Stacks and heaps
CONFIG_MAIN_STACK_SIZE=4096
CONFIG_HEAP_MEM_POOL_SIZE=16384
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096

# AT_CMD
# Enable AT_CMD debug for details
#CONFIG_AT_CMD_LOG_LEVEL_DBG=y
CONFIG_AT_CMD_RESPONSE_MAX_LEN=4096

# Device power management
CONFIG_DEVICE_POWER_MANAGEMENT=y

# Enable SUPL client support
#CONFIG_SUPL_CLIENT_LIB=y

# FOTA
CONFIG_HTTP_PARSER_URL=y
CONFIG_FOTA_DOWNLOAD=y
CONFIG_FOTA_DOWNLOAD_PROGRESS_EVT=y
CONFIG_DFU_TARGET=y
CONFIG_DOWNLOAD_CLIENT=y
CONFIG_DOWNLOAD_CLIENT_STACK_SIZE=4096
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_IMG_MANAGER=y
CONFIG_FLASH=y
CONFIG_IMG_ERASE_PROGRESSIVELY=y

#
# SLM-specific configurations
#
CONFIG_SLM_LOG_LEVEL_INF=y
# Configure external XTAL for UART
CONFIG_SLM_EXTERNAL_XTAL=n
# Enable GPIO wakeup if sleep is expected
#CONFIG_SLM_GPIO_WAKEUP=y
# Use UART_0 (when working with PC terminal)
CONFIG_UART_0_NRF_HW_ASYNC_TIMER=2
CONFIG_SLM_DATAMODE_HWFC=n
# Use UART_2 (when working with external MCU)
#CONFIG_SLM_CONNECT_UART_2=y
#CONFIG_UART_2_NRF_HW_ASYNC_TIMER=2

# Use optional GPS service
#CONFIG_SLM_GPS=y
# Use optional FTP client service
#CONFIG_SLM_FTPC=y
# Use optional MQTT client service
#CONFIG_SLM_MQTTC=y
# Use optional HTTP client service
CONFIG_SLM_HTTPC=y
# Enable Key Management Library
CONFIG_MODEM_KEY_MGMT=y

#Enable Debug symbols
CONFIG_DEBUG_OPTIMIZATIONS=y

RE: HTTPS connection using AT#XHTTPCCON fails to connect to server

Heidi — Mon, 26 Apr 2021 14:11:58 GMT

Hi!

First question, did you add CONFIG_SLM_HTTPC=y to the prj.conf file, to enable the HTTP module in the SLM application?

In the meantime, I will take a look at the trace.

Best regards,

Heidi