# Self Signed Certs on Docker Containers

**URL:** <https://forum.inductiveautomation.com/t/self-signed-certs-on-docker-containers/62356>\
**Category:** Ignition\
**Tags:** docker, ignition81\
**Created:** [July 27, 2022, 4:05pm UTC](https://forum.inductiveautomation.com/t/self-signed-certs-on-docker-containers/62356 "2022-07-27T16:05:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\
**Post date:** [July 27, 2022, 4:05pm UTC](https://forum.inductiveautomation.com/t/self-signed-certs-on-docker-containers/62356/1 "2022-07-27T16:05:20Z")

</div>

I didnt realize until recently that in the web server config there was the ability to create a self-signed cert.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/0/903e91fcc9a851f08e6017c1db457e0a8e10864d.png)

This is fantastic! However I am curious, is there a way to download that cert content to then automatically add to docker containers? Or If one creates their own certs, somewhere they can automatically be added so that dev containers can be done with SSL

I appreciate any info!

Side Note: There should be a tag (or optional tag) on the forums for “Docker”, because I definitely think there are a lot of really docker specific questions here that would be good to make easier to find.

---

<div class="post-metadata">

**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\
**Post date:** [July 27, 2022, 4:08pm UTC](https://forum.inductiveautomation.com/t/self-signed-certs-on-docker-containers/62356/2 "2022-07-27T16:08:40Z")

</div>

> [@kgamble](#):
>
> There should be a tag (or optional tag) on the forums for “Docker”

Your wish is my command, er, tag. 🙂

---

<div class="post-metadata">

**Author:** ![kgamble](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kgamble/32/8019_2.png) [@kgamble](https://forum.inductiveautomation.com/u/kgamble)\
**Post date:** [July 27, 2022, 4:09pm UTC](https://forum.inductiveautomation.com/t/self-signed-certs-on-docker-containers/62356/3 "2022-07-27T16:09:45Z")

</div>

Thanks Kathy! I appreciate the speed. This is almost as good as the time that Kevin added the ability to

```auto
copy this text

```

about 20 seconds after I requested it! lol

---

<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:** [July 27, 2022, 4:22pm UTC](https://forum.inductiveautomation.com/t/self-signed-certs-on-docker-containers/62356/4 "2022-07-27T16:22:55Z")

</div>

All you have to do to enable TLS on an Ignition 8.1.x gateway is drop a PKCS#12 keystore into place at `${IGNITION_INSTALL_LOCATION}/data/local/ssl.pfx` (note that this location differs slightly from a standard install in order to preserve it in the data volume via a sym-link from `${IGNITION_INSTALL_LOCATION}/webserver/ssl.pfx`).