# Module code signing issue after cert update

**URL:** <https://forum.inductiveautomation.com/t/module-code-signing-issue-after-cert-update/116949>\
**Category:** Ignition\
**Tags:** ignition83\
**Created:** [August 31, 2026, 5:33pm UTC](https://forum.inductiveautomation.com/t/module-code-signing-issue-after-cert-update/116949 "2026-08-31T17:33:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Serghei\_Luchianov](https://avatars.discourse-cdn.com/v4/letter/s/e47774/32.png) [@Serghei\_Luchianov](https://forum.inductiveautomation.com/u/Serghei_Luchianov)\
**Post date:** [August 31, 2026, 5:33pm UTC](https://forum.inductiveautomation.com/t/module-code-signing-issue-after-cert-update/116949/1 "2026-08-31T17:33:39Z")

</div>

Hi, we have updated our code signing certificate and now the module installs fine from fresh:

 ![Screenshot 2026-08-31 112058](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/8/58683660a0639a9ba0e174ea7b94ca4e834b4be7.png)

But fails to install when updating from the module signed by the certificate that's now expired with the error seen below:

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

And for some reason, when updating the module, certificate information seen on the screen shows the expired cert info, not the new one.

What is the expected behavior here? Are we looking at a bug?

Edit:  
This is Ignition 8.3.8

---

<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:** [August 31, 2026, 6:15pm UTC](https://forum.inductiveautomation.com/t/module-code-signing-issue-after-cert-update/116949/2 "2026-08-31T18:15:29Z")

</div>

Hmm, sounds like the same thing discussed here: [Error message when upgrading module with same certificate - Ignition 8.3 - #3 by bmusson](https://forum.inductiveautomation.com/t/error-message-when-upgrading-module-with-same-certificate-ignition-8-3/116603/3)

---

<div class="post-metadata">

**Author:** ![Serghei\_Luchianov](https://avatars.discourse-cdn.com/v4/letter/s/e47774/32.png) [@Serghei\_Luchianov](https://forum.inductiveautomation.com/u/Serghei_Luchianov)\
**Post date:** [August 31, 2026, 6:35pm UTC](https://forum.inductiveautomation.com/t/module-code-signing-issue-after-cert-update/116949/3 "2026-08-31T18:35:49Z")

</div>

The reason we're bringing this up is because the issue doesn't replicate on Ignition 8.1.54 - the module upgrades properly there.

---

<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:** [August 31, 2026, 6:40pm UTC](https://forum.inductiveautomation.com/t/module-code-signing-issue-after-cert-update/116949/4 "2026-08-31T18:40:20Z")

</div>

That's not very surprising, the module system is very different in 8.3.

That other thread has a workaround (uninstall the module first). I'll create a ticket to track this.

---

<div class="post-metadata">

**Author:** ![Serghei\_Luchianov](https://avatars.discourse-cdn.com/v4/letter/s/e47774/32.png) [@Serghei\_Luchianov](https://forum.inductiveautomation.com/u/Serghei_Luchianov)\
**Post date:** [August 31, 2026, 6:51pm UTC](https://forum.inductiveautomation.com/t/module-code-signing-issue-after-cert-update/116949/5 "2026-08-31T18:51:01Z")

</div>

Appreciate it! We already figured out the workaround, this is for our customers who will be upgrading modules going forward.