EG916Q-GL AT+QSSLOPEN Always Returns Error 579

IoT Modules LTE Standard Module
1

EG916Q-GL AT+QSSLOPEN Always Returns Error 579

Module Information

  • Module: EG916Q-GL

  • Firmware: EG916QGLLGR01A05M04_A0.300.A0.300

  • SIM: 1NCE IoT (ICCID: 89882280666142019797, IMSI: 901405114201979)

  • Network: Roaming (stat=5), RSSI=19 (-75 dBm)

  • Host MCU: ESP32-S3, communicating via UART AT commands at 115200 baud

Problem Description

AT+QSSLOPEN returns error code 579 for every TLS/SSL connection attempt. This error occurs regardless of:

  • Target server (www.google.com:443, custom AWS IoT endpoint on port 8883)

  • Security level (seclevel=0, 1, or 2)

  • SSL context (ctx 0 with certificates configured, ctx 1 completely clean/default)

  • SSL version (sslversion=3 for TLS 1.2 only, sslversion=4 for all)

  • Cipher suite (0xFFFF for all, 0x003C for specific)

  • Certificate configuration (mTLS with CA+cert+key, server-auth only, or NO certificates at all)

Raw TCP connections via AT+QIOPEN work correctly to the same servers and ports. The SSL/TLS functionality appears completely non-functional.

AT+QIGETERROR always reports +QIGETERROR: 0,operate successfully after each SSL failure, providing no useful diagnostic information.

AT+QMTOPEN with AT+QMTCFG="ssl" enabled also fails with result=5 (network connection error), consistent with the same broken TLS stack.

Error 579 is not documented in the Quectel AT Commands Manual for this module family (documented SSL error codes end at 574).

Network Environment


AT+QIACT?

+QIACT: 1,1,1,"100.76.161.65"

AT+QIDNSCFG=1

+QIDNSCFG: 1,"8.8.8.8","8.8.4.4"

AT+CCLK?

+CCLK: "26/02/18,20:33:17+00"

AT+QSSLOPEN=?

+QSSLOPEN: (1-15),(0-5),(0-11),<serveraddr>,<server_port>[,(0-2)]

Minimal Reproduction Steps

Step 1: Confirm TCP connectivity works


AT+QIOPEN=1,11,"TCP","www.google.com",443,0,0

OK

+QIOPEN: 11,0 <-- SUCCESS: TCP connection established

AT+QICLOSE=11

OK

Step 2: Configure a minimal SSL context (NO certificates, NO validation)


AT+QSSLCFG="sslversion",1,4

OK

AT+QSSLCFG="seclevel",1,0

OK

AT+QSSLCFG="ciphersuite",1,0xFFFF

OK

AT+QSSLCFG="sni",1,1

OK

Step 3: Verify the SSL context is clean (no certificate references)


AT+QSSLCFG="sslversion",1

+QSSLCFG: "sslversion",1,4

AT+QSSLCFG="seclevel",1

+QSSLCFG: "seclevel",1,0

AT+QSSLCFG="ciphersuite",1

+QSSLCFG: "ciphersuite",1,0XFFFF

AT+QSSLCFG="cacert",1

OK <-- Empty, no CA certificate

AT+QSSLCFG="clientcert",1

OK <-- Empty, no client certificate

AT+QSSLCFG="clientkey",1

OK <-- Empty, no client key

AT+QSSLCFG="sni",1

+QSSLCFG: "sni",1,1

Step 4: Attempt TLS connection


AT+QSSLOPEN=1,1,0,"www.google.com",443,0

OK

+QSSLOPEN: 0,579 <-- FAIL: Error 579 (undocumented)

AT+QIGETERROR

+QIGETERROR: 0,operate successfully <-- No useful error info

Step 5: For comparison, TCP to same server succeeds


AT+QIOPEN=1,11,"TCP","www.google.com",443,0,0

OK

+QIOPEN: 11,0 <-- SUCCESS

AT+QICLOSE=11

Complete Test Matrix (all fail with error 579)

| Test | seclevel | Target | SSL ctx | Certs | sslversion | ciphersuite | Result |

|------|----------|--------|---------|-------|------------|-------------|--------|

