Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to version 0.10.2 failed #10263

Closed
5 tasks done
murtaza-motorwala opened this issue Nov 4, 2024 · 3 comments
Closed
5 tasks done

Upgrade to version 0.10.2 failed #10263

murtaza-motorwala opened this issue Nov 4, 2024 · 3 comments
Labels
🐞 bug Something isn't working 🤔 cant-reproduce This issue can not be reproduced

Comments

@murtaza-motorwala
Copy link

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

@dosubot dosubot bot added the 🐞 bug Something isn't working label Nov 4, 2024
Copy link

dosubot bot commented Nov 4, 2024

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:

  1. Check Running Containers: Ensure that all 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 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.
  3. 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].

To continue talking to Dosu, mention @dosu.

@damadorPL
Copy link

2024-11-04 21:01:02 Error: ENOSPC: no space left on device, mkdir - you server is full ?

@crazywoola
Copy link
Member

This logs is pretty straightforward, you are running out of the disk spaces.

@crazywoola crazywoola added the 🤔 cant-reproduce This issue can not be reproduced label Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working 🤔 cant-reproduce This issue can not be reproduced
Projects
None yet
Development

No branches or pull requests

3 participants