# Signing upgraded modules for 8.3

**URL:** <https://forum.inductiveautomation.com/t/signing-upgraded-modules-for-8-3/110831>\
**Category:** Module Development\
**Tags:** ignition83\
**Created:** [September 22, 2025, 3:07pm UTC](https://forum.inductiveautomation.com/t/signing-upgraded-modules-for-8-3/110831 "2025-09-22T15:07:26Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![james.vosler](https://avatars.discourse-cdn.com/v4/letter/j/8797f3/32.png) [@james.vosler](https://forum.inductiveautomation.com/u/james.vosler)\
**Post date:** [September 22, 2025, 3:07pm UTC](https://forum.inductiveautomation.com/t/signing-upgraded-modules-for-8-3/110831/1 "2025-09-22T15:07:26Z")

</div>

Has anything changed for signing modules for 8.3?

I signed an upgraded module with the same tools that work for 8.1, but uploading the module has issues:

1. Ignition standard 8.3.0 (b2025091510)
2. modl contains certificates.p7b
3. Module is signed, but not found?
4. If accepted, module gets quarantined as unsigned  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/7/37ccc12f43d227d48634efa17b644141b7e35dd0.png)

---

<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:** [September 22, 2025, 3:20pm UTC](https://forum.inductiveautomation.com/t/signing-upgraded-modules-for-8-3/110831/2 "2025-09-22T15:20:49Z")

</div>

Not intentionally, can you share the module so we can take a look?

---

<div class="post-metadata">

**Author:** ![james.vosler](https://avatars.discourse-cdn.com/v4/letter/j/8797f3/32.png) [@james.vosler](https://forum.inductiveautomation.com/u/james.vosler)\
**Post date:** [September 22, 2025, 5:01pm UTC](https://forum.inductiveautomation.com/t/signing-upgraded-modules-for-8-3/110831/3 "2025-09-22T17:01:53Z")

</div>

The next reboot prompted to accept the certificate and the module loaded. So, there was something about the module import process that prevented or did not allow the certificate to be accepted. Chicken and egg issue perhaps.

Side note: the gateway the module is loaded on is in some sort of extreme resource constraint on cpu. To the point that loading a designer will sometimes timeout, and even restarting the gateway can timeout. We are working to resolve this before drawing any additional conclusions on the module’s behavior.

For sure - I can share the module if it would be helpful.

---

<div class="post-metadata">

**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\
**Post date:** [September 22, 2025, 8:20pm UTC](https://forum.inductiveautomation.com/t/signing-upgraded-modules-for-8-3/110831/4 "2025-09-22T20:20:25Z")

</div>

Did you have the unsigned version of the module installed already? This has happened to me, before in that situation, just uninstall the unsigned one, restart and install the signed one.

---

<div class="post-metadata">

**Author:** ![james.vosler](https://avatars.discourse-cdn.com/v4/letter/j/8797f3/32.png) [@james.vosler](https://forum.inductiveautomation.com/u/james.vosler)\
**Post date:** [September 22, 2025, 8:41pm UTC](https://forum.inductiveautomation.com/t/signing-upgraded-modules-for-8-3/110831/5 "2025-09-22T20:41:31Z")

</div>

I had attempted the unsigned install, but I had not enabled debug mode, so it would not install that way. Perhaps it got far enough to cause the issue.

---

<div class="post-metadata">

**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\
**Post date:** [September 22, 2025, 9:09pm UTC](https://forum.inductiveautomation.com/t/signing-upgraded-modules-for-8-3/110831/6 "2025-09-22T21:09:07Z")

</div>

That will definitely cause the issue, for some reason it does all the certificate stuff before checking the signed or unsigned check. A reboot normally fixes this from memory.  
I think there is still work being done on IAs side with this mechanism.

---

<div class="post-metadata">

**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\
**Post date:** [September 22, 2025, 9:19pm UTC](https://forum.inductiveautomation.com/t/signing-upgraded-modules-for-8-3/110831/7 "2025-09-22T21:19:52Z")

</div>

@Kevin.Herron Do you know if this behaviour is in an existing ticket in your system?

---

<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:** [September 22, 2025, 9:22pm UTC](https://forum.inductiveautomation.com/t/signing-upgraded-modules-for-8-3/110831/8 "2025-09-22T21:22:21Z")

</div>

Can't find it, but may not be searching the right terms.

What's the repro steps here? Install the unsigned version of a module without `-Dignition.allowunsignedmodules=true`, then follow up with a signed version and you get a blank dialog like this? Something else?

---

<div class="post-metadata">

**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\
**Post date:** [September 22, 2025, 9:25pm UTC](https://forum.inductiveautomation.com/t/signing-upgraded-modules-for-8-3/110831/9 "2025-09-22T21:25:55Z")

</div>

Yes, and also I believe if you have the unsigned module installed already and try installing the signed module, it will do the same dialog.

---

<div class="post-metadata">

**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:** [September 22, 2025, 9:27pm UTC](https://forum.inductiveautomation.com/t/signing-upgraded-modules-for-8-3/110831/10 "2025-09-22T21:27:16Z")

</div>

Different module file names? If so, maybe this:

> [@Install or Upgrade Module not working](https://forum.inductiveautomation.com/t/install-or-upgrade-module-not-working/110443/3):
>
> Huh... anybody from IA acknowledged this yet or should I make a ticket?
