Resolve HTTPS Endpoint Issue for AVR-IoT Project
Budget: $10 – $30 USD
I’m working on a project with the AVR-IoT Cellular Mini (Sequans Monarch 2 modem), where I modified the Arduino-based firmware myself to periodically transmit GPS latitude and longitude data to my backend (BE) over HTTPS.
The objective is to send GPS data (latitude, longitude, and timestamp) to a REST API endpoint at a defined interval and confirm that the data is successfully received and visible on the backend.
At the moment, I’m blocked by a TLS issue while attempting to configure the CA certificate for HTTPS. When I try to add the root CA certificate (ISRG Root X1 – Let’s Encrypt) to the device/modem, I get an error that says:
“CA certificate input too long”
Because of this issue:
• The TLS handshake fails.
• The HTTPS request does not complete.
• The endpoint is never reached.
• No GPS payload appears on the backend.
What I have done so far:
• Generated and included the ISRG Root X1 certificate in PEM format.
• Attempted to load the certificate into the modem for server verification.
• Built a custom HTTP POST payload in Arduino to send JSON data (latitude, longitude, timestamp).
• Verified that the payload structure itself is correct.
The problem seems to occur specifically during certificate loading and TLS configuration.
What I need to resolve:
• The correct method for storing or uploading the CA certificate to the Sequans modem, considering possible size limitations.
• Whether the certificate needs to be converted from PEM to DER format.
• How to properly configure TLS so the endpoint can be reached.
• Ensure that the HTTPS POST request successfully sends the GPS data to the backend.
Ultimately, I need to resolve the HTTPS endpoint issue so I can verify that my custom Arduino firmware reliably transmits GPS data to the backend within the required time interval. Any guidance on handling CA certificate size limits or correctly configuring TLS on the AVR-IoT Cellular Mini would be greatly appreciated.
The objective is to send GPS data (latitude, longitude, and timestamp) to a REST API endpoint at a defined interval and confirm that the data is successfully received and visible on the backend.
At the moment, I’m blocked by a TLS issue while attempting to configure the CA certificate for HTTPS. When I try to add the root CA certificate (ISRG Root X1 – Let’s Encrypt) to the device/modem, I get an error that says:
“CA certificate input too long”
Because of this issue:
• The TLS handshake fails.
• The HTTPS request does not complete.
• The endpoint is never reached.
• No GPS payload appears on the backend.
What I have done so far:
• Generated and included the ISRG Root X1 certificate in PEM format.
• Attempted to load the certificate into the modem for server verification.
• Built a custom HTTP POST payload in Arduino to send JSON data (latitude, longitude, timestamp).
• Verified that the payload structure itself is correct.
The problem seems to occur specifically during certificate loading and TLS configuration.
What I need to resolve:
• The correct method for storing or uploading the CA certificate to the Sequans modem, considering possible size limitations.
• Whether the certificate needs to be converted from PEM to DER format.
• How to properly configure TLS so the endpoint can be reached.
• Ensure that the HTTPS POST request successfully sends the GPS data to the backend.
Ultimately, I need to resolve the HTTPS endpoint issue so I can verify that my custom Arduino firmware reliably transmits GPS data to the backend within the required time interval. Any guidance on handling CA certificate size limits or correctly configuring TLS on the AVR-IoT Cellular Mini would be greatly appreciated.