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

Published app webapp link timing out (took too long to respond) #8131

New Issue
Closed
opened 2026-02-21 18:24:06 -05:00 by yindo · 7 comments
yindo commented 2026-02-21 18:24:06 -05:00
Owner
Copy Link
Copy Source

Originally created by @lema-founders on GitHub (Feb 10, 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

0.15.3

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

Image

App was published successfully but accessing the link (directly and embedded on another website doesn't work) http://34.145.91.111/chat/PNYbp8MV9DNxbOYG

Image

✔️ Expected Behavior

Showing published Dify app where user can send messages and receive responses from it (i.e. chatting with an LLM-powered chatbot)

❌ Actual Behavior

This site can’t be reached
34.145.91.111 took too long to respond.
Try:

Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_CONNECTION_TIMED_OUT

Originally created by @lema-founders on GitHub (Feb 10, 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 0.15.3 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/c5f887d1-4c06-466b-bedc-f6a272e6eadb) App was published successfully but accessing the link (directly and embedded on another website doesn't work) http://34.145.91.111/chat/PNYbp8MV9DNxbOYG ![Image](https://github.com/user-attachments/assets/04b078d8-1c14-4de8-b2f3-a6ca5af2bf80) ### ✔️ Expected Behavior Showing published Dify app where user can send messages and receive responses from it (i.e. chatting with an LLM-powered chatbot) ### ❌ Actual Behavior This site can’t be reached 34.145.91.111 took too long to respond. Try: Checking the connection [Checking the proxy and the firewall](chrome-error://chromewebdata/#buttons) [Running Windows Network Diagnostics](javascript:diagnoseErrors()) ERR_CONNECTION_TIMED_OUT
yindo added the 🐞 bug🤔 cant-reproduce labels 2026-02-21 18:24:06 -05:00
yindo closed this issue 2026-02-21 18:24:07 -05:00
yindo commented 2026-02-21 18:24:07 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 10, 2025):

Hey @lema-founders! I'm here to assist you with any bugs, questions, or contributions you have. Just let me know how I can help!

I found a similar closed issue where a user reported being unable to access their Dify app, but no solution was found in the comments [1].

For your issue, here are some troubleshooting steps you can consider:

  1. Network Configuration: Ensure that your network configuration allows external access. Check if the necessary ports are open and properly forwarded. Dify uses Docker Compose for IP address binding and port configuration. Make sure the relevant ports are exposed in your docker-compose.yaml file [2].

  2. Timeout Settings: Adjust the timeout settings in your .env file. You can configure environment variables like HTTP_REQUEST_MAX_CONNECT_TIMEOUT, HTTP_REQUEST_MAX_READ_TIMEOUT, and HTTP_REQUEST_MAX_WRITE_TIMEOUT to increase the timeout duration [3].

  3. Logs and Error Messages: Check the logs for any specific error messages that might indicate the cause of the timeout. Look for messages like "Requests rate limit exceeded" or "Worker was sent SIGKILL" which can help diagnose the issue [4].

  4. Firewall and Proxy Settings: Verify that your firewall and proxy settings are not blocking the connection. Ensure that the server hosting the Dify app has internet access and that there are no restrictions preventing access to the app [5].

These steps should help you identify and resolve the connection timeout issue with your self-hosted Dify app.

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Feb 10, 2025): <!-- Greeting --> Hey @lema-founders! I'm here to assist you with any bugs, questions, or contributions you have. Just let me know how I can help! <!-- Answer --> I found a similar closed issue where a user reported being unable to access their Dify app, but no solution was found in the comments <sup>[[1]](https://github.com/langgenius/dify/issues/536)</sup>. For your issue, here are some troubleshooting steps you can consider: 1. **Network Configuration**: Ensure that your network configuration allows external access. Check if the necessary ports are open and properly forwarded. Dify uses Docker Compose for IP address binding and port configuration. Make sure the relevant ports are exposed in your `docker-compose.yaml` file <sup>[[2]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup>. 2. **Timeout Settings**: Adjust the timeout settings in your `.env` file. You can configure environment variables like `HTTP_REQUEST_MAX_CONNECT_TIMEOUT`, `HTTP_REQUEST_MAX_READ_TIMEOUT`, and `HTTP_REQUEST_MAX_WRITE_TIMEOUT` to increase the timeout duration <sup>[[3]](https://github.com/langgenius/dify/issues/12880)</sup>. 3. **Logs and Error Messages**: Check the logs for any specific error messages that might indicate the cause of the timeout. Look for messages like "Requests rate limit exceeded" or "Worker was sent SIGKILL" which can help diagnose the issue <sup>[[4]](https://github.com/langgenius/dify/issues/11694)</sup>. 4. **Firewall and Proxy Settings**: Verify that your firewall and proxy settings are not blocking the connection. Ensure that the server hosting the Dify app has internet access and that there are no restrictions preventing access to the app <sup>[[5]](https://github.com/langgenius/dify-docs/blob/main/en/guides/workflow/error-handling/error-type.md)</sup>. These steps should help you identify and resolve the connection timeout issue with your self-hosted Dify app. <!-- 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/5009bcb2-87b4-401c-9226-208b5993583d?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/5009bcb2-87b4-401c-9226-208b5993583d?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/5009bcb2-87b4-401c-9226-208b5993583d?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/5009bcb2-87b4-401c-9226-208b5993583d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5009bcb2-87b4-401c-9226-208b5993583d?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/5009bcb2-87b4-401c-9226-208b5993583d?feedback_type=other)</sup>
yindo commented 2026-02-21 18:24:07 -05:00
Author
Owner
Copy Link
Copy Source

@lema-founders commented on GitHub (Feb 11, 2025):

Adding ports to firewall changed the error from connection timed out to 404 error

Image

@lema-founders commented on GitHub (Feb 11, 2025): Adding ports to firewall changed the error from connection timed out to 404 error ![Image](https://github.com/user-attachments/assets/a2d72a91-e015-4fb0-b10a-a0eb70b26f1b)
yindo commented 2026-02-21 18:24:07 -05:00
Author
Owner
Copy Link
Copy Source

@lema-founders commented on GitHub (Feb 11, 2025):

Image

docker nginx log shows 404 when accessing robots.txt and sitemap.xml, is this expected? @crazywoola

@lema-founders commented on GitHub (Feb 11, 2025): ![Image](https://github.com/user-attachments/assets/1d990bc7-cbc5-49eb-94d8-3febfea60dbd) docker nginx log shows 404 when accessing robots.txt and sitemap.xml, is this expected? @crazywoola
yindo commented 2026-02-21 18:24:07 -05:00
Author
Owner
Copy Link
Copy Source

@lema-founders commented on GitHub (Feb 11, 2025):

I made the robots.txt and sitemap.xml so there's not more 404 error in the logs (http://34.145.91.111:8888/robots.txt accessible here for example), but http://34.145.91.111/chat/PNYbp8MV9DNxbOYG still returns 404 page not found

Image

@lema-founders commented on GitHub (Feb 11, 2025): I made the robots.txt and sitemap.xml so there's not more 404 error in the logs (http://34.145.91.111:8888/robots.txt accessible here for example), but http://34.145.91.111/chat/PNYbp8MV9DNxbOYG still returns 404 page not found ![Image](https://github.com/user-attachments/assets/9442e6f0-5560-4e27-8af6-11cd5fa27a1f)
yindo commented 2026-02-21 18:24:07 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 11, 2025):

The files you added are not related to what you are experiencing.
Actually I am not sure why you are facing this.
I saw you wrote Source code.
Since you can see the console of dify, I suppose you haven't configure the env vars correct according to https://docs.dify.ai/getting-started/install-self-hosted/environments
Can you provide the detailed steps to start dify?

@crazywoola commented on GitHub (Feb 11, 2025): The files you added are not related to what you are experiencing. Actually I am not sure why you are facing this. I saw you wrote `Source code`. Since you can see the console of dify, I suppose you haven't configure the env vars correct according to https://docs.dify.ai/getting-started/install-self-hosted/environments Can you provide the detailed steps to start dify?
yindo commented 2026-02-21 18:24:07 -05:00
Author
Owner
Copy Link
Copy Source

@lema-founders commented on GitHub (Feb 12, 2025):

Reinstalling Dify from scratch did the trick - we missed some installation steps. The app link now loads (http://34.145.91.111/chat/PNYbp8MV9DNxbOYG) but the embedded webapp still doesn't show up (in https://www.lema-app.com/chat), @crazywoola do you know how to fix it?

This is the code in page.tsx for the Chat page (https://www.lema-app.com/chat)
export default function ChatPage() { return ( <div className="flex flex-col min-h-screen"> <main className="flex-1"> <section className="w-full py-6 sm:py-12 md:py-24"> <div className="container px-4 md:px-6"> <div className="max-w-[900px] mx-auto"> <h1 className="text-3xl font-bold tracking-tighter sm:text-4xl md:text-5xl mb-6"> Chat Application </h1> <iframe src="http://34.145.91.111/chatbot/6nvhPPQgMYhgY82T" style={{ width: '100%', height: '700px', border: 'none' }} allow="microphone" /> </div> </div> </section> </main> </div> ); }

@lema-founders commented on GitHub (Feb 12, 2025): Reinstalling Dify from scratch did the trick - we missed some installation steps. The app link now loads (http://34.145.91.111/chat/PNYbp8MV9DNxbOYG) but the embedded webapp still doesn't show up (in https://www.lema-app.com/chat), @crazywoola do you know how to fix it? This is the code in page.tsx for the Chat page (https://www.lema-app.com/chat) `export default function ChatPage() { return ( <div className="flex flex-col min-h-screen"> <main className="flex-1"> <section className="w-full py-6 sm:py-12 md:py-24"> <div className="container px-4 md:px-6"> <div className="max-w-[900px] mx-auto"> <h1 className="text-3xl font-bold tracking-tighter sm:text-4xl md:text-5xl mb-6"> Chat Application </h1> <iframe src="http://34.145.91.111/chatbot/6nvhPPQgMYhgY82T" style={{ width: '100%', height: '700px', border: 'none' }} allow="microphone" /> </div> </div> </section> </main> </div> ); }`
yindo commented 2026-02-21 18:24:08 -05:00
Author
Owner
Copy Link
Copy Source

@lema-founders commented on GitHub (Feb 13, 2025):

Changing the embed link to https works, closing this issue.. Thank you!

@lema-founders commented on GitHub (Feb 13, 2025): Changing the embed link to https works, closing this issue.. Thank you!
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#8131
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?