langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

how to setup ngnix config,now call api got Bad Getway #6036

New Issue
Closed
opened 2026-02-21 18:13:47 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 18:13:47 -05:00
Owner
Copy Link
Copy Source

Originally created by @tonyliu088 on GitHub (Oct 11, 2024).

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

docker ps -q | xargs -n 1 docker inspect --format '{{ .Name }}: {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}'
when i use this command ,got ip like /docker-api-1: 192.168.192.7192.168.208.4
how to setup in default.conf ?

✔️ Expected Behavior

No response

❌ Actual Behavior

docker ps -q | xargs -n 1 docker inspect --format '{{ .Name }}: {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}'
when i use this command ,got ip like /docker-api-1: 192.168.192.7192.168.208.4
how to setup in default.conf ?

location /v1 {
proxy_pass http://api:5001;
include proxy.conf;
}

Originally created by @tonyliu088 on GitHub (Oct 11, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.8.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce docker ps -q | xargs -n 1 docker inspect --format '{{ .Name }}: {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' when i use this command ,got ip like /docker-api-1: 192.168.192.7192.168.208.4 how to setup in default.conf ? ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior docker ps -q | xargs -n 1 docker inspect --format '{{ .Name }}: {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' when i use this command ,got ip like /docker-api-1: 192.168.192.7192.168.208.4 how to setup in default.conf ? location /v1 { proxy_pass http://api:5001; include proxy.conf; }
yindo added the 🙋‍♂️ question label 2026-02-21 18:13:47 -05:00
yindo closed this issue 2026-02-21 18:13:47 -05:00
yindo commented 2026-02-21 18:13:47 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 11, 2024):

I found a similar discussion that might help: how to update nginx/conf.d/default.conf, if modify directly, will replace [1].

To resolve the "Bad Gateway" error, ensure Nginx is forwarding requests to the correct IP addresses. Here's how you can configure the default.conf:

  1. Use the command to get the correct IP addresses of your containers:

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

  2. Check the output for the correct IP addresses. It seems like your output is malformed. Ensure each container has a single IP address.

  3. Update your default.conf with the correct IP address. For example, if /docker-api-1 has the IP 192.168.192.7, update the proxy_pass line:

    location /v1 {
    proxy_pass http://192.168.192.7:5001;
    include proxy.conf;
}

  4. Restart the Nginx container to apply the changes.

Make sure to verify the IP addresses and update them accordingly in your configuration [2].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Oct 11, 2024): <!-- Answer --> I found a similar discussion that might help: [how to update nginx/conf.d/default.conf, if modify directly, will replace](https://github.com/langgenius/dify/discussions/9217) <sup>[[1]](https://github.com/langgenius/dify/discussions/9217)</sup>. To resolve the "Bad Gateway" error, ensure Nginx is forwarding requests to the correct IP addresses. Here's how you can configure the `default.conf`: 1. Use the command to get the correct IP addresses of your containers: ```bash docker ps -q | xargs -n 1 docker inspect --format '{{ .Name }}: {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' ``` 2. Check the output for the correct IP addresses. It seems like your output is malformed. Ensure each container has a single IP address. 3. Update your `default.conf` with the correct IP address. For example, if `/docker-api-1` has the IP `192.168.192.7`, update the `proxy_pass` line: ```nginx location /v1 { proxy_pass http://192.168.192.7:5001; include proxy.conf; } ``` 4. Restart the Nginx container to apply the changes. Make sure to verify the IP addresses and update them accordingly in your configuration <sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/learn-more/faq/install-faq.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:13:47 -05:00
Author
Owner
Copy Link
Copy Source

@tonyliu088 commented on GitHub (Oct 11, 2024):

but /docker-api-1 has 2 ips ?how to setup

@tonyliu088 commented on GitHub (Oct 11, 2024): but /docker-api-1 has 2 ips ?how to setup
yindo commented 2026-02-21 18:13:48 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 11, 2024):

If /docker-api-1 has two IP addresses, you can set up Nginx to use one of them or configure load balancing. Here's how you can handle it:

  1. Choose One IP: If one IP is preferred, update the proxy_pass with that IP:

    location /v1 {
    proxy_pass http://<chosen-ip>:5001;
    include proxy.conf;
}

  2. Load Balancing: If you want to use both IPs, you can set up a simple load balancing configuration:

    upstream api_backend {
    server 192.168.192.7:5001;
    server 192.168.208.4:5001;
}

location /v1 {
    proxy_pass http://api_backend;
    include proxy.conf;
}

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

This setup will distribute requests between the two IPs. Adjust the IPs in the configuration to match your actual container IPs.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Oct 11, 2024): <!-- Answer --> If `/docker-api-1` has two IP addresses, you can set up Nginx to use one of them or configure load balancing. Here's how you can handle it: 1. **Choose One IP**: If one IP is preferred, update the `proxy_pass` with that IP: ```nginx location /v1 { proxy_pass http://<chosen-ip>:5001; include proxy.conf; } ``` 2. **Load Balancing**: If you want to use both IPs, you can set up a simple load balancing configuration: ```nginx upstream api_backend { server 192.168.192.7:5001; server 192.168.208.4:5001; } location /v1 { proxy_pass http://api_backend; include proxy.conf; } ``` 3. **Restart Nginx**: After updating the configuration, restart the Nginx container to apply the changes. This setup will distribute requests between the two IPs. Adjust the IPs in the configuration to match your actual container IPs. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:13:48 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Oct 11, 2024):

This is only for bug report, if you would like to ask a question, please head to Discussions.

@crazywoola commented on GitHub (Oct 11, 2024): This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🙋‍♂️ question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#6036
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?