Plugin Signature Verification Failed During Installation (PluginDaemonBadRequestError: bad signature) #11440

Closed
opened 2026-02-21 18:59:43 -05:00 by yindo · 0 comments
Owner

Originally created by @jaguarliuu on GitHub (Mar 17, 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 my locally developed Dify plugin (rookie_text2data) via the Dify platform, I encounter the following error:

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

I have followed the official documentation to configure digital signatures, but the installation still fails. Disabling signature verification is not a viable solution for production use.

  1. What specific configurations are required for Dify to accept a custom plugin signature?
  2. How can I validate my signature file is correctly formatted?
  3. Are there any known issues with self-signed certificates in Dify's verification process?
  4. Is there a debug mode or verbose logging I can enable to trace the signature validation step?

Plugin source code: jaguarliuu/rookie_text2data

✔️ Expected Behavior

No response

Actual Behavior

No response

Originally created by @jaguarliuu on GitHub (Mar 17, 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 my locally developed Dify plugin (rookie_text2data) via the Dify platform, I encounter the following error: ``` PluginDaemonBadRequestError: plugin verification has been enabled, and the plugin you want to install has a bad signature ``` I have followed the official documentation to configure digital signatures, but the installation still fails. Disabling signature verification is not a viable solution for production use. 1. What specific configurations are required for Dify to accept a custom plugin signature? 2. How can I validate my signature file is correctly formatted? 3. Are there any known issues with self-signed certificates in Dify's verification process? 4. Is there a debug mode or verbose logging I can enable to trace the signature validation step? Plugin source code: jaguarliuu/rookie_text2data ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 18:59:43 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#11440