# \[Transmission\]Connect to IoT Core =\> Received fatal alert: protocol\_version

**URL:** <https://forum.cirrus-link.com/t/transmission-connect-to-iot-core-received-fatal-alert-protocol-version/831>\
**Category:** Ignition Modules\
**Created:** [December 15, 2025, 9:07pm UTC](https://forum.cirrus-link.com/t/transmission-connect-to-iot-core-received-fatal-alert-protocol-version/831 "2025-12-15T21:07:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gnguyen](https://avatars.discourse-cdn.com/v4/letter/g/41988e/32.png) [@gnguyen](https://forum.cirrus-link.com/u/gnguyen)\
**Post date:** [December 15, 2025, 9:07pm UTC](https://forum.cirrus-link.com/t/transmission-connect-to-iot-core-received-fatal-alert-protocol-version/831/1 "2025-12-15T21:07:27Z")

</div>

Hi,

I try to connect Transmission 5.0.1 to AWS IoT Core.

I receive this error:

```auto
org.eclipse.paho.client.mqttv3.MqttException: MqttException
at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:38)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:738)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: protocol_version
at java.base/sun.security.ssl.Alert.createSSLException(Unknown Source)
at java.base/sun.security.ssl.Alert.createSSLException(Unknown Source)
at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source)
at java.base/sun.security.ssl.Alert$AlertConsumer.consume(Unknown Source)
at java.base/sun.security.ssl.TransportContext.dispatch(Unknown Source)
at java.base/sun.security.ssl.SSLTransport.decode(Unknown Source)
at java.base/sun.security.ssl.SSLSocketImpl.decode(Unknown Source)
at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at org.eclipse.paho.client.mqttv3.internal.SSLNetworkModule.start(SSLNetworkModule.java:159)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:724)

```

I’ve added wrapper.java.additional.100=-Djdk.tls.client.protocols=TLSv1.2,TLSv1.3 in ignition.conf and restarted the gateway and tried IoTSecurityPolicy\_TLS13\_1\_2\_2022\_10 and and othet option in domain configuration with no success.

Any idea?

BR

---

<div class="post-metadata">

**Author:** ![gnguyen](https://avatars.discourse-cdn.com/v4/letter/g/41988e/32.png) [@gnguyen](https://forum.cirrus-link.com/u/gnguyen)\
**Post date:** [December 15, 2025, 9:18pm UTC](https://forum.cirrus-link.com/t/transmission-connect-to-iot-core-received-fatal-alert-protocol-version/831/2 "2025-12-15T21:18:01Z")

</div>

Additional info form CLI:

```auto
$ aws iot describe-domain-configuration --domain-configuration-name "iot:Data-ATS"
{
    "domainConfigurationName": "iot:Data-ATS",
    "domainConfigurationArn": "arn:aws:iot:us-west-1:CLIENTID:domainconfiguration/iot:Data-ATS",
    "domainName": "BLAHBLAHBLAH-ats.iot.us-west-1.amazonaws.com",
    "serverCertificates": [],
    "domainConfigurationStatus": "ENABLED",
    "serviceType": "DATA",
    "domainType": "ENDPOINT",
    "lastStatusChangeDate": "2025-12-15T20:00:30.662000+00:00",
    "tlsConfig": {
        "securityPolicy": "IoTSecurityPolicy_TLS13_1_2_2022_10"
    },
    "authenticationType": "DEFAULT",
    "applicationProtocol": "DEFAULT"
}

```

---

<div class="post-metadata">

**Author:** ![wes.johnson](https://avatars.discourse-cdn.com/v4/letter/w/f14d63/32.png) [@wes.johnson](https://forum.cirrus-link.com/u/wes.johnson)\
**Post date:** [December 15, 2025, 10:19pm UTC](https://forum.cirrus-link.com/t/transmission-connect-to-iot-core-received-fatal-alert-protocol-version/831/3 "2025-12-15T22:19:57Z")

</div>

It appears there is an issue with TLS 1.3 on our side. I’m creating a ticket to look into this on our side.

For the time being, I think you may be able to work around this by using TLS 1.2 on the AWS IoT Core side. We could not repro with this:  
`"tlsConfig": { "securityPolicy": "IoTSecurityPolicy_TLS12_1_0_2015_01" },`

I’ll provide an update on TLS 1.3 support when I have it.

---

<div class="post-metadata">

**Author:** ![gnguyen](https://avatars.discourse-cdn.com/v4/letter/g/41988e/32.png) [@gnguyen](https://forum.cirrus-link.com/u/gnguyen)\
**Post date:** [December 16, 2025, 7:01am UTC](https://forum.cirrus-link.com/t/transmission-connect-to-iot-core-received-fatal-alert-protocol-version/831/4 "2025-12-16T07:01:03Z")

</div>

Good catch.

Thank you @wes.johnson

---

<div class="post-metadata">

**Author:** ![wes.johnson](https://avatars.discourse-cdn.com/v4/letter/w/f14d63/32.png) [@wes.johnson](https://forum.cirrus-link.com/u/wes.johnson)\
**Post date:** [December 28, 2025, 2:17am UTC](https://forum.cirrus-link.com/t/transmission-connect-to-iot-core-received-fatal-alert-protocol-version/831/5 "2025-12-28T02:17:04Z")

</div>

This has been fixed in the Cirrus Link modules nightly build. They did not previously support TLS 1.3. They do now in the nightly builds and will in the next official releases.
