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

[ERROR]lisinstalled plugins failed: plugin unique identifier is not valid #12510

New Issue
Closed
opened 2026-02-21 19:07:44 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:07:44 -05:00
Owner
Copy Link
Copy Source

Originally created by @shines18523 on GitHub (Apr 3, 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

dify-1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After the plug-in is installed offline, an error occurs. The plug-in is deleted from the web page, and the volumes/plugin_daemon/plugin and /volumes/plugin_daemon/plugin_packages/langgenius files are deleted from the server. Restart the container and reinstall the plug-in. An error message is displayed in the log

✔️ Expected Behavior

18/5000
How to eliminate this error? Currently the plugin works normally

❌ Actual Behavior

Originally created by @shines18523 on GitHub (Apr 3, 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 dify-1.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce After the plug-in is installed offline, an error occurs. The plug-in is deleted from the web page, and the volumes/plugin_daemon/plugin and /volumes/plugin_daemon/plugin_packages/langgenius files are deleted from the server. Restart the container and reinstall the plug-in. An error message is displayed in the log ### ✔️ Expected Behavior 18/5000 How to eliminate this error? Currently the plugin works normally ### ❌ Actual Behavior
yindo added the 🐞 bug label 2026-02-21 19:07:44 -05:00
yindo closed this issue 2026-02-21 19:07:44 -05:00
yindo commented 2026-02-21 19:07:45 -05:00
Author
Owner
Copy Link
Copy Source

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

I found two similar open issues related to the error "[ERROR] lisinstalled plugins failed: plugin unique identifier is not valid" in the Dify repository, but no solutions were found in the comments [1][2].

To resolve this error in Dify version 1.1.3 on a self-hosted Docker setup, you can try the following steps:

  1. Ensure that the manifest.yaml file and any .yaml files under the /provider path in your plugin project have the author field set to your GitHub ID. This is necessary to validate the plugin's unique identifier.

  2. Add or modify the following line in your docker/.env file:

    FORCE_VERIFYING_SIGNATURE=false

  3. Restart Docker services using these commands:

    cd docker
docker compose down
docker compose up -d

These steps should help eliminate the error by ensuring the environment variables are properly reloaded and the plugin's unique identifier is validated [3][4][5].

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 (Apr 3, 2025): <!-- Answer --> I found two similar open issues related to the error "[ERROR] lisinstalled plugins failed: plugin unique identifier is not valid" in the Dify repository, but no solutions were found in the comments <sup>[[1]](https://github.com/langgenius/dify-plugin-daemon/issues/112)</sup><sup>[[2]](https://github.com/langgenius/dify/issues/16616)</sup>. To resolve this error in Dify version 1.1.3 on a self-hosted Docker setup, you can try the following steps: 1. Ensure that the `manifest.yaml` file and any `.yaml` files under the `/provider` path in your plugin project have the `author` field set to your GitHub ID. This is necessary to validate the plugin's unique identifier. 2. Add or modify the following line in your `docker/.env` file: ``` FORCE_VERIFYING_SIGNATURE=false ``` 3. Restart Docker services using these commands: ```bash cd docker docker compose down docker compose up -d ``` These steps should help eliminate the error by ensuring the environment variables are properly reloaded and the plugin's unique identifier is validated <sup>[[3]](https://github.com/langgenius/dify/issues/14713)</sup><sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/jp/plugins/faq.md)</sup><sup>[[5]](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/3e610c41-ece1-4167-ae7e-8810e1d9ff6c?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/3e610c41-ece1-4167-ae7e-8810e1d9ff6c?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/3e610c41-ece1-4167-ae7e-8810e1d9ff6c?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/3e610c41-ece1-4167-ae7e-8810e1d9ff6c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/3e610c41-ece1-4167-ae7e-8810e1d9ff6c?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/3e610c41-ece1-4167-ae7e-8810e1d9ff6c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/3e610c41-ece1-4167-ae7e-8810e1d9ff6c?feedback_type=other)</sup>
yindo commented 2026-02-21 19:07:45 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 3, 2025):

Try this https://github.com/langgenius/dify/issues/16858#issuecomment-2754640885

@crazywoola commented on GitHub (Apr 3, 2025): Try this https://github.com/langgenius/dify/issues/16858#issuecomment-2754640885
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 🐞 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#12510
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?