langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Plugin Signature Verification Failed When Installing Custom Plugin in Dify #8878

New Issue
Closed
opened 2026-02-21 18:28:19 -05:00 by yindo · 16 comments
yindo commented 2026-02-21 18:28:19 -05:00
Owner
Copy Link
Copy Source

Originally created by @jaguarliuu on GitHub (Mar 2, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When attempting to install a custom plugin from my private Git repository in Dify, I encountered the following error:

{
    "code": "invalid_param",
    "message": "PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature",
    "status": 400
}

plugin repo: https://github.com/Eumenides1/rookie-weather

How can I resolve this issue?

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @jaguarliuu on GitHub (Mar 2, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.0.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When attempting to install a custom plugin from my private Git repository in Dify, I encountered the following error: ```json { "code": "invalid_param", "message": "PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature", "status": 400 } ``` plugin repo: https://github.com/Eumenides1/rookie-weather How can I resolve this issue? ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bugstale labels 2026-02-21 18:28:19 -05:00
yindo closed this issue 2026-02-21 18:28:19 -05:00
yindo commented 2026-02-21 18:28:19 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 2, 2025):

To resolve the "PluginDaemonBadRequestError" due to a bad plugin signature when installing a custom plugin from your private Git repository in Dify, you can try the following steps:

  1. Modify the Author Field: Ensure that the author field in both the manifest.yaml file in the plugin project and the .yaml file under the /provider path is set to your GitHub ID. This is crucial for the plugin's unique identifier to be valid.

  2. Retype the Plugin Packaging Command: After making the changes, retype the plugin packaging command to create a new plugin package.

  3. Install the New Plugin Package: Use the newly created plugin package for installation.

Additionally, if you still encounter issues, you can add the following line to the end of your .env configuration file to disable signature verification:

FORCE_VERIFYING_SIGNATURE=false

This will allow you to install plugins that are not listed on the Dify Marketplace. However, be aware that this may pose security risks, so it is recommended to first test the plugin in a sandbox environment before deploying it to a production environment [1][2].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 2, 2025): <!-- Answer --> To resolve the "PluginDaemonBadRequestError" due to a bad plugin signature when installing a custom plugin from your private Git repository in Dify, you can try the following steps: 1. **Modify the Author Field**: Ensure that the `author` field in both the `manifest.yaml` file in the plugin project and the `.yaml` file under the `/provider` path is set to your GitHub ID. This is crucial for the plugin's unique identifier to be valid. 2. **Retype the Plugin Packaging Command**: After making the changes, retype the plugin packaging command to create a new plugin package. 3. **Install the New Plugin Package**: Use the newly created plugin package for installation. Additionally, if you still encounter issues, you can add the following line to the end of your `.env` configuration file to disable signature verification: ```plaintext FORCE_VERIFYING_SIGNATURE=false ``` This will allow you to install plugins that are not listed on the Dify Marketplace. However, be aware that this may pose security risks, so it is recommended to first test the plugin in a sandbox environment before deploying it to a production environment <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/learn-more/faq/plugins.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/plugins/faq.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/46bd66dc-f26e-4c51-bebb-aaac01978522?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/46bd66dc-f26e-4c51-bebb-aaac01978522?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/46bd66dc-f26e-4c51-bebb-aaac01978522?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/46bd66dc-f26e-4c51-bebb-aaac01978522?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/46bd66dc-f26e-4c51-bebb-aaac01978522?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/46bd66dc-f26e-4c51-bebb-aaac01978522?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/46bd66dc-f26e-4c51-bebb-aaac01978522?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:20 -05:00
Author
Owner
Copy Link
Copy Source

@jaguarliuu commented on GitHub (Mar 2, 2025):

modify github id fix signature bug, but plugin new release has new error

{
    "code": "invalid_param",
    "message": "PluginDaemonBadRequestError: plugin_unique_identifier is not valid",
    "status": 400
}

how can I fix

@jaguarliuu commented on GitHub (Mar 2, 2025): modify github id fix signature bug, but plugin new release has new error ``` { "code": "invalid_param", "message": "PluginDaemonBadRequestError: plugin_unique_identifier is not valid", "status": 400 } ``` how can I fix
yindo commented 2026-02-21 18:28:20 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 2, 2025):

