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

Plugin installation stucked #11951

New Issue
Closed
opened 2026-02-21 19:04:55 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:04:55 -05:00
Owner
Copy Link
Copy Source

Originally created by @gangqinxiao13 on GitHub (Mar 21, 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

v1.1.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When a plugin installation fails, the installation process gets stuck, and it's impossible to determine which plugin failed to install. How can I identify which plugin installation failed? How can I manually stop the installation of plugins or check the status of plugin installations?

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @gangqinxiao13 on GitHub (Mar 21, 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 v1.1.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When a plugin installation fails, the installation process gets stuck, and it's impossible to determine which plugin failed to install. How can I identify which plugin installation failed? How can I manually stop the installation of plugins or check the status of plugin installations? ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:04:55 -05:00
yindo closed this issue 2026-02-21 19:04:56 -05:00
yindo commented 2026-02-21 19:04:56 -05:00
Author
Owner
Copy Link
Copy Source

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

I found some relevant information that might help with your issue regarding plugin installation in Dify.

  1. Identifying Failed Plugin Installations: Unfortunately, there isn't specific information on how to identify which plugin failed during installation. However, you can check the Docker container logs for installation status using the command docker logs container_name to get more insights into the process [1].

  2. Stopping Plugin Installations: There is no direct information available on manually stopping a plugin installation in Dify. This might require further investigation or checking the Dify documentation for any updates on this feature.

  3. Similar Issues: There are similar issues reported where plugin installations failed or got stuck. For example, one solution suggested increasing the Python environment initialization timeout by adding PYTHON_ENV_INIT_TIMEOUT: 320 to your docker-compose.yaml under the plugin_daemon service. Additionally, ensuring a stable network connection and disabling signature verification by adding FORCE_VERIFYING_SIGNATURE=false to your .env file might help [2][3].

These steps might help you troubleshoot and resolve the issue with plugin installations getting stuck.

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 21, 2025): <!-- Answer --> I found some relevant information that might help with your issue regarding plugin installation in Dify. 1. **Identifying Failed Plugin Installations**: Unfortunately, there isn't specific information on how to identify which plugin failed during installation. However, you can check the Docker container logs for installation status using the command `docker logs container_name` to get more insights into the process <sup>[[1]](https://github.com/langgenius/dify/issues/14776)</sup>. 2. **Stopping Plugin Installations**: There is no direct information available on manually stopping a plugin installation in Dify. This might require further investigation or checking the Dify documentation for any updates on this feature. 3. **Similar Issues**: There are similar issues reported where plugin installations failed or got stuck. For example, one solution suggested increasing the Python environment initialization timeout by adding `PYTHON_ENV_INIT_TIMEOUT: 320` to your `docker-compose.yaml` under the `plugin_daemon` service. Additionally, ensuring a stable network connection and disabling signature verification by adding `FORCE_VERIFYING_SIGNATURE=false` to your `.env` file might help <sup>[[2]](https://github.com/langgenius/dify/issues/15808)</sup><sup>[[3]](https://github.com/langgenius/dify/issues/15243)</sup>. These steps might help you troubleshoot and resolve the issue with plugin installations getting stuck. <!-- 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/c9e7f09d-e968-4971-b0a9-54962c14a2e6?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/c9e7f09d-e968-4971-b0a9-54962c14a2e6?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/c9e7f09d-e968-4971-b0a9-54962c14a2e6?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/c9e7f09d-e968-4971-b0a9-54962c14a2e6?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c9e7f09d-e968-4971-b0a9-54962c14a2e6?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/c9e7f09d-e968-4971-b0a9-54962c14a2e6?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c9e7f09d-e968-4971-b0a9-54962c14a2e6?feedback_type=other)</sup>
yindo commented 2026-02-21 19:04:56 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 21, 2025):

You can restart the plugin_daemon.

@crazywoola commented on GitHub (Mar 21, 2025): You can restart the plugin_daemon.
yindo commented 2026-02-21 19:04:56 -05:00
Author
Owner
Copy Link
Copy Source

@Kudou-Chitose commented on GitHub (Mar 21, 2025):

You can restart the plugin_daemon.

After upgrading from version 0.15.3 to v1.1.1, the system seems to be stuck. Even after restarting the plugin_daemon or performing a docker compose down & up, the issue persists. All five plugins are installed, but the system still displays "installing."
Image

Additionally, while some LLM configurations (e.g., volcengine_maas and OpenAI-API-compatible) were lost during the upgrade, others repeated.
Image

Downgrading back to version 0.15.3 resolved the issue, and all configurations were restored. However, upgrading to v1.1.1 again causes the issue to reappear.

@Kudou-Chitose commented on GitHub (Mar 21, 2025): > You can restart the plugin_daemon. After upgrading from version 0.15.3 to v1.1.1, the system seems to be stuck. Even after restarting the plugin_daemon or performing a docker compose down & up, the issue persists. All five plugins are installed, but the system still displays "installing." ![Image](https://github.com/user-attachments/assets/7c2fff08-2e7d-4bfa-8399-578405390bd4) Additionally, while some LLM configurations (e.g., volcengine_maas and OpenAI-API-compatible) were lost during the upgrade, others repeated. ![Image](https://github.com/user-attachments/assets/ba5ec6ae-9196-445d-8383-488f00d4e332) Downgrading back to version 0.15.3 resolved the issue, and all configurations were restored. However, upgrading to v1.1.1 again causes the issue to reappear.
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#11951
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?