EG800Q-EU firmware A11 - HTTPS 701 error with script.google.com only

IoT Modules LTE Standard Module
1

Hi,

I have EG800Q-EU with firmware EG800QEULCR01A11M04 and I’m experiencing a reproducible HTTPS issue.

Works fine:

  • https://www.google.com → 200 OK

  • https://httpbin.org/get → 200 OK

Always fails:

  • https://script.google.com → +QHTTPGET: 701

Tested all combinations of sslversion (3 and 4), ciphersuite (0xC02F, 0xCCA8, 0xC030, 0x009C, 0xFFFF), with and without ALPN, seclevel=0, ignorelocaltime=1, sni=1. Always 701.

DNS resolves correctly (142.251.98.100). PDP context active.

Is this a known bug in firmware A11? Is there a newer firmware available that fixes TLS compatibility with Google services?

If anyone has a newer firmware package for EG800Q-EU, I would greatly appreciate it — I can apply it via AT+QFOTADL.

Thank you.

I am also interested in any workaround, not only firmware update. My device will be deployed remotely with no physical access — cloud communication via LTE is critical.

Mariusz

2

I have sent the latest firmware to your email,pls try again

1 Like
3

Update on my problem (HTTPS 701 with script.google.com)

Thank you so much for sending the firmware package — I really appreciate it!

Unfortunately I have two challenges with applying it:

  1. The package is the full firmware for QFlash (USB flashing) — but I only have a Mac, not a Windows PC. QFlash is Windows-only.

  2. My device will be deployed remotely with no physical access, so a delta package (.par) for DFOTA over HTTP would be the ideal solution — I can apply it via AT+QFOTADL.

Does anyone have the .par delta package for upgrading EG800QEULCR01A11M04 → A0.301.A0.301? It would let me update the module remotely without any cable or special software.

Also, before I commit to flashing, I’d like to know if A0.301.A0.301 actually fixes the HTTPS issue with script.google.com. Could anyone with this firmware test the following AT commands and share the result?

AT+QICSGP=1,1,"internet","","",1
AT+QIACT=1
AT+QHTTPCFG="contextid",1
AT+QHTTPCFG="sslctxid",1
AT+QHTTPCFG="responseheader",1
AT+QSSLCFG="sslversion",1,4
AT+QSSLCFG="ciphersuite",1,0xFFFF
AT+QSSLCFG="seclevel",1,0
AT+QHTTPURL=22,30
https://script.google.com
AT+QHTTPGET=60

If you get +QHTTPGET: 0,200,... → the firmware fixes the issue (great news!) If you get +QHTTPGET: 701 → the bug is still there in A0.301.

This 30-second test would help me decide whether flashing is worth the risk. Thank you!

— Mariusz