To fix the "PluginDaemonBadRequestError: plugin_unique_identifier is not valid" error, modify the author field in both the manifest.yaml file in the plugin project and the .yaml file under the /provider path to your GitHub ID. Then, retype the plugin packaging command and install the new plugin package [1].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 2, 2025): <!-- Answer --> To fix the "PluginDaemonBadRequestError: plugin_unique_identifier is not valid" error, modify the `author` field in both the `manifest.yaml` file in the plugin project and the `.yaml` file under the `/provider` path to your GitHub ID. Then, retype the plugin packaging command and install the new plugin package <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/plugins/faq.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/4594f0f9-30f8-4cd2-99ff-6119a9f95806?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/4594f0f9-30f8-4cd2-99ff-6119a9f95806?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/4594f0f9-30f8-4cd2-99ff-6119a9f95806?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/4594f0f9-30f8-4cd2-99ff-6119a9f95806?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4594f0f9-30f8-4cd2-99ff-6119a9f95806?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/4594f0f9-30f8-4cd2-99ff-6119a9f95806?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4594f0f9-30f8-4cd2-99ff-6119a9f95806?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:20 -05:00
Author
Owner
Copy Link
Copy Source

@jaguarliuu commented on GitHub (Mar 2, 2025):

for modify github username to github id，new error
{
"code": "invalid_param",
"message": "PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature",
"status": 400
}
how to fix

@jaguarliuu commented on GitHub (Mar 2, 2025): for modify github username to github id，new error { "code": "invalid_param", "message": "PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature", "status": 400 } how to fix
yindo commented 2026-02-21 18:28:20 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 2, 2025):

To fix the "PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature" error after modifying the GitHub username to GitHub ID, you can add the following line to the end of your .env configuration file:

FORCE_VERIFYING_SIGNATURE=false

This will disable the signature verification, allowing you to install plugins that are not verified on the Dify Marketplace. However, be cautious as this may pose security risks. It is recommended to use this setting in a test or sandbox environment first before deploying to production [1][2].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 2, 2025): <!-- Answer --> To fix the "PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature" error after modifying the GitHub username to GitHub ID, you can add the following line to the end of your `.env` configuration file: ```plaintext FORCE_VERIFYING_SIGNATURE=false ``` This will disable the signature verification, allowing you to install plugins that are not verified on the Dify Marketplace. However, be cautious as this may pose security risks. It is recommended to use this setting in a test or sandbox environment first before deploying to production <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/learn-more/faq/plugins.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/learn-more/faq/plugins.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:20 -05:00
Author
Owner
Copy Link
Copy Source

@jaguarliuu commented on GitHub (Mar 3, 2025):

After adding FORCE_VERIFYING_SIGNATURE=false to the Dify configuration, the issue was resolved. However, if others use my plugin, they will still encounter the same problem, which is not fundamentally resolved. What is the root cause of the problem?

@jaguarliuu commented on GitHub (Mar 3, 2025): After adding FORCE_VERIFYING_SIGNATURE=false to the Dify configuration, the issue was resolved. However, if others use my plugin, they will still encounter the same problem, which is not fundamentally resolved. What is the root cause of the problem?
yindo commented 2026-02-21 18:28:20 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 3, 2025):

The root cause of the "PluginDaemonBadRequestError" related to plugin signature verification is that the plugin you want to install has a bad signature, and plugin verification has been enabled. This issue arises because the signature of the plugin does not match the expected signature, which is calculated using specific data and a secret key.

To resolve this issue fundamentally, you need to ensure that the plugin is properly signed with a valid signature. This involves using the correct secret key and ensuring that all the data used in the signature calculation (such as filename, mimetype, tenant_id, user_id, timestamp, and nonce) is accurate and consistent with what is expected by the verification process.

