Closed ghost closed 2 years ago
@colramos-amd Do you have other plugins installed from local source that are working correctly? If you are allowing unsigned from local, I would start with deleting the MANIFEST.txt from the dist folder. I think you might want to file this as an issue in the grafana repository as well, because it sounds like when grafana detects a plugin that has signing information, it attempts to verify it, despite it being in the allow unsigned list.
@colramos-amd any updates on this? Will close, as no one else seems to be having this issue.
I downloaded a .zip of main branch to run on my own machine on 8/03. Grafana complains that the signature has been modified and is refusing to show the plugin.
As noted in the Grafana docs...
I'm 99% sure this wasn't an issue with my installation. I made sure it's in my Grafana plugins folder, yarn install/dev ran without any problems, and the proj ID is listed in my grafana.ini
allow_loading_unsigned_plugins