How to properly configure HTTP proxy for Dify in Docker container (e.g., for OpenAI access in restricted regions)General Discussion

[zhihaoyang30]

Self Checks

• 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.

Content

Issue Summary

I am trying to run Dify via Docker in a region where direct access to OpenAI, Hugging Face, and similar services is blocked. I’ve set up an HTTP proxy (e.g., Clash running on 127.0.0.1:7890) on the host and confirmed that it works from the host machine.

However, I’m unable to get Dify’s Docker container to route traffic through the proxy despite trying:

• Setting HTTP_PROXY and HTTPS_PROXY in the container environment
• Adding proxy settings in docker-compose.yml
• Modifying /etc/environment or the Dockerfile

Steps to Reproduce

1. Run Dify using docker-compose with a working proxy on the host
2. Set proxy in container using env vars or Dockerfile
3. Observe that outbound API requests (e.g., to OpenAI) still fail with DNS errors

Expected Behavior

Dify components inside the Docker container should route their outbound HTTP requests through the configured proxy (e.g., via HTTP_PROXY).

Actual Behavior

All outbound connections fail with errors like:

'HTTPSConnectionPool(host=\'maps.googleapis.com\', port=443): Max retries exceeded with url 'xxx''

Request

Could you please provide:

• Official documentation or guidance on configuring Dify with an HTTP proxy inside Docker?
• Any best practices for deploying Dify in environments with restricted internet access?

Thanks in advance!

---

Environment:

• Docker on [Linux]
• Docker Compose
• Proxy: http://127.0.0.1:7890 (Clash)