If you want others to use your plugin without encountering this issue, you should distribute the plugin with a valid signature that can be verified by others. This means ensuring that the signature is correctly generated and matches the expected criteria used by Dify's verification process [1].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 3, 2025): <!-- Answer --> The root cause of the "PluginDaemonBadRequestError" related to plugin signature verification is that the plugin you want to install has a bad signature, and plugin verification has been enabled. This issue arises because the signature of the plugin does not match the expected signature, which is calculated using specific data and a secret key. To resolve this issue fundamentally, you need to ensure that the plugin is properly signed with a valid signature. This involves using the correct secret key and ensuring that all the data used in the signature calculation (such as filename, mimetype, tenant_id, user_id, timestamp, and nonce) is accurate and consistent with what is expected by the verification process. If you want others to use your plugin without encountering this issue, you should distribute the plugin with a valid signature that can be verified by others. This means ensuring that the signature is correctly generated and matches the expected criteria used by Dify's verification process <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/learn-more/faq/plugins.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/38fecf31-4705-4e3f-a20f-1eb451ed5084?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/38fecf31-4705-4e3f-a20f-1eb451ed5084?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/38fecf31-4705-4e3f-a20f-1eb451ed5084?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/38fecf31-4705-4e3f-a20f-1eb451ed5084?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/38fecf31-4705-4e3f-a20f-1eb451ed5084?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/38fecf31-4705-4e3f-a20f-1eb451ed5084?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/38fecf31-4705-4e3f-a20f-1eb451ed5084?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:20 -05:00
Author
Owner
Copy Link
Copy Source

@jaguarliuu commented on GitHub (Mar 3, 2025):

https://github.com/langgenius/dify-docs/blob/main/zh_CN/plugins/publish-plugins/broken-reference package plugin doc 404；I don't know Which parameters affect the generation of signatures, and which configurations need to be modified and verified to resolve the issue permanently?

@jaguarliuu commented on GitHub (Mar 3, 2025): https://github.com/langgenius/dify-docs/blob/main/zh_CN/plugins/publish-plugins/broken-reference package plugin doc 404；I don't know Which parameters affect the generation of signatures, and which configurations need to be modified and verified to resolve the issue permanently?
yindo commented 2026-02-21 18:28:21 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 3, 2025):

The parameters that affect the generation of plugin signatures in Dify are related to the PLUGIN_DAEMON_KEY and FORCE_VERIFYING_SIGNATURE. To resolve the signature verification issue permanently, ensure that the PLUGIN_DAEMON_KEY is correctly configured and consistent across all relevant components. Additionally, verify that FORCE_VERIFYING_SIGNATURE is set to the desired value (true or false) based on whether you want to enforce signature verification.

Here are the relevant configurations:

PLUGIN_DAEMON_KEY: ${PLUGIN_DAEMON_KEY:-lYkiYYT6owG+71oLerGzA7GXCgOT++6ovaezWAjpCjf+Sjc3ZtU+qUEi}
FORCE_VERIFYING_SIGNATURE: ${FORCE_VERIFYING_SIGNATURE:-true}

Make sure these configurations are correctly set in your docker/docker-compose.yaml file and any other configuration files that might override these settings [1].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 3, 2025): <!-- Answer --> The parameters that affect the generation of plugin signatures in Dify are related to the `PLUGIN_DAEMON_KEY` and `FORCE_VERIFYING_SIGNATURE`. To resolve the signature verification issue permanently, ensure that the `PLUGIN_DAEMON_KEY` is correctly configured and consistent across all relevant components. Additionally, verify that `FORCE_VERIFYING_SIGNATURE` is set to the desired value (`true` or `false`) based on whether you want to enforce signature verification. Here are the relevant configurations: ```yaml PLUGIN_DAEMON_KEY: ${PLUGIN_DAEMON_KEY:-lYkiYYT6owG+71oLerGzA7GXCgOT++6ovaezWAjpCjf+Sjc3ZtU+qUEi} FORCE_VERIFYING_SIGNATURE: ${FORCE_VERIFYING_SIGNATURE:-true} ``` Make sure these configurations are correctly set in your `docker/docker-compose.yaml` file and any other configuration files that might override these settings <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/934176a7-309e-412c-8b77-3d1af3723627?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/934176a7-309e-412c-8b77-3d1af3723627?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/934176a7-309e-412c-8b77-3d1af3723627?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/934176a7-309e-412c-8b77-3d1af3723627?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/934176a7-309e-412c-8b77-3d1af3723627?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/934176a7-309e-412c-8b77-3d1af3723627?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/934176a7-309e-412c-8b77-3d1af3723627?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:21 -05:00
Author
Owner
Copy Link
Copy Source

@jaguarliuu commented on GitHub (Mar 3, 2025):

I can't find what is PLUGIN_DAEMON_KEY ，how to get it

