Hey @lbbc1117! I'm here to help you with any bugs, questions, or contributions you have for Dify. Let's work together to solve your issue!

The SSL error you're encountering in a self-hosted Dify setup without a proxy might be related to the default SSL settings in the Docker environment. By default, HTTPS is disabled in Dify's Docker setup, which could lead to SSL handshake issues if not configured properly.

To address this, you can check and modify the following settings in your Docker environment:

1. Enable HTTPS: Ensure that NGINX_HTTPS_ENABLED is set to true in your Docker environment configuration. This will enable HTTPS and allow SSL connections.

2. SSL Certificates: Verify that the SSL certificate and key files (dify.crt and dify.key) are correctly configured and accessible by the Docker container. These files should be placed in the appropriate directory and referenced correctly in your configuration.

3. SSL Protocols: Ensure that the SSL protocols are correctly set. The default protocols are TLSv1.1, TLSv1.2, and TLSv1.3. You might want to adjust these if your environment requires different protocols.

4. Network Configuration: Double-check your network settings to ensure there are no firewall rules or network policies blocking SSL traffic.

These steps should help resolve the SSL errors you're experiencing. If the issue persists, consider checking the Docker logs for more detailed error messages that might provide further insights into the problem.

To continue talking to Dosu, mention @dosu.

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

Fixed in #11906
Duplicated #11839
Duplicated #11739

Fixed in #11906 Duplicated #11839 Duplicated #11739

THX for reply

But reverting HTTP proxy settings as mentioned in #11906 and re-running docker compose NOT solving this issue

It looks like a SSL issue, not proxy