3.12.7, 3.12.8 and 3.12.9 update failed "Plugin validation failed"

[perplexityjeff]

What happened:
Updated the plugin now it fails with error plugin validation failed. Reverted to 3.12.6 which works fine

"Plugin validation failed" pluginId=grafana-image-renderer error="plugin 'grafana-image-renderer' has an modified signature

Environment:

• Grafana Image Renderer version: 3.12.7
• Grafana version: 12.0.2
• Installed plugin or remote renderer service: plugin
• OS Grafana Image Renderer is installed on: Debian
• User OS & Browser: Firefox, Edge

[Proximyst]

@perplexityjeff Thanks for reporting a bug!

I can't reproduce this locally with Grafana Enterprise v12.0.2 and grafana-image-renderer v3.12.6 thru .9.

As the log indicates the validation failed as a file within the plugin was modified, would it be possible for you to rm -rf the image-renderer plugins directory (that should be under plugins/grafana-image-renderer/ directory under wherever you store your Grafana data) and reinstall the plugin? After doing so, is the problem still there?

Linux mariell-arch 6.15.4-arch2-1 #1 SMP PREEMPT_DYNAMIC Fri, 27 Jun 2025 16:35:07 +0000 x86_64 GNU/Linux
Grafana commit: 5bda17e7c1cb313eb96266f2fdda73a6b35c3977 / refs/tags/v12.0.2
Grafana Enterprise commit: e5bbba5b46271d72f3503cbc7e4cb01d825ae3f0 / refs/tags/v12.0.2

[perplexityjeff]

Hi @Proximyst,

Here are the following steps that I have done. I was running 3.12.6 before running these commands to attempt to install 3.12.9 (for example), however any version higher than 3.12.6 does not work for me:

• Uninstallation:

• Directory check to make sure its clean, however the uninstall command already deleted the folder:

• Installation which seems to go fine:

• After which the error logs if I use tail -f grafana.log:

• And if I load up the interface:

• Reverting back to 3.12.6 and it works great:

It seems very much related to the issue #651, we do both seem to run Debian based systems but I do not know if that is something that could be related.

[macabu]

Hey @perplexityjeff, would you be able to follow @Proximyst 's instructions in #651 and enable debug logging ?