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

Docker Compose deployment, completed according to the documentation process without any exception errors, but the local localhost cannot be opened #8800

New Issue
Closed
opened 2026-02-21 18:27:45 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:27:45 -05:00
Owner
Copy Link
Copy Source

Originally created by @dsbdsb26 on GitHub (Mar 1, 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

Docker Compose deployment, completed according to the documentation process without any exception errors, but the local localhost cannot be opened

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @dsbdsb26 on GitHub (Mar 1, 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 Docker Compose deployment, completed according to the documentation process without any exception errors, but the local localhost cannot be opened ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 18:27:45 -05:00
yindo closed this issue 2026-02-21 18:27:45 -05:00
yindo commented 2026-02-21 18:27:45 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 1, 2025):

I found a similar issue where users were unable to access localhost after completing a Docker Compose deployment. Here are some steps that might help resolve the issue:

  1. Check Environment Variables: Ensure that your .env file is correctly configured with the necessary API URLs. Specifically, verify that CONSOLE_API_URL, SERVICE_API_URL, and APP_API_URL are set to the correct backend URLs for your application. If they are left empty, they default to the same domain, which might not be suitable for your setup [1].

  2. Configure Server Address: If you are trying to access the application using 127.0.0.1, remember that this is the internal address of the container. You need to configure Dify's server address to be the host's local network IP address instead. Set DIFY_BIND_ADDRESS to 0.0.0.0 in your .env file to allow access from external sources [1].

  3. Verify Port Configuration: Ensure that EXPOSE_NGINX_PORT and EXPOSE_NGINX_SSL_PORT are correctly set to the ports you intend to use for HTTP and HTTPS access [1].

For more detailed configuration options, you can refer to the example .env file provided in the Dify documentation. You can also check the documentation at Dify's installation guide for more details on setting these environment variables.

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 (Mar 1, 2025): <!-- Answer --> I found a similar issue where users were unable to access localhost after completing a Docker Compose deployment. Here are some steps that might help resolve the issue: 1. **Check Environment Variables**: Ensure that your `.env` file is correctly configured with the necessary API URLs. Specifically, verify that `CONSOLE_API_URL`, `SERVICE_API_URL`, and `APP_API_URL` are set to the correct backend URLs for your application. If they are left empty, they default to the same domain, which might not be suitable for your setup <sup>[[1]](https://github.com/langgenius/dify/issues/14160)</sup>. 2. **Configure Server Address**: If you are trying to access the application using `127.0.0.1`, remember that this is the internal address of the container. You need to configure Dify's server address to be the host's local network IP address instead. Set `DIFY_BIND_ADDRESS` to `0.0.0.0` in your `.env` file to allow access from external sources <sup>[[1]](https://github.com/langgenius/dify/issues/14160)</sup>. 3. **Verify Port Configuration**: Ensure that `EXPOSE_NGINX_PORT` and `EXPOSE_NGINX_SSL_PORT` are correctly set to the ports you intend to use for HTTP and HTTPS access <sup>[[1]](https://github.com/langgenius/dify/issues/14160)</sup>. For more detailed configuration options, you can refer to the example `.env` file provided in the Dify documentation. You can also check the documentation at [Dify's installation guide](https://docs.dify.ai/getting-started/install-self-hosted/environments) for more details on setting these environment variables. <!-- 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/ff185599-78c8-4913-a53e-95adb3133277?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/ff185599-78c8-4913-a53e-95adb3133277?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/ff185599-78c8-4913-a53e-95adb3133277?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/ff185599-78c8-4913-a53e-95adb3133277?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ff185599-78c8-4913-a53e-95adb3133277?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/ff185599-78c8-4913-a53e-95adb3133277?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ff185599-78c8-4913-a53e-95adb3133277?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 🤔 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#8800
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?