| 1 | 2 (mTLS) | AWS IoT:8883 | 0 | CA + cert + key | 3 | 0xFFFF | 579 |

| 2 | 2 (mTLS) | AWS IoT:8883 | 0 | AmazonRootCA1 only | 3 | 0xFFFF | 579 |

| 3 | 2 (mTLS) | AWS IoT:8883 | 0 | Starfield G2 only | 3 | 0xFFFF | 579 |

| 4 | 0 (none) | www.google.com:443 | 0 | client cert/key in ctx | 4 | 0xFFFF | 579 |

| 5 | 0 (none) | AWS IoT:8883 | 0 | client cert/key in ctx | 4 | 0xFFFF | 579 |

| 6 | 1 (server) | AWS IoT:8883 | 0 | AmazonRootCA1 | 4 | 0xFFFF | 579 |

| 7 | 0 (none) | www.google.com:443 | 1 (clean) | None at all | 4 | 0xFFFF | 579 |

| 8 | 0 (none) | www.google.com:443 | 1 (clean) | None at all | 3 | 0xFFFF | 579 |

Test 7 is the most significant: a completely clean SSL context with zero certificates, zero validation (seclevel=0), attempting to connect to www.google.com:443 — still returns error 579.

Independent Verification

We verified from a PC on the same network that the AWS IoT endpoint’s TLS chain validates correctly:


$ openssl s_client -connect a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883 -CAfile AmazonRootCA1.pem

...

Verify return code: 0 (ok)

Protocol: TLSv1.2

Cipher: ECDHE-RSA-AES128-GCM-SHA256

The server certificate chain and CA certificates are not the issue.

Certificate File Storage

Certificates are uploaded via AT+QFUPL and confirmed present:


AT+QFLST="*"

+QFLST: "UFS:ca.pem",2612

+QFLST: "UFS:client.key",1679

+QFLST: "UFS:client.pem",1220

Note: AT+QFLST shows files with "UFS:" prefix, but AT+QSSLCFG stores paths without prefix (e.g., "ca.pem"). We also confirmed AT+QSECWRITE is not supported on this firmware (returns ERROR).

Questions

  1. What does error code 579 mean? It is not in the documented error code range (ends at 574).

  2. Is there a known issue with SSL/TLS on this firmware version (EG916QGLLGR01A05M04)?

  3. Is there a newer firmware available for the EG916Q-GL that we should test?

  4. Should certificate file paths use the "UFS:" prefix in AT+QSSLCFG commands?

  5. Does AT+QMTOPEN with SSL use the same internal TLS stack as AT+QSSLOPEN?

  6. Are there any additional AT+QSSLCFG parameters we should set that are required for TLS to function? We noticed the module supports negotiatetime, ignoreinvalidcertsign, renegotiation, alpn — could any default values prevent TLS from working?

Attached: Full Boot Log

I (1253) MODEM: Modem UART1 init (TX:13 RX:12 @ 115200 baud)

I (1263) MODEM: Powering on modem (PWRKEY pulse)…

I (2463) MODEM: Modem STATUS is ON

I (8483) MODEM: Modem ID:

Quectel

EG916Q-GL

Revision: EG916QGLLGR01A05M04

OK

I (8983) MODEM: SIM ready

I (9483) MODEM: SIM ICCID: 89882280666142019797

I (9983) MODEM: SIM IMSI: 901405114201979

I (9983) MODEM: Carrier detected: 1NCE | Auto-APN: ‘iot.1nce.net’

I (9983) MODEM: Waiting for network registration…

I (10493) MODEM: Network registered (stat=5, roaming)

I (10993) MAIN_APP: LTE signal: RSSI=19 (-75 dBm)

I (10993) MODEM: Activating PDP with APN: ‘iot.1nce.net’ (carrier: 1NCE)

I (11523) MODEM: 3GPP PDP before config:

+CGDCONT: 1,“IP”,“iot.1nce.net”,“0.0.0.0”,0,0,0,0

OK

I (12553) MODEM: 3GPP PDP after config:

+CGDCONT: 1,“IP”,“iot.1nce.net”,“0.0.0.0”,0,0,0,0

OK

I (13053) MODEM: 3GPP PDP activation state:

+CGACT: 1,1

