The High Quality index mode doesn't work

[raoxinyi]

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

0.14.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Whole logs:
worker.log

docker compose ps:

✔️ Expected Behavior

Please help me fix the error：
[siliconflow] Server Unavailable Error, ('Connection aborted.'.connectionResetError(104, 'Connection reset by peer'))

❌ Actual Behavior

The Economical Index Mode works well, but when I switch to High Quality Mode, it doesn't function properly.
I have added proxy settings in the docker-compose.yaml file, which keeps the network running normally.

It works well in almost every situation except for the High Quality Mode.

[dosubot]

Hey @raoxinyi! I'm here to help you with any bugs, questions, or contributions. Let's work on solving this issue together.

The "Connection reset by peer" error you're encountering in the High Quality Index Mode could be related to several factors, especially given that the Economical Index Mode works fine. Here are some steps and considerations to help troubleshoot and potentially resolve the issue:

1. Network Stability: Ensure that your network connection is stable and that there are no interruptions. This error often occurs due to network instability.

2. Proxy Configuration: Double-check your proxy settings in the docker-compose.yaml file. Ensure that they are correctly configured and not interfering with the connection to external services required by the High Quality Index Mode.

3. Sandbox Service: Verify that the sandbox service is running properly. The absence or malfunction of this service can lead to network issues.

4. External Service Dependencies: The High Quality Index Mode relies on external services like OpenAI's embedding interface. Ensure that these services are accessible from your network and that there are no firewall or proxy restrictions blocking them.

5. Logs and Monitoring: Review the logs provided in worker.log for any additional error messages or clues that might indicate the root cause of the issue. This can help identify if the problem is with a specific service or configuration.

6. Resource Allocation: Check if there are sufficient resources (CPU, memory) allocated to the Docker containers, especially those handling the High Quality Index Mode. Insufficient resources can lead to service disruptions.

By addressing these areas, you may be able to resolve the connectivity issues affecting the High Quality Index Mode. If the problem persists, further investigation into the specific configurations and interactions with external services may be necessary.

To continue talking to Dosu, mention @dosu.

---

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

[crazywoola]

This error is raised by silliconflow's api, we can not do much about it actually.