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

New Issue
Closed
opened 2026-02-21 19:11:53 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:11:53 -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

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 <img width="1510" alt="Image" src="https://github.com/user-attachments/assets/77007ad0-aa0d-441d-b998-a8f58051caa1" /> ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:11:53 -05:00
yindo closed this issue 2026-02-21 19:11:53 -05:00
yindo commented 2026-02-21 19:11:53 -05:00
Author
Owner
Copy Link
Copy Source

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

I found similar threads that might be relevant to your issue:

  1. Docker Dify works fine for a while then can't access - This discussion is open and suggests checking port configurations and ensuring all Docker containers are running correctly [1].

  2. connection error: request error, status_code: 503 - This discussion is open and recommends verifying environment variables and Nginx configuration [2].

To resolve the issue of the Dify backend running but being inaccessible in the browser, ensure 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 [3].

If Nginx is running on your system, stop it using sudo systemctl stop nginx, then restart the Dify containers with docker compose up -d [4]. If you encounter a PluginDaemonInternalServerError: killed by timeout error, add PLUGIN_MAX_EXECUTION_TIMEOUT: 2400 to your docker-compose.yaml file [5].

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 that might be relevant to your issue: 1. **[Docker Dify works fine for a while then can't access](https://github.com/langgenius/dify/discussions/15480)** - This discussion is open and suggests checking port configurations and ensuring all Docker containers are running correctly <sup>[[1]](https://github.com/langgenius/dify/discussions/15480)</sup>. 2. **[connection error: request error, status_code: 503](https://github.com/langgenius/dify/discussions/6181)** - This discussion is open and recommends verifying environment variables and Nginx configuration <sup>[[2]](https://github.com/langgenius/dify/discussions/6181)</sup>. To resolve the issue of the Dify backend running but being inaccessible in the browser, ensure 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 <sup>[[3]](https://github.com/langgenius/dify/issues/16324)</sup>. If Nginx is running on your system, stop it using `sudo systemctl stop nginx`, then restart the Dify containers with `docker compose up -d` <sup>[[4]](https://github.com/langgenius/dify-docs/issues/421)</sup>. If you encounter a `PluginDaemonInternalServerError: killed by timeout` error, add `PLUGIN_MAX_EXECUTION_TIMEOUT: 2400` to your `docker-compose.yaml` file <sup>[[5]](https://github.com/langgenius/dify/issues/15407)</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/62eca3a7-4a49-4b86-8cce-8ac7c7af3ab7?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/62eca3a7-4a49-4b86-8cce-8ac7c7af3ab7?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/62eca3a7-4a49-4b86-8cce-8ac7c7af3ab7?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/62eca3a7-4a49-4b86-8cce-8ac7c7af3ab7?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/62eca3a7-4a49-4b86-8cce-8ac7c7af3ab7?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/62eca3a7-4a49-4b86-8cce-8ac7c7af3ab7?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/62eca3a7-4a49-4b86-8cce-8ac7c7af3ab7?feedback_type=other)</sup>
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 🐞 bug
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#13376
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?