# How to Auto-Accept Self Signed Module Certs When Deploying Ignition with Docker

**URL:** <https://forum.inductiveautomation.com/t/how-to-auto-accept-self-signed-module-certs-when-deploying-ignition-with-docker/62696>\
**Category:** Ignition\
**Created:** [August 4, 2022, 7:31pm UTC](https://forum.inductiveautomation.com/t/how-to-auto-accept-self-signed-module-certs-when-deploying-ignition-with-docker/62696 "2022-08-04T19:31:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nicholas.robinson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nicholas.robinson/32/22188_2.png) [@nicholas.robinson](https://forum.inductiveautomation.com/u/nicholas.robinson)\
**Post date:** [August 4, 2022, 7:31pm UTC](https://forum.inductiveautomation.com/t/how-to-auto-accept-self-signed-module-certs-when-deploying-ignition-with-docker/62696/1 "2022-08-04T19:31:19Z")

</div>

We are getting ourselves up to speed with how to deploy Ignition to the cloud. The question of this post is what should we be doing to make it so that self signed certificates on our modules are automatically accepted?

Once we open the Ignition gateway running in a container we see this;

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/8/f8de695e84fe7948207e3447f9061ce4b00729fa.png)

In the docker file we point to the module which is located in our GIT repo like this:

```auto
COPY ./Walmart-SSO-signed.modl /usr/local/bin/ignition/user-lib/modules/Walmart-SSO-signed.modl

```

Is there something we can specify in the docker file or in the yml file that will make the certificate acceptance happen automatically?

Thanks,

Nick

---

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [August 4, 2022, 8:38pm UTC](https://forum.inductiveautomation.com/t/how-to-auto-accept-self-signed-module-certs-when-deploying-ignition-with-docker/62696/2 "2022-08-04T20:38:21Z")

</div>

You’ll want to achieve this by creating your own derived image (as it looks like you’re already doing). A multi-stage build is ideal for this, as it allows you to use some custom helper scripts (perhaps with their own dependencies) without them (or those dependencies) ending up in the final image.

Take a look at this demo video: [adhoc-00004.mp4](https://inductiveautomation1-my.sharepoint.com/:v:/g/personal/kcollins_inductiveautomation_com/EYaRwZNxos9Cjzed6is_4XQBTin_5g8ONTQG3QVdmMg3xg)

It describes how the functionality in this attached solution works and some insights on the “why”.

See here for a GH repo with the content from the demo video: [thirdgen88/ignition-derived-example](https://github.com/thirdgen88/ignition-derived-example)

---

<div class="post-metadata">

**Author:** ![nicholas.robinson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nicholas.robinson/32/22188_2.png) [@nicholas.robinson](https://forum.inductiveautomation.com/u/nicholas.robinson)\
**Post date:** [August 8, 2022, 2:45pm UTC](https://forum.inductiveautomation.com/t/how-to-auto-accept-self-signed-module-certs-when-deploying-ignition-with-docker/62696/3 "2022-08-08T14:45:23Z")

</div>

@kcollins thanks for this reference, we were able to use the register-module.sh called from our Docker file and now the modules will register correctly at time of container run.

Thanks,

Nick