OK

I (16373) MODEM: PDP context:

+QIACT: 1,1,1,“100.76.161.65”

OK

I (16883) MODEM: Active DNS servers:

+QIDNSCFG: 1,“8.8.8.8”,“8.8.4.4”

OK

I (16883) MODEM: PDP active — waiting 3s for data path to stabilize…

I (19883) MAIN_APP: LTE modem ready

I (19883) MAIN_APP: LTE ready — starting MQTT

I (19883) APP_MQTT: Starting MQTT on LTE transport

I (19883) MQTT_LTE: Starting LTE MQTT connection (broker=‘mqtts://a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com’ port=8883)…

I (19893) APP_NVS: Attempting to load credentials from NVS…

I (19903) APP_NVS: Loaded ‘aws_root_ca’ (len=2612)

I (19903) APP_NVS: Loaded ‘aws_cert’ (len=1220)

I (24573) MQTT_LTE: Credentials uploaded to modem UFS

I (25143) MQTT_LTE: Modem files:

+QFLST: “UFS:ca.pem”,2612

+QFLST: “UFS:client.key”,1679

+QFLST: “UFS:client.pem”,1220

OK

I (25653) MODEM: Modem time:

+CCLK: “26/02/18,20:49:46+00”

OK

I (29653) MODEM: SSL context 0 configured for mTLS — reading back config:

I (30153) MODEM: sslversion:

+QSSLCFG: “sslversion”,0,3

OK

I (30663) MODEM: ciphersuite:

+QSSLCFG: “ciphersuite”,0,0XFFFF

OK

I (31163) MODEM: seclevel:

+QSSLCFG: “seclevel”,0,2

OK

I (31663) MODEM: cacert:

+QSSLCFG: “cacert”,0,“ca.pem”

OK

I (32173) MODEM: clientcert:

+QSSLCFG: “clientcert”,0,“client.pem”

OK

I (32683) MODEM: clientkey:

+QSSLCFG: “clientkey”,0,“client.key”

OK

I (33183) MODEM: sni:

+QSSLCFG: “sni”,0,1

OK

I (33693) MODEM: ignorelocaltime:

+QSSLCFG: “ignorelocaltime”,0,1

OK

I (34193) MODEM_MQTT: MQTT bound to PDP context 1

I (36193) MODEM_MQTT: MQTT SSL enabled (ctx 0)

I (36193) MQTT_LTE: === LTE TLS Diagnostic ===

I (36693) MQTT_LTE: Modem firmware:

EG916QGLLGR01A05M04_A0.300.A0.300

OK

W (36793) MODEM: Response buffer full (1023 bytes)

W (36793) MODEM: AT timeout. Partial RX (1023 bytes):

+QSSLCFG: “sslversion”,(0-5),(0-5)

+QSSLCFG: “dtls”,(0-5),(0,1)

+QSSLCFG: “ciphersuite”,(0-5),(0X0035,0X002F,0X0005,0X0004,0

W (36803) MQTT_LTE: QSSLCFG=? failed or truncated. Partial:

+QSSLCFG: “sslversion”,(0-5),(0-5)

+QSSLCFG: “dtls”,(0-5),(0,1)

+QSSLCFG: “ciphersuite”,(0-5),(0X0035,0X002F,0X0005,0X0004,0X000A,0X003D,0XC002,0XC003,0XC004,0XC005,0XC007,0XC008,0XC009,0XC00A,0XC011,0XC012,0XC013,0XC014,0XC00C,0XC00D,0XC00E,0XC00F,0XC023,0XC024,0XC025,0XC026,0XC027,0XC028,0XC029,0XC02A,0XC02F,0XC030,0XFFFF)

+QSSLCFG: “seclevel”,(0-5),(0-2)

+QSSLCFG: “cacert”,(0-5),

+QSSLCFG: “clientcert”,(0-5),<client_cert_path>

+QSSLCFG: “clientkey”,(0-5),<client_key_path>,<key_pwd>

+QSSLCFG: “sni”,(0-5),(0,1)

+QSSLCFG: “ignorelocaltime”,(0-5),(0,1)

+QSSLCFG: “negotiatetime”,(0-5),(10-150)

+QSSLCFG: “ignoreinvalidcertsign”,(0-5),(0,1)

+QSSLCFG: “ignorecertitem”,(0-5),(0-1048575)

+QSSLCFG: “ignoremulticertchainverify”,(0-5),(0,1)

+QSSLCFG: “session_cache”,(0-5),(0,1)

+QSSLCFG: “dtlsversion”,(0-5),(0,1)

+QSSLCFG: “psk_enable”,(0-5),(0,1)

+QSSLCFG: “psk”,(0-5),,

+QSSLCFG: “renegotiation”,(0-5),(0,1)

+QSSLCFG: “closetimemode”,(0-5),(0,1)

+QSSLCFG: “alpn”,(0-5),<p

I (37903) MQTT_LTE: QSSLOPEN syntax:

+QSSLOPEN: (1-15),(0-5),(0-11),,<server_port>[,(0-2)]

OK

I (38403) MQTT_LTE: Step 1: Testing raw TCP to broker a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883 …

I (39403) MODEM: TCP test: opening connection to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

I (41503) MODEM: Resolved a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com → 56.137.44.180 (via QISTATE)

I (42003) MODEM: TCP test SUCCESS: connected to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

I (42003) MQTT_LTE: *** RAW TCP OK (a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com → 56.137.44.180:8883) ***

I (42003) MQTT_LTE: Step 2: Testing mTLS via QSSLOPEN to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883 (seclevel=2)…

I (43023) MODEM: SSL test: opening TLS connection to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883 (ssl_ctx=0)

E (45203) MODEM: SSL test FAILED (err=579) to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

E (45703) MODEM: SSL error detail:

+QIGETERROR: 0,operate successfully

OK

E (45703) MQTT_LTE: *** mTLS FAILED with CA bundle — testing individual CAs ***

I (45703) APP_NVS: Attempting to load credentials from NVS…

I (45713) APP_NVS: Loaded ‘aws_root_ca’ (len=2612)

I (45713) APP_NVS: Loaded ‘aws_cert’ (len=1220)

I (45723) MQTT_LTE: CA bundle contains 2 cert(s), testing each individually:

I (45723) MQTT_LTE: Testing CA: CA[0] (AmazonRootCA1) (1188 bytes)…

I (47733) MODEM: Modem time:

+CCLK: “26/02/18,20:50:08+00”

OK

I (51733) MODEM: SSL context 0 configured for mTLS — reading back config:

I (52233) MODEM: sslversion:

+QSSLCFG: “sslversion”,0,3

OK

I (52743) MODEM: ciphersuite:

+QSSLCFG: “ciphersuite”,0,0XFFFF

OK

I (53243) MODEM: seclevel:

+QSSLCFG: “seclevel”,0,2

OK

I (53743) MODEM: cacert:

+QSSLCFG: “cacert”,0,“ca.pem”

OK

I (54253) MODEM: clientcert:

+QSSLCFG: “clientcert”,0,“client.pem”

OK

I (54763) MODEM: clientkey:

+QSSLCFG: “clientkey”,0,“client.key”

OK

I (55263) MODEM: sni:

+QSSLCFG: “sni”,0,1

OK

I (55773) MODEM: ignorelocaltime:

+QSSLCFG: “ignorelocaltime”,0,1

OK

I (56773) MODEM: SSL test: opening TLS connection to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883 (ssl_ctx=0)

E (59013) MODEM: SSL test FAILED (err=579) to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

E (59513) MODEM: SSL error detail:

+QIGETERROR: 0,operate successfully

OK

E (59513) MQTT_LTE: *** CA[0] (AmazonRootCA1): TLS FAILED ***

I (59513) MQTT_LTE: Testing CA: CA[1] (Starfield G2) (1424 bytes)…

I (61533) MODEM: Modem time:

+CCLK: “26/02/18,20:50:22+00”

OK

I (65543) MODEM: SSL context 0 configured for mTLS — reading back config:

I (66043) MODEM: sslversion:

+QSSLCFG: “sslversion”,0,3

OK

I (66553) MODEM: ciphersuite:

+QSSLCFG: “ciphersuite”,0,0XFFFF

OK

I (67053) MODEM: seclevel:

+QSSLCFG: “seclevel”,0,2

OK

I (67553) MODEM: cacert:

+QSSLCFG: “cacert”,0,“ca.pem”

OK

I (68063) MODEM: clientcert:

+QSSLCFG: “clientcert”,0,“client.pem”

OK

I (68573) MODEM: clientkey:

+QSSLCFG: “clientkey”,0,“client.key”

OK

I (69073) MODEM: sni:

+QSSLCFG: “sni”,0,1

OK

I (69583) MODEM: ignorelocaltime:

+QSSLCFG: “ignorelocaltime”,0,1

OK

I (70583) MODEM: SSL test: opening TLS connection to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883 (ssl_ctx=0)

E (72823) MODEM: SSL test FAILED (err=579) to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

E (73323) MODEM: SSL error detail:

+QIGETERROR: 0,operate successfully

OK

E (73323) MQTT_LTE: *** CA[1] (Starfield G2): TLS FAILED ***

E (73323) MQTT_LTE: *** DIAGNOSIS: No individual CA validated the server chain ***

E (73323) MQTT_LTE: *** Running TLS stack isolation tests… ***

I (73333) MQTT_LTE: — Test A: seclevel=0 to www.google.com:443 (no cert validation) —

I (74843) MQTT_LTE: seclevel readback:

+QSSLCFG: “seclevel”,0,0

OK

I (75843) MODEM: SSL test: opening TLS connection to www.google.com:443 (ssl_ctx=0)

E (78003) MODEM: SSL test FAILED (err=579) to www.google.com:443

E (78503) MODEM: SSL error detail:

+QIGETERROR: 0,operate successfully

OK

E (78503) MQTT_LTE: *** Test A FAILED — modem TLS stack may be broken ***

I (78503) MQTT_LTE: — Test B: seclevel=0 to AWS endpoint (no cert validation) —

I (79513) MODEM: SSL test: opening TLS connection to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883 (ssl_ctx=0)

E (81583) MODEM: SSL test FAILED (err=579) to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

E (82083) MODEM: SSL error detail:

+QIGETERROR: 0,operate successfully

OK

E (82083) MQTT_LTE: *** Test B FAILED — AWS may require client cert at TLS level ***

I (82083) MQTT_LTE: — Test C: seclevel=1 to AWS with CA[0] (server-auth only) —

I (85083) MQTT_LTE: seclevel readback:

+QSSLCFG: “seclevel”,0,1

OK

I (86083) MODEM: SSL test: opening TLS connection to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883 (ssl_ctx=0)

E (88283) MODEM: SSL test FAILED (err=579) to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

E (88793) MODEM: SSL error detail:

+QIGETERROR: 0,operate successfully

OK

E (88793) MQTT_LTE: *** Test C FAILED — CA truly doesn’t validate server chain ***

E (88793) MQTT_LTE: *** Run: openssl s_client -connect a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883 -CAfile AmazonRootCA1.pem -showcerts ***

I (88803) MQTT_LTE: — Test D: Fresh SSL context 1, NO certs, seclevel=0 to Google —

I (89323) MQTT_LTE: sslversion:

OK

I (91823) MQTT_LTE: ctx1 sslversion:

+QSSLCFG: “sslversion”,1,4

OK

I (92323) MQTT_LTE: ctx1 seclevel:

+QSSLCFG: “seclevel”,1,0

OK

I (92833) MQTT_LTE: ctx1 ciphersuite:

+QSSLCFG: “ciphersuite”,1,0XFFFF

OK

I (93333) MQTT_LTE: ctx1 cacert:

OK

I (93833) MQTT_LTE: ctx1 clientcert:

OK

I (94333) MQTT_LTE: ctx1 clientkey:

OK

I (94833) MQTT_LTE: ctx1 sni:

+QSSLCFG: “sni”,1,1

OK

I (95833) MODEM: SSL test: opening TLS connection to www.google.com:443 (ssl_ctx=1)

E (98363) MODEM: SSL test FAILED (err=579) to www.google.com:443

E (98863) MODEM: SSL error detail:

+QIGETERROR: 0,operate successfully

OK

E (98863) MQTT_LTE: *** Test D FAILED — TLS broken even on clean context ***

I (98863) MQTT_LTE: — Test E: Probing AT+QSECWRITE support —

W (99373) MODEM: RX [ERR]:

ERROR

I (99373) MQTT_LTE: QSECWRITE not supported (QFUPL path is correct)

W (99873) MODEM: RX [ERR]:

ERROR

I (99873) MQTT_LTE: — Test F: seclevel=0 ctx 1, sslversion=3 (TLS 1.2 only) —

I (100373) MQTT_LTE: sslversion set to 3 (TLS 1.2):

OK

I (101373) MODEM: SSL test: opening TLS connection to www.google.com:443 (ssl_ctx=1)

E (103403) MODEM: SSL test FAILED (err=579) to www.google.com:443

E (103903) MODEM: SSL error detail:

+QIGETERROR: 0,operate successfully

OK

E (103903) MQTT_LTE: *** Test F FAILED — TLS broken regardless of version ***

I (106003) MODEM: Modem time:

+CCLK: “26/02/18,20:51:06+00”

OK

I (110003) MODEM: SSL context 0 configured for mTLS — reading back config:

I (110503) MODEM: sslversion:

+QSSLCFG: “sslversion”,0,3

OK

I (111013) MODEM: ciphersuite:

+QSSLCFG: “ciphersuite”,0,0XFFFF

OK

I (111513) MODEM: seclevel:

+QSSLCFG: “seclevel”,0,2

OK

I (112013) MODEM: cacert:

+QSSLCFG: “cacert”,0,“ca.pem”

OK

I (112523) MODEM: clientcert:

+QSSLCFG: “clientcert”,0,“client.pem”

OK

I (113033) MODEM: clientkey:

+QSSLCFG: “clientkey”,0,“client.key”

OK

I (113533) MODEM: sni:

+QSSLCFG: “sni”,0,1

OK

I (114043) MODEM: ignorelocaltime:

+QSSLCFG: “ignorelocaltime”,0,1

OK

I (114543) MODEM_MQTT: MQTT bound to PDP context 1

I (116543) MODEM_MQTT: MQTT SSL enabled (ctx 0)

I (116543) MQTT_LTE: MQTT connection attempt 1/3 to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

I (116543) MQTT_LTE: Opening MQTT connection to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

W (117053) MODEM: RX [ERR]:

ERROR

E (119973) MODEM_MQTT: QMTOPEN failed (result=5):

+QMTOPEN: 0,5

E (119973) MQTT_LTE: Failed to open MQTT TCP connection to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

W (119973) MQTT_LTE: Attempt 1 failed, retrying in 5000 ms…

I (124983) MQTT_LTE: MQTT connection attempt 2/3 to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

I (124983) MQTT_LTE: Opening MQTT connection to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

W (125493) MODEM: RX [ERR]:

ERROR

E (128233) MODEM_MQTT: QMTOPEN failed (result=5):

+QMTOPEN: 0,5

E (128233) MQTT_LTE: Failed to open MQTT TCP connection to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

W (128233) MQTT_LTE: Attempt 2 failed, retrying in 5000 ms…

I (133243) MQTT_LTE: MQTT connection attempt 3/3 to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

I (133243) MQTT_LTE: Opening MQTT connection to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

W (133753) MODEM: RX [ERR]:

ERROR

E (136503) MODEM_MQTT: QMTOPEN failed (result=5):

+QMTOPEN: 0,5

E (136503) MQTT_LTE: Failed to open MQTT TCP connection to a2w1tnlfha6u8c-ats.iot.us-gov-west-1.amazonaws.com:8883

E (136503) MQTT_LTE: LTE MQTT failed after 3 attempts

2

Dear Customer,

579 error code is for our internal use only.
This seems firmware level TLS malfunction, I will send you latest firmware through your email.

Thank you.

Regards,
Fazrul Redzuan

3

Thank you, the firmware update has fixed the 579/TLS issue!

4

Hi Fazrul Redzuan,

I am facing similar issue. I am using “EG916Q-GL TEA card”. Can you please share the latest firmware with me as well.

5

Dear Customer,

Could you please help to create a new ticket and share your AT logs first? You may route the ticket directly to my name. I will review and analyze the AT logs and then share the appropriate firmware with you through the new ticket.

Thank you.