You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please see attached log. All the containers came up and running but the docker-web-1 has errors. I get a 502 Bad gateway when I try to access the console.
✔️ Expected Behavior
It should load the homepage at localhost:3000
❌ Actual Behavior
I get a 502 Bad gateway when I try to access the console.
The text was updated successfully, but these errors were encountered:
I found a similar issue related to a 502 Bad Gateway error after upgrading to Dify version 0.10.2. This error often occurs because Nginx is forwarding requests to the wrong location. Here are the steps to resolve this issue:
Check Running Containers: Ensure that all your containers are running and note their IP addresses by executing:
Open the Nginx configuration file located at dify/docker/nginx/conf.d.
Replace http://api:5001 with the actual IP address of your API container, e.g., http://<your-api-ip>:5001.
Replace http://web:3000 with the actual IP address of your web container, e.g., http://<your-web-ip>:3000.
Restart Nginx: After updating the configuration, restart the Nginx container or reload the configuration to apply the changes.
Additionally, ensure that there are no cross-domain issues by checking the CORS configuration in your docker-compose.yml file. Update the relevant environment variables to match your new domain if necessary [1][2].
Self Checks
Dify version
0.10.2
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
web-1.txt
Please see attached log. All the containers came up and running but the docker-web-1 has errors. I get a 502 Bad gateway when I try to access the console.
✔️ Expected Behavior
It should load the homepage at localhost:3000
❌ Actual Behavior
I get a 502 Bad gateway when I try to access the console.
The text was updated successfully, but these errors were encountered: