Hi everyone, I think I have encountered a bug in 8.3.8 related to upgrading of my module which shares a certificate with older versions of the module.
When I install/upgrade the module I correctly get the module acceptance prompt:
however accepting the certificate results in the following error:

This fails to close the accept certificate prompt, and the "Gateway Restart Required" banner is never provided causing me to have to manually restart the gateway. After a restart the module is able to be correctly installed.
While not breaking this is frustrating UX - is this a known issue/is this a result of me incorrectly signing my module?
Hmm. If you can reproduce easily, you should open a support ticket. I've been going through similar upgrades all the time without issue, so it may be something specific to your environment.
I’ve encountered this issue when installing a module that has a different certificate than the previously installed version.
This happens to me pretty regularly because my CI builds use a different cert than my local builds.
You get the popup to accept the cert, but after pressing “Accept Certificate” you get a “Certificate Already Accepted” error, and the module fails to install.
The current solution is to uninstall the existing module, restart, install the new module, restart.
Ah, I think this is almost certainly the cause.
a) because I do a lot of development with unsigned modules and later update to signed modules for build releases
b) recently rolled a new cert after the old one expired