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

Plugin installation failed through market #8950

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

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

1.0.0, commit 43ab7c22a7

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

Plugin system is not working:

  1. Plugin installation through the marketplace fails for any plugin.
  2. Plugin installation will silently fail through local files after a waiting period.

✔️ Expected Behavior

Plugin installation should success.

❌ Actual Behavior

No plugin installation can be done through marketplace and local files.

Originally created by @iondex on GitHub (Mar 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 1.0.0, commit 43ab7c22a78f4376275510c7178baf17575cdbe1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/b1299563-91af-4027-9491-6dee00384bd8) Plugin system is not working: 1. Plugin installation through the marketplace fails for any plugin. 2. Plugin installation will silently fail through local files after a waiting period. ### ✔️ Expected Behavior Plugin installation should success. ### ❌ Actual Behavior No plugin installation can be done through marketplace and local files.
yindo added the 🐞 bug label 2026-02-21 18:28:48 -05:00
yindo closed this issue 2026-02-21 18:28:48 -05:00
yindo commented 2026-02-21 18:28:48 -05:00
Author
Owner
Copy Link
Copy Source

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

@iondex Hello there! I'm Dosu, a bot here to help you with bug fixes, answer questions, and guide you on how to contribute. Let's tackle this issue together while we wait for a human maintainer to assist.

I found some relevant information that might help with the plugin installation issue you're experiencing in Dify version 1.0.0 when self-hosted with Docker.

  1. Timeout and Gateway Errors: The plugin installation failure might be due to a timeout error and a 504 Gateway Time-out error when fetching plugin manifests from marketplace.dify.ai. This could be a temporary connectivity issue with the marketplace [1].

  2. Environment Timeout Adjustment: If you encounter an error related to 'init environment failed', you can try adding the PYTHON_ENV_INIT_TIMEOUT environment variable to your docker-compose.yaml file under the plugin_daemon service configuration to extend the timeout period. Here's how you can do it:

    plugin_daemon:
  environment:
    PYTHON_ENV_INIT_TIMEOUT: 320

    This change increases the default timeout from 120 seconds to 320 seconds, which might help prevent the 'init environment failed' error during plugin installation [1].

  3. Network Stability: Ensure your network connection is stable. If you're using a proxy like Clash, enabling global TUN mode has been reported to resolve installation timeout problems [2].

