Upload knowledge base error, error information:Meta endpoint! Unexpected status code: 502, with response body: None.

[wgq910668]

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

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

Uploading knowledge base error, select high quality upload. Error. Error message：Meta endpoint! Unexpected status code: 502, with response body: None.

Deployment method: local source code deployment. Front-end and back-end are deployed. Other components are deployed by docker. Including weaviate and worker logs.

Worker log information：

docker ps：

docker logs :

✔️ Expected Behavior

Upload Successfully

❌ Actual Behavior

No response

[dosubot]

A similar issue was reported and resolved in a closed thread. The error "Meta endpoint! Unexpected status code: 502, with response body: None" in a self-hosted Dify setup using Docker is likely related to an issue with the Nginx configuration forwarding the service to the wrong location. Here are the steps you can take to resolve this issue:

1. Check Running Containers: Ensure that your containers are running and note their IP addresses by executing:

   docker ps -q | xargs -n 1 docker inspect --format '{{ .Name }}: {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}'

2. Update Nginx Configuration:

   • Open the Nginx configuration file located at dify/docker/nginx/conf.d.
   • Replace http://api:5001 with http://<your-api-ip>:5001.
   • Replace http://web:3000 with http://<your-web-ip>:3000.

3. Restart Nginx: After updating the configuration, restart the Nginx container or reload the configuration to apply the changes.

These steps should help in resolving the 502 error by ensuring that the requests are correctly routed to the appropriate service endpoints ^[1].

To continue talking to Dosu, mention @dosu.

---

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

[crazywoola]

might related to this #12960 as well.