Gemalto is now part of the Thales Group, find out more.

You are here

EHS5-E TLS mutual authentication problem - Remote peer has closed the connection | Thales IoT Developer Community

August 31, 2021 - 10:59pm, 1612 views


I'm running EHS5-E and trying to establish TLS communication to AWS IoT mutual communication without success. The error code is:


^SIS: 0,0,48,"Remote peer has closed the connection"

I then tried to connect to server instead, and there they have 2 ports: server authentication mutual authentication (client cert required)

and for port 8883, the connection is successful, while for 8884, it got the same message "remote peer has closed the connection", similar to AWS IoT.

Here are the link to the mosquitto client private key, cert and mosquitto ca cert that I used.

Please note that I do the same connection tests using ELS61-E R2, using the same set of certificates to AWS and correspondingly, and all TLS communication works as expected. This got me to believe that something in the EHS5-E TLS stack is not right, specifically the client authentication part, causing the server to close the communication immediately. Unfortunately I have not managed to setup an internet server to capture TLS handshake yet.

My HW version:

URC: Cinterion
URC: A-REVISION 00.000.55
URC: at^sjam=5
URC: ^SJAM: "a:/JRC-1.56.58.jad","Java Remote Control MIDlet Suite","Cinterion", "1.56.58",1


It would be great if someone can do the same test (quite easy to do towards mosquitto server) and confirm the problem with the modem. Otherwise, any help would be appreciated. Thanks!