@jaguarliuu commented on GitHub (Mar 3, 2025): I can't find what is PLUGIN_DAEMON_KEY ，how to get it
yindo commented 2026-02-21 18:28:21 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 3, 2025):

To find or obtain the PLUGIN_DAEMON_KEY for Dify, you can refer to the docker/docker-compose.yaml file. The key is set with a default value as follows:

PLUGIN_DAEMON_KEY: ${PLUGIN_DAEMON_KEY:-lYkiYYT6owG+71oLerGzA7GXCgOT++6ovaezWAjpCjf+Sjc3ZtU+qUEi}

This means that if the PLUGIN_DAEMON_KEY environment variable is not set, it will default to lYkiYYT6owG+71oLerGzA7GXCgOT++6ovaezWAjpCjf+Sjc3ZtU+qUEi. You can use this default value or set your own by defining the PLUGIN_DAEMON_KEY environment variable [1].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 3, 2025): <!-- Answer --> To find or obtain the `PLUGIN_DAEMON_KEY` for Dify, you can refer to the `docker/docker-compose.yaml` file. The key is set with a default value as follows: ```yaml PLUGIN_DAEMON_KEY: ${PLUGIN_DAEMON_KEY:-lYkiYYT6owG+71oLerGzA7GXCgOT++6ovaezWAjpCjf+Sjc3ZtU+qUEi} ``` This means that if the `PLUGIN_DAEMON_KEY` environment variable is not set, it will default to `lYkiYYT6owG+71oLerGzA7GXCgOT++6ovaezWAjpCjf+Sjc3ZtU+qUEi`. You can use this default value or set your own by defining the `PLUGIN_DAEMON_KEY` environment variable <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/446193d3-2b7d-43d1-b1cd-637861982b31?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/446193d3-2b7d-43d1-b1cd-637861982b31?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/446193d3-2b7d-43d1-b1cd-637861982b31?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/446193d3-2b7d-43d1-b1cd-637861982b31?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/446193d3-2b7d-43d1-b1cd-637861982b31?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/446193d3-2b7d-43d1-b1cd-637861982b31?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/446193d3-2b7d-43d1-b1cd-637861982b31?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:21 -05:00
Author
Owner
Copy Link
Copy Source

@jaguarliuu commented on GitHub (Mar 3, 2025):

I want to know， github id is a number or github username？ if is a number how can i get it

@jaguarliuu commented on GitHub (Mar 3, 2025): I want to know， github id is a number or github username？ if is a number how can i get it
yindo commented 2026-02-21 18:28:21 -05:00
Author
Owner
Copy Link
Copy Source

@junjiem commented on GitHub (Mar 3, 2025):

@jaguarliuu https://docs.dify.ai/zh-hans/learn-more/faq/plugins

@junjiem commented on GitHub (Mar 3, 2025): @jaguarliuu https://docs.dify.ai/zh-hans/learn-more/faq/plugins
yindo commented 2026-02-21 18:28:21 -05:00
Author
Owner
Copy Link
Copy Source

@shaojun commented on GitHub (Mar 19, 2025):

To fix the "PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature" error after modifying the GitHub username to GitHub ID, you can add the following line to the end of your .env configuration file:

FORCE_VERIFYING_SIGNATURE=false

This will disable the signature verification, allowing you to install plugins that are not verified on the Dify Marketplace. However, be cautious as this may pose security risks. It is recommended to use this setting in a test or sandbox environment first before deploying to production [1][2].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

i assume the .env is the file under dify/docker/.env, correct? not the one in tools folder.
I'm using local develop and build .difypkg via CLI.
and i noticed the .env already has a line with that key, so i just updated it to false:

Image

then I did a docker compose restart, but still seeing this error:

Upload failed

PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature

Image

