# Docker Transmission Module to AWS **URL:** \ **Category:** Ignition\ **Created:** [May 15, 2023, 3:31pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728 "2023-05-15T15:31:51Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![Brian\_Dressler](https://avatars.discourse-cdn.com/v4/letter/b/e9c0ed/32.png) [@Brian\_Dressler](https://forum.inductiveautomation.com/u/Brian_Dressler)\ **Post date:** [May 15, 2023, 3:31pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/1 "2023-05-15T15:31:51Z")
I'm spinning up a docker container with Cirrus Link Transmission Module that will connect to AWS IoT. I have tried with both ignition versions 8.1.19 (Transmission 4.0.12) and version 8.1.26 (Transmission 4.0.16). I am getting the same intermittent error that it cannot connect. I can connect using the same versions and SSL certs from my physical host. If I wait long enough, sometimes it will actually connect. This is what the errors look like. Has anyone had success with docker container connection to AWS IoT? ```auto SSLSocketFactoryWrapper 15May2023 08:29:58 Failed to load Security Providers java.lang.UnsatisfiedLinkError: no conscrypt_openjdk_jni-linux-aarch_64 in java.library.path: [lib, lib/core/gateway] at java.base/java.lang.ClassLoader.loadLibrary(Unknown Source) at java.base/java.lang.Runtime.loadLibrary0(Unknown Source) at java.base/java.lang.System.loadLibrary(Unknown Source) at org.conscrypt.NativeLibraryUtil.loadLibrary(NativeLibraryUtil.java:54) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.base/java.lang.reflect.Method.invoke(Unknown Source) at org.conscrypt.NativeLibraryLoader$1.run(NativeLibraryLoader.java:297) at org.conscrypt.NativeLibraryLoader$1.run(NativeLibraryLoader.java:289) at java.base/java.security.AccessController.doPrivileged(Native Method) at org.conscrypt.NativeLibraryLoader.loadLibraryFromHelperClassloader(NativeLibraryLoader.java:289) at org.conscrypt.NativeLibraryLoader.loadLibrary(NativeLibraryLoader.java:262) at org.conscrypt.NativeLibraryLoader.load(NativeLibraryLoader.java:162) at org.conscrypt.NativeLibraryLoader.loadFirstAvailable(NativeLibraryLoader.java:106) at org.conscrypt.NativeCryptoJni.init(NativeCryptoJni.java:50) at org.conscrypt.NativeCrypto.(NativeCrypto.java:63) at org.conscrypt.OpenSSLProvider.(OpenSSLProvider.java:58) at org.conscrypt.OpenSSLProvider.(OpenSSLProvider.java:51) at org.conscrypt.OpenSSLProvider.(OpenSSLProvider.java:47) at com.cirruslink.common.mqtt.client.SSLSocketFactoryWrapper.loadProviders(SSLSocketFactoryWrapper.java:428) at com.cirruslink.common.mqtt.client.SSLSocketFactoryWrapper.getSocketFactory(SSLSocketFactoryWrapper.java:272) at com.cirruslink.common.mqtt.client.SSLSocketFactoryWrapper.(SSLSocketFactoryWrapper.java:101) at com.cirruslink.common.mqtt.client.CirrusClient.setMqttConnectOptions(CirrusClient.java:230) at com.cirruslink.common.mqtt.client.CirrusClient.setSslProps(CirrusClient.java:187) at com.cirruslink.common.mqtt.client.CirrusClient.(CirrusClient.java:152) at com.cirruslink.mqtt.transmission.gateway.TransmissionClient.connectToTargetServer(TransmissionClient.java:1103) at com.cirruslink.mqtt.transmission.gateway.TransmissionClient.run(TransmissionClient.java:845) at java.base/java.lang.Thread.run(Unknown Source) ``` ```auto TahuClient 15May2023 08:29:56 MT-551b4fc5-82eb-40b5: connect failed due to MqttException 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: java.net.UnknownHostException: AWSIoTHostName.iot.AWSRegion.amazonaws.com at java.base/java.net.AbstractPlainSocketImpl.connect(Unknown Source) at java.base/java.net.SocksSocketImpl.connect(Unknown Source) at java.base/java.net.Socket.connect(Unknown Source) at java.base/sun.security.ssl.SSLSocketImpl.connect(Unknown Source) at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:74) at org.eclipse.paho.client.mqttv3.internal.SSLNetworkModule.start(SSLNetworkModule.java:132) at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:724) ... 1 common frames omitted ``` ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 15, 2023, 4:21pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/2 "2023-05-15T16:21:58Z")
> [@Brian\_Dressler](#): > > `Caused by: java.net.UnknownHostException: something.something.amazonaws.com` Seems pretty clear. This isn't resolving. Edit: Redacted from my comment, too. ---
**Author:** ![Brian\_Dressler](https://avatars.discourse-cdn.com/v4/letter/b/e9c0ed/32.png) [@Brian\_Dressler](https://forum.inductiveautomation.com/u/Brian_Dressler)\ **Post date:** [May 15, 2023, 4:49pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/3 "2023-05-15T16:49:15Z")
I wish it were that simple. It is failing first on properly setting the SSL properties and opening SSL socket. The second error is resolving host. As I mentioned if I let the connection sit for 5-10 minutes and try it eventually connects. When I go to disable and enable the connection again I get the same errors (with success ~5-10 minutes later again). Also, I noticed I had my endpoint in the logs above so I went ahead and redacted that. ```auto SSLSocketFactoryWrapper 15May2023 08:29:58 Failed to load Security Providers java.lang.UnsatisfiedLinkError: no conscrypt_openjdk_jni-linux-aarch_64 in java.library.path: [lib, lib/core/gateway] ``` ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 15, 2023, 4:52pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/4 "2023-05-15T16:52:21Z")
> [@Brian\_Dressler](#): > > `java.lang.UnsatisfiedLinkError: no conscrypt_openjdk_jni-linux-aarch_64` Are you purposely using this security provider or is that happening automatically as part of your environment? Is your container really running on Linux / ARM64? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 15, 2023, 4:57pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/5 "2023-05-15T16:57:37Z")
{ I don't have the power to hide the pre-redaction versions.... @Kevin.Herron ? Brian's too, please. } ---
**Author:** ![Brian\_Dressler](https://avatars.discourse-cdn.com/v4/letter/b/e9c0ed/32.png) [@Brian\_Dressler](https://forum.inductiveautomation.com/u/Brian_Dressler)\ **Post date:** [May 15, 2023, 4:58pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/6 "2023-05-15T16:58:32Z")
On first question: That is happening automatically. On the second question: I'm running my container on my Mac. Does it not use the containerized SSL Provider? Is there anything I need to do during the build process to make sure that gets loaded? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 15, 2023, 4:59pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/7 "2023-05-15T16:59:30Z")
You probably aren't going to be able to run this on your ARM-based Mac. [That security provider](https://github.com/google/conscrypt) doesn't seem to provide Linux/ARM64 native libraries. ---
**Author:** ![Brian\_Dressler](https://avatars.discourse-cdn.com/v4/letter/b/e9c0ed/32.png) [@Brian\_Dressler](https://forum.inductiveautomation.com/u/Brian_Dressler)\ **Post date:** [May 15, 2023, 5:01pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/8 "2023-05-15T17:01:41Z")
Got it, good to know. Very weird though that it will eventually connect. I'm assuming if I run this on my Windows machine or non M1 Mac this would work? ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 15, 2023, 5:04pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/9 "2023-05-15T17:04:27Z")
I guess? I'm not really even sure why this security provider is being used. Maybe something about the container image you're using? The error may also be a red herring since it eventually connects. ---
**Author:** ![jspecht](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jspecht/32/6465_2.png) [@jspecht](https://forum.inductiveautomation.com/u/jspecht)\ **Post date:** [May 15, 2023, 5:12pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/10 "2023-05-15T17:12:12Z")
> [@Kevin.Herron](#): > > I'm not really even sure why this security provider is being used. FWIW: looks like conscrypt is included in the transmission module's modl file. Probably need Cirrus Link folks to chime in, but it's likely that it is bundled and used in whatever MQTT TLS context by design... ---
**Author:** ![Kevin.Collins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.collins/32/13497_2.png) [@Kevin.Collins](https://forum.inductiveautomation.com/u/Kevin.Collins)\ **Post date:** [May 15, 2023, 5:24pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/11 "2023-05-15T17:24:11Z")
Looks like their included conscrypt library doesn't include native libraries for aarch64... ![690x346](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/c/9cdca7cd6fc9264a0df58ad945fd6ba3033a5e10.jpeg) EDIT: looks like there is an open ticket [here](https://github.com/google/conscrypt/issues/858) for adding aarch64 builds to their uber jar... aaaaand Kevin H already covered this.. Sorry! #tooslow ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 15, 2023, 5:26pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/12 "2023-05-15T17:26:24Z")
Conscrypt doesn't publish a build with Linux/aarch64 native libraries. > [@Kevin.Herron](#): > > [That security provider](https://github.com/google/conscrypt) doesn't seem to provide Linux/ARM64 native libraries. ---
**Author:** ![Brian\_Dressler](https://avatars.discourse-cdn.com/v4/letter/b/e9c0ed/32.png) [@Brian\_Dressler](https://forum.inductiveautomation.com/u/Brian_Dressler)\ **Post date:** [May 15, 2023, 5:37pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/13 "2023-05-15T17:37:23Z")
ok, so this is making sense now. I built a gateway backup on my mac and loaded it along with the MQTT modules in docker. This is the build that is giving me issues. I just went ahead and built a blank ephemeral gateway and loaded transmission module. This connects without any issues. I think there is something in the database that is forcing it to use this provider... ---
**Author:** ![Brian\_Dressler](https://avatars.discourse-cdn.com/v4/letter/b/e9c0ed/32.png) [@Brian\_Dressler](https://forum.inductiveautomation.com/u/Brian_Dressler)\ **Post date:** [May 15, 2023, 7:52pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/14 "2023-05-15T19:52:22Z")
I'm going to post this here for posterity's sake. I reached out to Cirrus so hopefully I can get some resolution. If I run the following on my M1 Mac and manually install Transmission version 4.1.12 and configure SSL/AWS endpoint it connects every time without any issue: ```auto docker run -d -p 9088:8088 --name ignition-test inductiveautomation/ignition:8.1.19 \ -n docker-test1 -a localhost -h 9088 -s 9043 ``` If I run docker-compose and load a gateway backup I get the consrypt errors above. I'm assuming this has something to do with the backup database and what SSL security provider is uses. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [May 15, 2023, 7:58pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/15 "2023-05-15T19:58:41Z")
Please share the resolution when you get it figured out. Haven’t seen this one before. ---
**Author:** ![wes0johnson](https://avatars.discourse-cdn.com/v4/letter/w/7ab992/32.png) [@wes0johnson](https://forum.inductiveautomation.com/u/wes0johnson)\ **Post date:** [June 1, 2023, 9:38pm UTC](https://forum.inductiveautomation.com/t/docker-transmission-module-to-aws/73728/16 "2023-06-01T21:38:52Z")
This was an issue in that MQTT Transmission used Conscrypt for ALPN support in TLS connections to support Java8 which doesn't have native ALPN support. We've fixed this by upticking the minimum Java level to 11 and simply removing the Conscrypt dependency. This is now in the nightly modules and will be part of the 4.0.17 GA release.