502 Bad Gateway error

[quchenchen]

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

Dify version
v0.14.2

Cloud or Self Hosted
Self Hosted (Docker)

Steps to reproduce

I am experiencing a 502 Bad Gateway error with my Nginx setup. Upon inspecting the Docker containers, I noticed that some of the IP addresses are concatenated together, which seems to be causing the issue. Here is the output from the command （docker ps -q | xargs -n 1 docker inspect --format '{{ .Name }}: {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}'） I used to inspect the containers:
/dify_fy7y-nginx-1: 172.29.0.9
/dify_fy7y-worker-1: 172.29.0.7172.31.0.4
/dify_fy7y-api-1: 172.29.0.8172.31.0.5
/dify_fy7y-db-1: 172.29.0.3
/dify_fy7y-redis-1: 172.29.0.2
/dify_fy7y-ssrf_proxy-1: 172.29.0.5172.31.0.3
/dify_fy7y-weaviate-1: 172.29.0.4
/dify_fy7y-sandbox-1: 172.31.0.2
/dify_fy7y-web-1: 172.29.0.6

As you can see, the IP addresses for some containers are incorrectly concatenated. I need assistance in resolving this issue to ensure that Nginx can correctly forward requests to the appropriate backend services. Could you please provide guidance on how to fix the IP address configuration and ensure that Nginx is set up correctly?

The issue occurred when I was adjusting the reverse proxy address. It was accessible normally before. I have already checked the 502 Bad Gateway section on the Dify documentation, but it didn't help.