about 1.0.1 plugin-daemon proxy setting bugs

[ZHBingo]

Self Checks

• [x] This is only for bug report, if you would like to ask a question, please head to Discussions.
• [x] I have searched for existing issues search for existing issues, including closed ones.
• [x] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• [x] Please do not modify this template :) and fill in all the required fields.

Dify version

1.0.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I deployed Dify using Docker within an internal network. Due to network restrictions, I must use a proxy to download and compile plugins. I added http_proxy and https_proxy to the plugin_daemon node in the docker-compose.yaml. However, the console now reports an error: uv pip install does not recognize --proxy. When using pip install with a proxy, the --proxy works, but uv pip does not support the --proxy parameter. As a result, plugins consistently fail to compile under proxy settings. Could you please confirm if this is a bug?

✔️ Expected Behavior

After configuring the proxy, the plugins can download dependencies through the proxy and complete compilation.

❌ Actual Behavior

An error was reported: uv pip install does not support the --proxy parameter.

[dosubot[bot]]

Hello @ZHBingo! I'm here to help you with bug fixes, answer questions, and guide you on how to become a contributor. Let's work together to resolve the issue you're facing.

There is a known issue in the Dify codebase regarding the use of proxies with uv pip install. The error 'unexpected argument --proxy' occurs when installing plugin dependencies in the Dify plugin daemon. To resolve this, you can replace the plugin_daemon tag in your Docker configuration with 07d13bfb59acc422afa06436c7fdc5f3bc7e6554-local, which addresses the redundant proxy handling in the Python environment setup ^[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}

[crazywoola]

I think need more details to confirm this is a bug. What's your plugin_daemon version?

[xiaoyunjie]

I have the same problem，plugin-daemon version 0.0.4-local Intranet environment Plug-ins and dependencies are downloaded through agents

@crazywoola

[kaughn]

Same for me.

[system-man]

add proxy in cmd.ENV()

[kurokobo]

@crazywoola Summary of the proxy-related issues for each version:

• ✅ 0.0.3-local (with Dify 1.0.0)
  • No proxy-related issue exists
• 🚨 0.0.4-local (with Dify 1.0.1)
  • Unexpected argument --proxy is used in proxy environment
  • Reported by
    • https://github.com/langgenius/dify-plugin-daemon/issues/102
    • #16052 (this issue)
  • Fixed by https://github.com/langgenius/dify-plugin-daemon/pull/99
• 🚨 0.0.5-local (with Dify 1.1.0)
  • Inaccessible to PyPI in proxy environment
  • Reported by
    • https://github.com/langgenius/dify/issues/16076
    • https://github.com/langgenius/dify-plugin-daemon/issues/118
  • Fixed by https://github.com/langgenius/dify-plugin-daemon/pull/119

So I'm waiting for the https://github.com/langgenius/dify-plugin-daemon/pull/119 to be merged and new 0.0.6-local will be released 😃

[kurokobo]

A short-term workaround is to use 0.0.3-local instead of 0.0.4-local or 0.0.5-local. In my environment, it works fine even under a proxy.

However, there is a possibility that other issues, which have been fixed in 0.0.4-local and 0.0.5-local, may emerge, so whether the plugin installation completes successfully and becomes usable depends on your environment.

[kurokobo]

@Yeuoly F.Y.I.

[Yeuoly]

@Yeuoly F.Y.I.

Great work! I have merged it

[kurokobo]

https://github.com/langgenius/dify-plugin-daemon/pull/119#issuecomment-2736755526

[xiaoyunjie]

tks，i solved the problem

[jskcnsl]

I have the same issue of https://github.com/langgenius/dify/issues/17072, can you take a look again ?