# Certificate renewals

**URL:** <https://forum.inductiveautomation.com/t/certificate-renewals/109136>\
**Category:** Ignition 8.3 Early Access\
**Created:** [July 30, 2025, 12:57pm UTC](https://forum.inductiveautomation.com/t/certificate-renewals/109136 "2025-07-30T12:57:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mquinn](https://avatars.discourse-cdn.com/v4/letter/m/cab0a1/32.png) [@mquinn](https://forum.inductiveautomation.com/u/mquinn)\
**Post date:** [July 30, 2025, 12:57pm UTC](https://forum.inductiveautomation.com/t/certificate-renewals/109136/1 "2025-07-30T12:57:26Z")

</div>

Did something change in how certificate renewals work? I've been using 8.1 with an auto renew script that bundles the cert and chain into /usr/local/bin/ignition/webserver/ssl.pfx with an alias of ignition and password of ignition, then invoking gwcmd.sh --reloadks to apply the new certificate.

This doesn't seem to be working anymore after upgrading to 8.3. The docs don't seem to discuss applying a certificate outside the GUI. At a glance I don't see anything in the API for certificate management either. I could be missing something though.

---

<div class="post-metadata">

**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:** [July 30, 2025, 1:06pm UTC](https://forum.inductiveautomation.com/t/certificate-renewals/109136/2 "2025-07-30T13:06:19Z")

</div>

> [@mquinn](#):
>
> /usr/local/bin/ignition/webserver/ssl.pfx

I think the location changed.

Try `$IGNITION/data/config/local/ignition/webserver/keystore/ssl.pfx`

---

<div class="post-metadata">

**Author:** ![mquinn](https://avatars.discourse-cdn.com/v4/letter/m/cab0a1/32.png) [@mquinn](https://forum.inductiveautomation.com/u/mquinn)\
**Post date:** [July 30, 2025, 1:21pm UTC](https://forum.inductiveautomation.com/t/certificate-renewals/109136/3 "2025-07-30T13:21:33Z")

</div>

That's got it. I removed the file and created a symlink to my ssl.pfx over in my main certs directory, any reason why that would cause an issue?

---

<div class="post-metadata">

**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:** [July 30, 2025, 2:00pm UTC](https://forum.inductiveautomation.com/t/certificate-renewals/109136/4 "2025-07-30T14:00:55Z")

</div>

Should be okay unless maybe somebody starts using the web UI or API to update the keystore.

---

<div class="post-metadata">

**Author:** ![philip](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/philip/32/5709_2.png) [@philip](https://forum.inductiveautomation.com/u/philip)\
**Post date:** [February 14, 2026, 11:09pm UTC](https://forum.inductiveautomation.com/t/certificate-renewals/109136/5 "2026-02-14T23:09:02Z")

</div>

Burned by this change of location today when the certificate expired and the renewal wasn’t going to the correct location. Anyway to get this location documented at this page

[https://www.docs.inductiveautomation.com/docs/8.3/platform/gateway/web-interface/network/web-server-settings/secure-communication-ssl-tls](https://www.docs.inductiveautomation.com/docs/8.3/platform/gateway/web-interface/network/web-server-settings/secure-communication-ssl-tls)

or update this guide:

[https://inductiveautomation.com/resources/article/lets-encrypt-guide-for-ignition](https://inductiveautomation.com/resources/article/lets-encrypt-guide-for-ignition)

I would still be trying to figure this out if it wasn’t for your post.