Offline Environment Failure: Plugin Still Attempts to Install dify_plugin from PyPI Despite Configuration Changes (Network Timeout) #48 #8818

Closed
opened 2026-02-21 18:27:54 -05:00 by yindo · 1 comment
Owner

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

related issue https://github.com/langgenius/dify-plugin-daemon/issues/48

✔️ Expected Behavior

No response

Actual Behavior

No response

Originally created by @jun0315 on GitHub (Mar 1, 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 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce related issue https://github.com/langgenius/dify-plugin-daemon/issues/48 ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:27:54 -05:00
yindo closed this issue 2026-02-21 18:27:54 -05:00
Author
Owner

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

Hello, @jun0315! I'm here to help you with any bugs, questions, or contributions related to Dify. Let's tackle this issue together while we wait for a human maintainer.

I found a similar open issue that might be relevant to your situation. The issue suggests that the problem could be related to how Dify differentiates between local and marketplace plugins. To address this, you should:

  1. Ensure that the plugin is correctly identified as a local plugin by verifying the configuration settings, such as MARKETPLACE_ENABLED and MARKETPLACE_API_URL, in your environment to prevent unintended marketplace interactions.

  2. Review the logic in your upgrade process to ensure that it correctly identifies and handles local plugins without attempting to fetch updates from the marketplace. This involves checking the conditions under which the HTTP request to the marketplace is triggered and ensuring they are not met for local plugins [1].

Additionally, for offline environments, you can consider using the "Local Upload" method by packaging your plugin into a .difypkg file and uploading it manually. This method is suitable for offline environments and allows you to maintain internal plugins without exposing sensitive information [2].

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 1, 2025): <!-- Greeting --> Hello, @jun0315! I'm here to help you with any bugs, questions, or contributions related to Dify. Let's tackle this issue together while we wait for a human maintainer. <!-- Answer --> I found a similar open issue that might be relevant to your situation. The issue suggests that the problem could be related to how Dify differentiates between local and marketplace plugins. To address this, you should: 1. Ensure that the plugin is correctly identified as a local plugin by verifying the configuration settings, such as `MARKETPLACE_ENABLED` and `MARKETPLACE_API_URL`, in your environment to prevent unintended marketplace interactions. 2. Review the logic in your upgrade process to ensure that it correctly identifies and handles local plugins without attempting to fetch updates from the marketplace. This involves checking the conditions under which the HTTP request to the marketplace is triggered and ensuring they are not met for local plugins <sup>[[1]](https://github.com/langgenius/dify/issues/14276)</sup>. Additionally, for offline environments, you can consider using the "Local Upload" method by packaging your plugin into a `.difypkg` file and uploading it manually. This method is suitable for offline environments and allows you to maintain internal plugins without exposing sensitive information <sup>[[2]](https://github.com/langgenius/dify/issues/14582)</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/92966f0d-2afb-44ca-b95b-6a22fe2092d4?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/92966f0d-2afb-44ca-b95b-6a22fe2092d4?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/92966f0d-2afb-44ca-b95b-6a22fe2092d4?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/92966f0d-2afb-44ca-b95b-6a22fe2092d4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/92966f0d-2afb-44ca-b95b-6a22fe2092d4?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/92966f0d-2afb-44ca-b95b-6a22fe2092d4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/92966f0d-2afb-44ca-b95b-6a22fe2092d4?feedback_type=other)</sup>
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#8818