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

Unable to access dedify #13885

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

Originally created by @2002yxd1128 on GitHub (May 14, 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

Image

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @2002yxd1128 on GitHub (May 14, 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 ![Image](https://github.com/user-attachments/assets/123628ae-f24f-4efb-95c4-b34ef21d2ddb) ![Image](https://github.com/user-attachments/assets/ede7d043-a369-40d9-b6e2-d1a1878b7350) ![Image](https://github.com/user-attachments/assets/e41d2492-2254-4541-88fe-f186656119c4) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🤔 cant-reproduce label 2026-02-21 19:14:22 -05:00
yindo closed this issue 2026-02-21 19:14:22 -05:00
yindo commented 2026-02-21 19:14:22 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (May 14, 2025):

Please check whether you have setup the environment variables correctly according to our docs.

@crazywoola commented on GitHub (May 14, 2025): Please check whether you have setup the environment variables correctly according to our docs.
yindo commented 2026-02-21 19:14:22 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 14, 2025):

I found a similar issue related to connection timeout errors in a self-hosted Dify setup using Docker. The suggested solutions include:

  1. Check Docker Network Configuration: Ensure that the Docker containers are correctly configured to communicate over the network. Verify that the networks section in your docker-compose-template.yaml includes the necessary network settings for your setup.

  2. Verify Environment Variables: Double-check that all environment variables are correctly set in your Docker Compose file, especially those related to network settings.

  3. Service Dependencies: Ensure that all services listed under depends_on are running and healthy. You can check the health status of services using Docker's health check feature.

  4. Network Access: If you are using a proxy, try turning it off temporarily to see if it resolves the issue. Alternatively, access the installation page using http://127.0.0.1/install instead of http://localhost/install.

  5. Reinstallation: If the issue persists, consider performing a complete reinstallation of Dify, ensuring all services are correctly set up and Docker volumes are properly mounted [1][2].

These steps should help resolve the connection timeout error you're experiencing.

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 (May 14, 2025): <!-- Answer --> I found a similar issue related to connection timeout errors in a self-hosted Dify setup using Docker. The suggested solutions include: 1. **Check Docker Network Configuration**: Ensure that the Docker containers are correctly configured to communicate over the network. Verify that the `networks` section in your `docker-compose-template.yaml` includes the necessary network settings for your setup. 2. **Verify Environment Variables**: Double-check that all environment variables are correctly set in your Docker Compose file, especially those related to network settings. 3. **Service Dependencies**: Ensure that all services listed under `depends_on` are running and healthy. You can check the health status of services using Docker's health check feature. 4. **Network Access**: If you are using a proxy, try turning it off temporarily to see if it resolves the issue. Alternatively, access the installation page using `http://127.0.0.1/install` instead of `http://localhost/install`. 5. **Reinstallation**: If the issue persists, consider performing a complete reinstallation of Dify, ensuring all services are correctly set up and Docker volumes are properly mounted <sup>[[1]](https://github.com/langgenius/dify/issues/13501)</sup><sup>[[2]](https://github.com/langgenius/dify/issues/16801)</sup>. These steps should help resolve the connection timeout error you're experiencing. <!-- 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/2b262a6b-cc50-4467-a27f-707f1e7f1d67?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/2b262a6b-cc50-4467-a27f-707f1e7f1d67?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/2b262a6b-cc50-4467-a27f-707f1e7f1d67?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/2b262a6b-cc50-4467-a27f-707f1e7f1d67?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2b262a6b-cc50-4467-a27f-707f1e7f1d67?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/2b262a6b-cc50-4467-a27f-707f1e7f1d67?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2b262a6b-cc50-4467-a27f-707f1e7f1d67?feedback_type=other)</sup>
yindo commented 2026-02-21 19:14:22 -05:00
Author
Owner
Copy Link
Copy Source

@2002yxd1128 commented on GitHub (May 14, 2025):

At first I was starting the dify service normally (and later added ragflow, but both were accessible), and suddenly yesterday I couldn't access both dify and ragflow through my browser. today I stopped both services and started dedify alone and still couldn't access it, and I didn't change the config file.

@2002yxd1128 commented on GitHub (May 14, 2025): At first I was starting the dify service normally (and later added ragflow, but both were accessible), and suddenly yesterday I couldn't access both dify and ragflow through my browser. today I stopped both services and started dedify alone and still couldn't access it, and I didn't change the config file.
yindo commented 2026-02-21 19:14:22 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (May 14, 2025):

and I didn't change the config file.

I think you should sync the changes accordingly.

@crazywoola commented on GitHub (May 14, 2025): > and I didn't change the config file. I think you should sync the changes accordingly.
yindo commented 2026-02-21 19:14:22 -05:00
Author
Owner
Copy Link
Copy Source

@2002yxd1128 commented on GitHub (May 14, 2025):

Are you referring to the config file for dify that should be changed? I did change some port configurations for ragflow and used docker-compose -p ragflow up -d to prevent redis conflicts between dify and ragflow

@2002yxd1128 commented on GitHub (May 14, 2025): Are you referring to the config file for dify that should be changed? I did change some port configurations for ragflow and used docker-compose -p ragflow up -d to prevent redis conflicts between dify and ragflow
yindo commented 2026-02-21 19:14:22 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (May 14, 2025):

Are you referring to the config file for dify that should be changed? I did change some port configurations for ragflow and used docker-compose -p ragflow up -d to prevent redis conflicts between dify and ragflow

I mean you should check the newly added environment variables in .env with .env.example. Sometimes, it will affect the startup process.

@crazywoola commented on GitHub (May 14, 2025): > Are you referring to the config file for dify that should be changed? I did change some port configurations for ragflow and used docker-compose -p ragflow up -d to prevent redis conflicts between dify and ragflow I mean you should check the newly added environment variables in `.env` with `.env.example`. Sometimes, it will affect the startup process.
yindo commented 2026-02-21 19:14:23 -05:00
Author
Owner
Copy Link
Copy Source

@2002yxd1128 commented on GitHub (May 14, 2025):

Are you referring to the config file for dify that should be changed? I did change some port configurations for ragflow and used docker-compose -p ragflow up -d to prevent redis conflicts between dify and ragflow

I mean you should check the newly added environment variables in .env with .env.example. Sometimes, it will affect the startup process.
I recopied the .env.example file but it still doesn't seem to work

Image

Image

Image

Image

@2002yxd1128 commented on GitHub (May 14, 2025): > > Are you referring to the config file for dify that should be changed? I did change some port configurations for ragflow and used docker-compose -p ragflow up -d to prevent redis conflicts between dify and ragflow > > I mean you should check the newly added environment variables in `.env` with `.env.example`. Sometimes, it will affect the startup process. I recopied the .env.example file but it still doesn't seem to work ![Image](https://github.com/user-attachments/assets/91e738b4-941c-4f39-b653-335b88630568) ![Image](https://github.com/user-attachments/assets/6a582a5b-165b-4dfb-8d59-05dd74d747f3) ![Image](https://github.com/user-attachments/assets/8d9e7e3d-d89a-4109-8953-b2455af4c366) ![Image](https://github.com/user-attachments/assets/58d18e6f-ddd4-4ede-ae64-e240fc7e910a)
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#13885
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?