@shaojun commented on GitHub (Mar 19, 2025): > To fix the "PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature" error after modifying the GitHub username to GitHub ID, you can add the following line to the end of your `.env` configuration file: > > ``` > FORCE_VERIFYING_SIGNATURE=false > ``` > > This will disable the signature verification, allowing you to install plugins that are not verified on the Dify Marketplace. However, be cautious as this may pose security risks. It is recommended to use this setting in a test or sandbox environment first before deploying to production [[1]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/learn-more/faq/plugins.md)[[2]](https://github.com/langgenius/dify-docs/blob/main/en/learn-more/faq/plugins.md). > > _To continue talking to [Dosu](https://dosu.dev), mention [@dosu](https://github.com/dosu)._ > > Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=other) i assume the `.env` is the file under `dify/docker/.env`, correct? not the one in tools folder. I'm using **local develop and build** `.difypkg` via `CLI`. and i noticed the `.env` already has a line with that key, so i just updated it to `false`: ![Image](https://github.com/user-attachments/assets/5837c617-3d09-4f15-82a3-cb6d223b0176) then I did a `docker compose restart`, but still seeing this error: ``` Upload failed PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature ``` ![Image](https://github.com/user-attachments/assets/717a8b8a-0fe3-4481-8766-ff65b820c500)
yindo commented 2026-02-21 18:28:21 -05:00
Author
Owner
Copy Link
Copy Source

@shaojun commented on GitHub (Mar 19, 2025):

To fix the "PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature" error after modifying the GitHub username to GitHub ID, you can add the following line to the end of your .env configuration file:

FORCE_VERIFYING_SIGNATURE=false

This will disable the signature verification, allowing you to install plugins that are not verified on the Dify Marketplace. However, be cautious as this may pose security risks. It is recommended to use this setting in a test or sandbox environment first before deploying to production [1][2].
To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

i assume the .env is the file under dify/docker/.env, correct? not the one in tools folder. I'm using local develop and build .difypkg via CLI. and i noticed the .env already has a line with that key, so i just updated it to false:

Image

then I did a docker compose restart, but still seeing this error:

Upload failed

PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature

Image

figured it out, should using below to reload the .env file rather than docker compose restart:

docker compose down
docker compose up -d
@shaojun commented on GitHub (Mar 19, 2025): > > To fix the "PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature" error after modifying the GitHub username to GitHub ID, you can add the following line to the end of your `.env` configuration file: > > ``` > > FORCE_VERIFYING_SIGNATURE=false > > ``` > > > > > > > > > > > > > > > > > > > > > > > > This will disable the signature verification, allowing you to install plugins that are not verified on the Dify Marketplace. However, be cautious as this may pose security risks. It is recommended to use this setting in a test or sandbox environment first before deploying to production [[1]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/learn-more/faq/plugins.md)[[2]](https://github.com/langgenius/dify-docs/blob/main/en/learn-more/faq/plugins.md). > > _To continue talking to [Dosu](https://dosu.dev), mention [@dosu](https://github.com/dosu)._ > > Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/717fe1e9-ccdf-4e72-bcf1-f52bbbb23b97?feedback_type=other) > > i assume the `.env` is the file under `dify/docker/.env`, correct? not the one in tools folder. I'm using **local develop and build** `.difypkg` via `CLI`. and i noticed the `.env` already has a line with that key, so i just updated it to `false`: > > ![Image](https://github.com/user-attachments/assets/5837c617-3d09-4f15-82a3-cb6d223b0176) > > then I did a `docker compose restart`, but still seeing this error: > > ``` > Upload failed > > PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature > ``` > > ![Image](https://github.com/user-attachments/assets/717a8b8a-0fe3-4481-8766-ff65b820c500) figured it out, should using below to reload the `.env` file rather than `docker compose restart`: ``` docker compose down docker compose up -d ```
yindo commented 2026-02-21 18:28:21 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 19, 2025):

Hi, @jaguarliuu. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • You faced a "PluginDaemonBadRequestError" when installing a custom plugin due to signature verification issues.
  • Attempts to modify the GitHub ID and disable signature verification were not ideal for broader use.
  • I suggested modifying the author field and disabling signature verification.
  • Shaojun confirmed that using docker compose down and docker compose up -d successfully reloaded the .env file, resolving the issue.

Next Steps:

  • Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here.
  • If no updates are provided, the issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Apr 19, 2025): Hi, @jaguarliuu. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - You faced a "PluginDaemonBadRequestError" when installing a custom plugin due to signature verification issues. - Attempts to modify the GitHub ID and disable signature verification were not ideal for broader use. - I suggested modifying the `author` field and disabling signature verification. - Shaojun confirmed that using `docker compose down` and `docker compose up -d` successfully reloaded the `.env` file, resolving the issue. **Next Steps:** - Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here. - If no updates are provided, the issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label stale 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#8878
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?