These steps should help address the plugin installation issues you're facing.

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): <!-- Greeting --> @iondex Hello there! I'm Dosu, a bot here to help you with bug fixes, answer questions, and guide you on how to contribute. Let's tackle this issue together while we wait for a human maintainer to assist. <!-- Answer --> I found some relevant information that might help with the plugin installation issue you're experiencing in Dify version 1.0.0 when self-hosted with Docker. 1. **Timeout and Gateway Errors**: The plugin installation failure might be due to a timeout error and a 504 Gateway Time-out error when fetching plugin manifests from marketplace.dify.ai. This could be a temporary connectivity issue with the marketplace <sup>[[1]](https://github.com/langgenius/dify/issues/14729)</sup>. 2. **Environment Timeout Adjustment**: If you encounter an error related to 'init environment failed', you can try adding the `PYTHON_ENV_INIT_TIMEOUT` environment variable to your `docker-compose.yaml` file under the `plugin_daemon` service configuration to extend the timeout period. Here's how you can do it: ```yaml plugin_daemon: environment: PYTHON_ENV_INIT_TIMEOUT: 320 ``` This change increases the default timeout from 120 seconds to 320 seconds, which might help prevent the 'init environment failed' error during plugin installation <sup>[[1]](https://github.com/langgenius/dify/issues/14729)</sup>. 3. **Network Stability**: Ensure your network connection is stable. If you're using a proxy like Clash, enabling global TUN mode has been reported to resolve installation timeout problems <sup>[[2]](https://github.com/langgenius/dify/issues/14535)</sup>. These steps should help address the plugin installation issues you're facing. <!-- 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/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=other)</sup>
yindo commented 2026-02-21 18:28:48 -05:00
Author
Owner
Copy Link
Copy Source

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

Duplicated #14820

@crazywoola commented on GitHub (Mar 3, 2025): Duplicated #14820
yindo commented 2026-02-21 18:28:48 -05:00
Author
Owner
Copy Link
Copy Source

@FerretAngel commented on GitHub (Mar 4, 2025):

@iondex Hello there! I'm Dosu, a bot here to help you with bug fixes, answer questions, and guide you on how to contribute. Let's tackle this issue together while we wait for a human maintainer to assist.你好呀！我是DOSU，这里是一个机器人，可以帮助您解决错误修复，回答问题并指导您如何做出贡献。当我们等待人类维护者协助时，让我们一起解决这个问题。

I found some relevant information that might help with the plugin installation issue you're experiencing in Dify version 1.0.0 when self-hosted with Docker.我找到了一些相关信息，这些信息可能有助于您在Dify版本1.0.0中遇到的插件安装问题。

  1. Timeout and Gateway Errors: The plugin installation failure might be due to a timeout error and a 504 Gateway Time-out error when fetching plugin manifests from marketplace.dify.ai. This could be a temporary connectivity issue with the marketplace [1].超时和网关错误：插件安装故障可能是由于超时错误和504网关超时错误，从Marketplace.dify.ai出现插件时。这可能是市场[1]的临时连接问题。

  2. Environment Timeout Adjustment: If you encounter an error related to 'init environment failed', you can try adding the PYTHON_ENV_INIT_TIMEOUT environment variable to your docker-compose.yaml file under the plugin_daemon service configuration to extend the timeout period. Here's how you can do it:���境超时调整：如果遇到与“初始化环境失败”相关的错误，则可以尝试在服务配置下将环境变量添加到文件中以延长超时周期。您可以做到这一点：
    plugin_daemon:
    environment:
    PYTHON_ENV_INIT_TIMEOUT: 320

    This change increases the default timeout from 120 seconds to 320 seconds, which might help prevent the 'init environment failed' error during plugin installation [1].此更改将默认超时从120秒增加到320秒，这可能有助于防止插件安装期间的“ Init环境失败”错误[1]。

  3. Network Stability: Ensure your network connection is stable. If you're using a proxy like Clash, enabling global TUN mode has been reported to resolve installation timeout problems [2].网络稳定性：确保您的网络连接稳定。如果您使用的是诸如冲突之类的代理，则据报道启用全局TUN模式来解决安装超时问题[2]。

These steps should help address the plugin installation issues you're facing.这些步骤应有助于解决您所面临的插件安装问题。

_To continue talking to Dosu, mention @dosu._要继续与 dosu 交谈。

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other帮助DOSU学习！给予反馈：出色的响应 | 无关的答案 | 不正确的来源 | 太冗长 | 幻觉 | 错误报告 | 其他

请问如何为dify的docker环境配置全局代理？

@FerretAngel commented on GitHub (Mar 4, 2025): > [@iondex](https://github.com/iondex) Hello there! I'm Dosu, a bot here to help you with bug fixes, answer questions, and guide you on how to contribute. Let's tackle this issue together while we wait for a human maintainer to assist.你好呀！我是DOSU，这里是一个机器人，可以帮助您解决错误修复，回答问题并指导您如何做出贡献。当我们等待人类维护者协助时，让我们一起解决这个问题。 > > I found some relevant information that might help with the plugin installation issue you're experiencing in Dify version 1.0.0 when self-hosted with Docker.我找到了一些相关信息，这些信息可能有助于您在Dify版本1.0.0中遇到的插件安装问题。 > > 1. **Timeout and Gateway Errors**: The plugin installation failure might be due to a timeout error and a 504 Gateway Time-out error when fetching plugin manifests from marketplace.dify.ai. This could be a temporary connectivity issue with the marketplace [[1]](https://github.com/langgenius/dify/issues/14729).**超时和网关错误**：插件安装故障可能是由于超时错误和504网关超时错误，从Marketplace.dify.ai出现插件时。这可能是市场[[1]](https://github.com/langgenius/dify/issues/14729)的临时连接问题。 > 2. **Environment Timeout Adjustment**: If you encounter an error related to 'init environment failed', you can try adding the `PYTHON_ENV_INIT_TIMEOUT` environment variable to your `docker-compose.yaml` file under the `plugin_daemon` service configuration to extend the timeout period. Here's how you can do it:**���境超时调整**：如果遇到与“初始化环境失败”相关的错误，则可以尝试在服务配置下将环境变量添加到文件中以延长超时周期。您可以做到这一点： > plugin_daemon: > environment: > PYTHON_ENV_INIT_TIMEOUT: 320 > > > > > > > > > > This change increases the default timeout from 120 seconds to 320 seconds, which might help prevent the 'init environment failed' error during plugin installation [[1]](https://github.com/langgenius/dify/issues/14729).此更改将默认超时从120秒增加到320秒，这可能有助于防止插件安装期间的“ Init环境失败”错误[[1]](https://github.com/langgenius/dify/issues/14729)。 > 3. **Network Stability**: Ensure your network connection is stable. If you're using a proxy like Clash, enabling global TUN mode has been reported to resolve installation timeout problems [[2]](https://github.com/langgenius/dify/issues/14535).<SD1>网络稳定性：确保您的网络连接稳定。如果您使用的是诸如冲突之类的代理，则据报道启用全局TUN模式来解决安装超时问题[[2]](https://github.com/langgenius/dify/issues/14535)。 > > These steps should help address the plugin installation issues you're facing.这些步骤应有助于解决您所面临的插件安装问题。 > > _To continue talking to [Dosu](https://dosu.dev), mention [@dosu](https://github.com/dosu)._要继续与[ dosu ](https://dosu.dev)交谈。 > > Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=other)帮助DOSU学习！给予反馈：[出色的响应](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=great_response) | [无关的答案](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=irrelevant_answer) | [不正确的来源](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=incorrect_sources) | [太冗长](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=too_verbose) | [幻觉](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=hallucination) | [错误报告](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=bug_report) | [其他](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=other) 请问如何为dify的docker环境配置全局代理？
yindo commented 2026-02-21 18:28:48 -05:00
Author
Owner
Copy Link
Copy Source

@tonyc726 commented on GitHub (Mar 5, 2025):

@iondex Hello there! I'm Dosu, a bot here to help you with bug fixes, answer questions, and guide you on how to contribute. Let's tackle this issue together while we wait for a human maintainer to assist.

I found some relevant information that might help with the plugin installation issue you're experiencing in Dify version 1.0.0 when self-hosted with Docker.

  1. Timeout and Gateway Errors: The plugin installation failure might be due to a timeout error and a 504 Gateway Time-out error when fetching plugin manifests from marketplace.dify.ai. This could be a temporary connectivity issue with the marketplace [1].

  2. Environment Timeout Adjustment: If you encounter an error related to 'init environment failed', you can try adding the PYTHON_ENV_INIT_TIMEOUT environment variable to your docker-compose.yaml file under the plugin_daemon service configuration to extend the timeout period. Here's how you can do it:
    plugin_daemon:
    environment:
    PYTHON_ENV_INIT_TIMEOUT: 320

    This change increases the default timeout from 120 seconds to 320 seconds, which might help prevent the 'init environment failed' error during plugin installation [1].

  3. Network Stability: Ensure your network connection is stable. If you're using a proxy like Clash, enabling global TUN mode has been reported to resolve installation timeout problems [2].

These steps should help address the plugin installation issues you're facing.

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 added PYTHON_ENV_INIT_TIMEOUT: 320 in the docker-compose.yml, and it works. So why not install some model providers by default? @dosu Anyway, the dify server is so slow.😂

@tonyc726 commented on GitHub (Mar 5, 2025): > [@iondex](https://github.com/iondex) Hello there! I'm Dosu, a bot here to help you with bug fixes, answer questions, and guide you on how to contribute. Let's tackle this issue together while we wait for a human maintainer to assist. > > I found some relevant information that might help with the plugin installation issue you're experiencing in Dify version 1.0.0 when self-hosted with Docker. > > 1. **Timeout and Gateway Errors**: The plugin installation failure might be due to a timeout error and a 504 Gateway Time-out error when fetching plugin manifests from marketplace.dify.ai. This could be a temporary connectivity issue with the marketplace [[1]](https://github.com/langgenius/dify/issues/14729). > 2. **Environment Timeout Adjustment**: If you encounter an error related to 'init environment failed', you can try adding the `PYTHON_ENV_INIT_TIMEOUT` environment variable to your `docker-compose.yaml` file under the `plugin_daemon` service configuration to extend the timeout period. Here's how you can do it: > plugin_daemon: > environment: > PYTHON_ENV_INIT_TIMEOUT: 320 > > > This change increases the default timeout from 120 seconds to 320 seconds, which might help prevent the 'init environment failed' error during plugin installation [[1]](https://github.com/langgenius/dify/issues/14729). > 3. **Network Stability**: Ensure your network connection is stable. If you're using a proxy like Clash, enabling global TUN mode has been reported to resolve installation timeout problems [[2]](https://github.com/langgenius/dify/issues/14535). > > These steps should help address the plugin installation issues you're facing. > > _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/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/43538c26-6f4d-4116-8232-45d066d66e7c?feedback_type=other) I added `PYTHON_ENV_INIT_TIMEOUT: 320` in the `docker-compose.yml`, and it works. So why not install some model providers by default? @dosu Anyway, the dify server is so slow.😂
yindo commented 2026-02-21 18:28:48 -05:00
Author
Owner
Copy Link
Copy Source

@BrikerMan commented on GitHub (Mar 5, 2025):

PYTHON_ENV_INIT_TIMEOUT did not work on my end. And only solution I find is manually download form dify marketplace then install it.

@BrikerMan commented on GitHub (Mar 5, 2025): `PYTHON_ENV_INIT_TIMEOUT` did not work on my end. And only solution I find is manually download form dify marketplace then install it.
yindo commented 2026-02-21 18:28:48 -05:00
Author
Owner
Copy Link
Copy Source

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

To configure a global proxy for Dify's Docker environment, you don't need to manually set the HTTP_PROXY and HTTPS_PROXY environment variables if you're using the latest version of Dify, as it handles proxy settings automatically. If you're using WSL2, ensure that networkingMode=mirrored and autoProxy=true are enabled in your .wslconfig file, and configure your proxy (like Clash) as a system proxy on Windows. No additional proxy configuration is needed in the Docker configuration. If you experience connection issues, make sure you're using the latest version of Dify, as earlier versions had known proxy-related issues that have since been fixed [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 5, 2025): <!-- Answer --> To configure a global proxy for Dify's Docker environment, you don't need to manually set the `HTTP_PROXY` and `HTTPS_PROXY` environment variables if you're using the latest version of Dify, as it handles proxy settings automatically. If you're using WSL2, ensure that `networkingMode=mirrored` and `autoProxy=true` are enabled in your `.wslconfig` file, and configure your proxy (like Clash) as a system proxy on Windows. No additional proxy configuration is needed in the Docker configuration. If you experience connection issues, make sure you're using the latest version of Dify, as earlier versions had known proxy-related issues that have since been fixed <sup>[[1]](https://github.com/langgenius/dify/issues/11839)</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/57e78765-dbd3-4c53-b506-0b1a08715247?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/57e78765-dbd3-4c53-b506-0b1a08715247?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/57e78765-dbd3-4c53-b506-0b1a08715247?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/57e78765-dbd3-4c53-b506-0b1a08715247?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/57e78765-dbd3-4c53-b506-0b1a08715247?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/57e78765-dbd3-4c53-b506-0b1a08715247?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/57e78765-dbd3-4c53-b506-0b1a08715247?feedback_type=other)</sup>
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#8950
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?