[ERROR]PluginDaemonInternalServerError: plugin not found #14498

Closed
opened 2026-02-21 19:17:31 -05:00 by yindo · 3 comments
Owner

Originally created by @RERRRER on GitHub (Jun 9, 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.4.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The plugin failed to install. Checking the log revealed that plugin_daemon-1 kept reporting errors: [ERROR] load data failed: open /app/storage/persistence/9c76ce08-6de8-4081-b9ea-bff4c3d4790e/hjlarry/mcp-server/950d09ae74ad4a2bb0e0ddde3ca25a1b: no such file or directory.

api-1 | core.plugin.impl.exc.PluginDaemonInternalServerError: PluginDaemonInternalServerError: plugin not found
plugin_daemon-1 | 2025/06/09 04:24:52 factory.go:28: [ERROR]PluginDaemonInternalServerError: plugin not found

Image

✔️ Expected Behavior

No response

Actual Behavior

No response

Originally created by @RERRRER on GitHub (Jun 9, 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.4.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce The plugin failed to install. Checking the log revealed that plugin_daemon-1 kept reporting errors: [ERROR] load data failed: open /app/storage/persistence/9c76ce08-6de8-4081-b9ea-bff4c3d4790e/hjlarry/mcp-server/950d09ae74ad4a2bb0e0ddde3ca25a1b: no such file or directory. api-1 | core.plugin.impl.exc.PluginDaemonInternalServerError: PluginDaemonInternalServerError: plugin not found plugin_daemon-1 | 2025/06/09 04:24:52 factory.go:28: [ERROR]PluginDaemonInternalServerError: plugin not found ![Image](https://github.com/user-attachments/assets/e5fd242d-99c1-4c07-a918-6fe6330ec194) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 19:17:31 -05:00
yindo closed this issue 2026-02-21 19:17:31 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Jun 9, 2025):

Hi @RERRRER! I'm Dosu and I’m helping the dify team.

This error is a known issue in Dify 1.4.1 and has been fixed in a recent update. To resolve it, uninstall and reinstall the affected plugins—no additional configuration or image updates are needed, as the underlying problem was patched on the marketplace side. If you’re running both the source code and Docker at the same time, stop one to avoid data conflicts. If the error persists, clean your database to remove conflicting provider records, or do a full database purge and fresh install. For plugin initialization timeouts, you can add PYTHON_ENV_INIT_TIMEOUT to your docker-compose.yaml as needed. For more details, see the related issues: #20448, #20445, and #15940.

To reply, just mention @dosu.


How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jun 9, 2025): <!-- Greeting --> Hi @RERRRER! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This error is a known issue in Dify 1.4.1 and has been fixed in a recent update. To resolve it, uninstall and reinstall the affected plugins—no additional configuration or image updates are needed, as the underlying problem was patched on the marketplace side. If you’re running both the source code and Docker at the same time, stop one to avoid data conflicts. If the error persists, clean your database to remove conflicting provider records, or do a full database purge and fresh install. For plugin initialization timeouts, you can add `PYTHON_ENV_INIT_TIMEOUT` to your `docker-compose.yaml` as needed. For more details, see the related issues: [#20448](https://github.com/langgenius/dify/issues/20448), [#20445](https://github.com/langgenius/dify/issues/20445), and [#15940](https://github.com/langgenius/dify/issues/15940). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/e3de9447-7299-4e85-9854-b53b253ddca9?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e3de9447-7299-4e85-9854-b53b253ddca9?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e3de9447-7299-4e85-9854-b53b253ddca9?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e3de9447-7299-4e85-9854-b53b253ddca9?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e3de9447-7299-4e85-9854-b53b253ddca9?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e3de9447-7299-4e85-9854-b53b253ddca9?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e3de9447-7299-4e85-9854-b53b253ddca9?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/20811)
Author
Owner

@RERRRER commented on GitHub (Jun 9, 2025):

All the above methods have been tried, including deleting the plugin data directory, changing the PIP mirror source, modifying FORCE_VERIFYING_SIGNATURE=false, adding PYTHON_ENV_INIT_TIMEOUT=320, and other plugins can be installed normally. However, the two plugins langgenius/tongyi and junjiem/mcp_compat_dify_tools still fail to install properly, showing the error "PluginDaemonInternalServerError: plugin not found".
Image

Image
@dosu

@RERRRER commented on GitHub (Jun 9, 2025): All the above methods have been tried, including deleting the plugin data directory, changing the PIP mirror source, modifying FORCE_VERIFYING_SIGNATURE=false, adding PYTHON_ENV_INIT_TIMEOUT=320, and other plugins can be installed normally. However, the two plugins langgenius/tongyi and junjiem/mcp_compat_dify_tools still fail to install properly, showing the error "PluginDaemonInternalServerError: plugin not found". ![Image](https://github.com/user-attachments/assets/a8555f7b-386f-46cc-8c7d-a1dc8fd5e7a3) ![Image](https://github.com/user-attachments/assets/af045002-1880-4c4f-9c5e-3ebe6dc35563) @dosu
Author
Owner

@RockChinQ commented on GitHub (Jun 10, 2025):

Image Image

I've fixed these plugins, you can try installing them again.

@RockChinQ commented on GitHub (Jun 10, 2025): <img width="777" alt="Image" src="https://github.com/user-attachments/assets/57bc87f8-4be5-41b8-b95f-c09aa6e56c18" /> <img width="594" alt="Image" src="https://github.com/user-attachments/assets/e7915eea-7c79-46a2-82ec-873d6ed8c7a9" /> I've fixed these plugins, you can try installing them again.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#14498