# Cannot load custom plugin

**URL:** <https://community.grafana.com/t/cannot-load-custom-plugin/63031>\
**Category:** Grafana Plugin Development\
**Created:** [March 28, 2022, 8:32am UTC](https://community.grafana.com/t/cannot-load-custom-plugin/63031 "2022-03-28T08:32:00Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![ryanscar9](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@ryanscar9](https://community.grafana.com/u/ryanscar9)\
**Post date:** [March 28, 2022, 8:32am UTC](https://community.grafana.com/t/cannot-load-custom-plugin/63031/1 "2022-03-28T08:32:00Z")

</div>

I’m running grafana with docker, and I tried to follow this build a [panel plugin tutorial](https://grafana.com/tutorials/build-a-panel-plugin)  
However, **I can’t see my custom plugin on Grafana**.

This is what my logs say:  
msg=“Skipping loading plugin due to problem with signature”

Do the errors say something about signed/unsigned plugins? I know that if a plugin is unsigned, then Grafana does not load nor start it. So if that’s the case, should I sign my custom plugin first to work?

Or do I have to add GF\_PLUGINS\_ALLOW\_LOADING\_UNSIGNED\_PLUGINS=“my-plugin” in the docker run command?

---

<div class="post-metadata">

**Author:** ![marcusolsson](https://sea2.discourse-cdn.com/grafana/user_avatar/community.grafana.com/marcusolsson/32/7922_2.png) [@marcusolsson](https://community.grafana.com/u/marcusolsson)\
**Post date:** [March 31, 2022, 8:28am UTC](https://community.grafana.com/t/cannot-load-custom-plugin/63031/2 "2022-03-31T08:28:01Z")

</div>

Hi Ryan,

Have you tried setting the app mode to development? That will load all unsigned plugins. `GF_PLUGINS_ALLOW_LOADING_UNSIGNED_PLUGINS` should work too, but is typically better for when you want to allow a specific unsigned plugin in a production environment.

> [@Local plugin doesn't load](https://community.grafana.com/t/local-plugin-doesnt-load/62127):
>
> I have grafana 8.4.3 installed, node 16.13.2 and yarn 1.22.17 Following instructions from [Build a panel plugin | Grafana Labs](https://grafana.com/tutorials/build-a-panel-plugin/) In /var/lib/grafana/plugins folder I’ve used command npx @grafana/toolkit plugin:create test-plugin. I entered the folder test-plugin and ran yarn install and yarn dev with no issues. After that i restarted grafana with service grafana-server restart. The problem is i still don’t see my plugin listed in http://127.0.0.1:3000/plugins. The issue is that i had no proble…

---

<div class="post-metadata">

**Author:** ![raakasf](https://sea2.discourse-cdn.com/grafana/user_avatar/community.grafana.com/raakasf/32/19056_2.png) [@raakasf](https://community.grafana.com/u/raakasf)\
**Post date:** [May 9, 2022, 9:53pm UTC](https://community.grafana.com/t/cannot-load-custom-plugin/63031/3 "2022-05-09T21:53:27Z")

</div>

Hello @marcusolsson,

I am facing some issues related to datasource plugin development too in addition to the above, namely:

1. console.log in the plugin code doesn’t print out on Firefox or CDT
2. Variables are “not available” when you place a breakpoint and do a watch on them

Could you please tell me how to set the app mode to development?

---

<div class="post-metadata">

**Author:** ![raakasf](https://sea2.discourse-cdn.com/grafana/user_avatar/community.grafana.com/raakasf/32/19056_2.png) [@raakasf](https://community.grafana.com/u/raakasf)\
**Post date:** [May 24, 2022, 2:47pm UTC](https://community.grafana.com/t/cannot-load-custom-plugin/63031/4 "2022-05-24T14:47:58Z")

</div>

For me the following worked:

1. Set in the following in environment variable in Grafana container and restart the container

> GF\_DEFAULT\_APP\_MODE=development

1. Build the react plugin with the following option and reload the plugin if you are switching mode from prod to dev. You don’t need to reload after this.

> yarn dev

---

<div class="post-metadata">

**Author:** ![aramosvizcarra](https://avatars.discourse-cdn.com/v4/letter/a/ea666f/32.png) [@aramosvizcarra](https://community.grafana.com/u/aramosvizcarra)\
**Post date:** [November 8, 2022, 3:32pm UTC](https://community.grafana.com/t/cannot-load-custom-plugin/63031/5 "2022-11-08T15:32:22Z")

</div>

> [@ryanscar9](#):
>
> GF\_PLUGINS\_ALLOW\_LOADING\_UNSIGNED\_PLUGINS=“my-plugin”

This didn’t fix it for me I need to add GF\_PLUGINS\_ALLOW\_LOADING\_UNSIGNED\_PLUGINS=“my-plugin” otherwise Grafana won’t allow unsigned plugins to be installed

---

<div class="post-metadata">

**Author:** ![academo](https://avatars.discourse-cdn.com/v4/letter/a/e9a140/32.png) [@academo](https://community.grafana.com/u/academo)\
**Post date:** [November 8, 2022, 6:16pm UTC](https://community.grafana.com/t/cannot-load-custom-plugin/63031/6 "2022-11-08T18:16:43Z")

</div>

Grafana will only load unsigned plugins if in development mode. See previous comments on how to set grafana in development mode.

---

<div class="post-metadata">

**Author:** ![aramosvizcarra](https://avatars.discourse-cdn.com/v4/letter/a/ea666f/32.png) [@aramosvizcarra](https://community.grafana.com/u/aramosvizcarra)\
**Post date:** [November 8, 2022, 6:27pm UTC](https://community.grafana.com/t/cannot-load-custom-plugin/63031/7 "2022-11-08T18:27:57Z")

</div>

You are right, I added the ENV variable in the wrong place in my docker file.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/grafana/original/2X/e/ef5308cc58c9e5a13187b5012eb99f406928462f.png) [@system](https://community.grafana.com/u/system)\
**Post date:** [November 8, 2023, 6:28pm UTC](https://community.grafana.com/t/cannot-load-custom-plugin/63031/8 "2023-11-08T18:28:30Z")

</div>

Closed on November 8, 2023, 6:28pm UTC

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
