502 Bad Gateway for brand new installation

[TianzeWang]

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

v0.10.2 - Main UTC+8 (Nov.4 12:48PM)

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I followed exactly the same to update the code and initially encountered this error. To exclude the issues of my local configuration, I created a new folder and git cloned a new copy of dify, and same issue still persists.

2. Git clone dify main
3. CD docker, cp .env
4. Mac Desktop Docker updated to latest version
5. docker compose up -d

✔️ Expected Behavior

Docker normally start up

❌ Actual Behavior

Docker showed 502 bad gateway

[dosubot]

@TianzeWang Hello there! I'm here to help you with any bugs, questions, or contributions for Dify. Let's tackle this issue together!

The "502 Bad Gateway" error you're encountering in a self-hosted Docker installation of Dify version v0.10.2 is likely due to Nginx forwarding the service to the wrong location. To resolve this, ensure that the containers are running and then execute the following command with root privileges to get the correct IP addresses:

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

Look for lines similar to:

/docker-web-1: 172.19.0.5
/docker-api-1: 172.19.0.7

Note the IP addresses and then open the dify/docker/nginx/conf.d directory. Replace http://api:5001 with http://172.19.0.7:5001 and http://web:3000 with http://172.19.0.5:3000. After making these changes, restart the Nginx container or reload the configuration. Remember, these IP addresses are examples; you must execute the command to get your own IP addresses and configure them accordingly. You may need to reconfigure the IP addresses if you restart the related containers ^[1].

To continue talking to Dosu, mention @dosu.

[TianzeWang]

I have repeated the same, same issue still persists.

[TianzeWang]

However I noticed that the worker and api shows multiple ip address. Not sure if this is causing the problem.

[crazywoola]

Please check the container logs, we discovered a strange behavior that you need to wait for several minutes to start the container.