-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin disabled due to modified content #304
Comments
+1 to this, getting the same issue. If installed via cli grafana won't even start |
Same issue here. I have it installed on a Windows machine as well. |
Quick fix for this is to install 3.2.0 instead. If you are using the grafana cli you can add a version as the last arguement for the install command. |
Hello! Thank you for reporting this. Can you share your Grafana logs when restarting Grafana and seeing the plugin disabled? |
Hello, I reproduce it again with version 3.3.0 (I did not tried to do it with version 3.2.0 though) I attach you the log As you can see at 13:22 I installed the plugin via web. You can see that at 13:27 grafana-image-renderer has a modified signature so the plugin does not start. Something that it is also noticiable is that if you download the zip File via grafana Api you get a folder named plugin-win32-x64-unknown that is something that is weird for me. I download all the plugins via this script(It is a Powershell file but you can see the logic inside) |
@AgnesToulet info already added |
Thanks for the logs! This is the same issue as #260 and it's fixed in Grafana 9.4.0 (grafana/grafana#59104). |
What happened:
We installed last Grafana (8.2.2) version in a Windows Server and we installed this plugin using admin/plugins.
We observed that when we stop the Windows Grafana Service sometimes we find this message
What you expected to happen:
To do not have problems when restarting grafana service
How to reproduce it (as minimally and precisely as possible):
Have a Grafana service in a Windows machine with this plugin installed. Restart the service several times.
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: