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

Dify backend is running but inaccessible in browser. #13403

New Issue
Closed
opened 2026-02-21 19:12:02 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:12:02 -05:00
Owner
Copy Link
Copy Source

Originally created by @2002yxd1128 on GitHub (Apr 26, 2025).

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

1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

My Dify instance has been running on the server without any modifications, but one day it suddenly became inaccessible via the browser. The backend services appear to be functioning normally. What could be causing this issue?
Image

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @2002yxd1128 on GitHub (Apr 26, 2025). ### 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 1.0.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce My Dify instance has been running on the server without any modifications, but one day it suddenly became inaccessible via the browser. The backend services appear to be functioning normally. What could be causing this issue? <img width="1511" alt="Image" src="https://github.com/user-attachments/assets/9b462a51-374a-4a93-8844-61cc357bc707" /> <img width="1477" alt="Image" src="https://github.com/user-attachments/assets/8ed7b3e8-f7d7-47eb-9a36-1bed7e503b9f" /> ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🤔 cant-reproduce label 2026-02-21 19:12:02 -05:00
yindo closed this issue 2026-02-21 19:12:02 -05:00
yindo commented 2026-02-21 19:12:02 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 26, 2025):

I found similar threads discussing the issue of Dify being inaccessible in the browser despite the backend services running normally. Here are some relevant discussions and solutions:

  1. Open Issue: Dify backend is running but inaccessible in browser suggests ensuring that your environment variables in the docker-compose.yaml file are correctly configured with your server's addresses. Specifically, set variables like CONSOLE_API_URL, SERVICE_API_URL, and APP_API_URL with your actual server domain. Additionally, make sure your application is not bound to localhost but to a publicly accessible domain or IP address. If Nginx is running on your system, stop it using sudo systemctl stop nginx, then restart the Dify containers with docker compose up -d. If you encounter a PluginDaemonInternalServerError: killed by timeout error, add PLUGIN_MAX_EXECUTION_TIMEOUT: 2400 to your docker-compose.yaml file [1].

  2. Closed Issue: Prompt generator return HTTP 502 (Bad Gateway) was resolved by updating the Nginx configuration to point to the correct container IP addresses. You can check the IP addresses of your Docker containers using:

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

    Then, update the Nginx configuration in dify/docker/nginx/conf.d to use these IP addresses for the API and web services [2].

Additionally, it's important to note that version 1.0.0 of Dify has not been officially released and shows compatibility issues. It is recommended to use version v0.15.3 for production environments to avoid potential problems [3].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Apr 26, 2025): <!-- Answer --> I found similar threads discussing the issue of Dify being inaccessible in the browser despite the backend services running normally. Here are some relevant discussions and solutions: 1. **Open Issue**: [Dify backend is running but inaccessible in browser](https://github.com/langgenius/dify/issues/18820) suggests ensuring that your environment variables in the `docker-compose.yaml` file are correctly configured with your server's addresses. Specifically, set variables like `CONSOLE_API_URL`, `SERVICE_API_URL`, and `APP_API_URL` with your actual server domain. Additionally, make sure your application is not bound to `localhost` but to a publicly accessible domain or IP address. If Nginx is running on your system, stop it using `sudo systemctl stop nginx`, then restart the Dify containers with `docker compose up -d`. If you encounter a `PluginDaemonInternalServerError: killed by timeout` error, add `PLUGIN_MAX_EXECUTION_TIMEOUT: 2400` to your `docker-compose.yaml` file <sup>[[1]](https://github.com/langgenius/dify/issues/18820)</sup>. 2. **Closed Issue**: [Prompt generator return HTTP 502 (Bad Gateway)](https://github.com/langgenius/dify/issues/16453) was resolved by updating the Nginx configuration to point to the correct container IP addresses. You can check the IP addresses of your Docker containers using: ```bash docker ps -q | xargs -n 1 docker inspect --format '{{ .Name }}: {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' ``` Then, update the Nginx configuration in `dify/docker/nginx/conf.d` to use these IP addresses for the API and web services <sup>[[2]](https://github.com/langgenius/dify/issues/16453)</sup>. Additionally, it's important to note that version 1.0.0 of Dify has not been officially released and shows compatibility issues. It is recommended to use version v0.15.3 for production environments to avoid potential problems <sup>[[3]](https://github.com/langgenius/dify/issues/14016)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/7bf6598d-d13c-4fec-b8d8-f305331556f7?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/7bf6598d-d13c-4fec-b8d8-f305331556f7?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/7bf6598d-d13c-4fec-b8d8-f305331556f7?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/7bf6598d-d13c-4fec-b8d8-f305331556f7?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7bf6598d-d13c-4fec-b8d8-f305331556f7?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/7bf6598d-d13c-4fec-b8d8-f305331556f7?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7bf6598d-d13c-4fec-b8d8-f305331556f7?feedback_type=other)</sup>
yindo commented 2026-02-21 19:12:02 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 27, 2025):

I think the provided information is not sufficient to investigate, I suggest upgrading to the latest version

@crazywoola commented on GitHub (Apr 27, 2025): I think the provided information is not sufficient to investigate, I suggest upgrading to the latest version
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 🤔 cant-reproduce
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#13403
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?