langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

[models] Connection Error, Request timed out. #677

New Issue
Closed
opened 2026-02-16 10:20:09 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:20:09 -05:00
Owner
Copy Link
Copy Source

Originally created by @coticom on GitHub (Sep 28, 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 Dify issues & Dify Official Plugins, 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.7.2

Plugin version

1.9.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

✔️ Error log

[models] Connection Error, Request timed out.

Has anyone encountered the above problem before? How to solve it

Originally created by @coticom on GitHub (Sep 28, 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 [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/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.7.2 ### Plugin version 1.9.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="908" height="267" alt="Image" src="https://github.com/user-attachments/assets/60c01269-6c26-444f-97d4-18c159ac984d" /> ### ✔️ Error log [models] Connection Error, Request timed out. Has anyone encountered the above problem before? How to solve it
yindo added the bug label 2026-02-16 10:20:09 -05:00
yindo closed this issue 2026-02-16 10:20:09 -05:00
yindo commented 2026-02-16 10:20:10 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 28, 2025):

This timeout error is common in self-hosted Dify Docker setups and usually means the model server isn't reachable or responsive within the default 300-second timeout window. Here are the most effective troubleshooting steps:

  • Make sure your model server is running and accessible from inside the Dify Docker container. For Docker, use container names instead of localhost for inter-container communication, and confirm all containers are on the same network with correct port exposure reference.
  • Check logs for more details: run docker-compose logs api (and also check worker and plugin_daemon containers). You can increase log verbosity by setting LOG_LEVEL=DEBUG and ENABLE_REQUEST_LOGGING=True in your .env reference.
  • If you’re using plugins, ensure Docker has proper network access so dependencies can install during initialization reference.
  • Timeout errors can also be caused by hardcoded limits. In Dify 1.7.2, the plugin request timeout is fixed at 300 seconds. To increase it, you need to modify the timeout value in the relevant provider code (often in llm.py or common_openai.py inside the plugin Docker container), then rebuild the container reference reference.
  • For Windows, moving your Docker directory to the WSL filesystem (instead of NTFS) and enabling global TUN mode in your proxy (if using one) can help reference.
  • If you’re using Alibaba Bailian or DeepSeek, note that some OpenAI-compatible endpoints do not support DeepSeek, which can cause connection errors reference.

If you need to change the timeout:

  1. Enter the plugin’s Docker container.
  2. Locate the relevant file (llm.py or common_openai.py).
  3. Find the timeout parameter (usually set to 300).
  4. Change it to your desired value.
  5. Rebuild and restart the container.

If you still see timeouts after these steps, upgrading to Dify 1.8.0 may resolve some plugin timeout issues reference.

Let me know if you need more detailed instructions for any of these steps!

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Sep 28, 2025): <!-- Answer --> This timeout error is common in self-hosted Dify Docker setups and usually means the model server isn't reachable or responsive within the default 300-second timeout window. Here are the most effective troubleshooting steps: - Make sure your model server is running and accessible from inside the Dify Docker container. For Docker, use container names instead of `localhost` for inter-container communication, and confirm all containers are on the same network with correct port exposure [reference](https://github.com/langgenius/dify/issues/22100). - Check logs for more details: run `docker-compose logs api` (and also check `worker` and `plugin_daemon` containers). You can increase log verbosity by setting `LOG_LEVEL=DEBUG` and `ENABLE_REQUEST_LOGGING=True` in your `.env` [reference](https://github.com/langgenius/dify/issues/20246). - If you’re using plugins, ensure Docker has proper network access so dependencies can install during initialization [reference](https://github.com/langgenius/dify/issues/20325). - Timeout errors can also be caused by hardcoded limits. In Dify 1.7.2, the plugin request timeout is fixed at 300 seconds. To increase it, you need to modify the timeout value in the relevant provider code (often in `llm.py` or `common_openai.py` inside the plugin Docker container), then rebuild the container [reference](https://github.com/langgenius/dify-official-plugins/issues/936) [reference](https://github.com/langgenius/dify-official-plugins/issues/1705). - For Windows, moving your Docker directory to the WSL filesystem (instead of NTFS) and enabling global TUN mode in your proxy (if using one) can help [reference](https://github.com/langgenius/dify/issues/14842). - If you’re using Alibaba Bailian or DeepSeek, note that some OpenAI-compatible endpoints do not support DeepSeek, which can cause connection errors [reference](https://github.com/langgenius/dify-official-plugins/issues/498). If you need to change the timeout: 1. Enter the plugin’s Docker container. 2. Locate the relevant file (`llm.py` or `common_openai.py`). 3. Find the timeout parameter (usually set to 300). 4. Change it to your desired value. 5. Rebuild and restart the container. If you still see timeouts after these steps, upgrading to Dify 1.8.0 may resolve some plugin timeout issues [reference](https://github.com/langgenius/dify-official-plugins/issues/1512). Let me know if you need more detailed instructions for any of these steps! <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/70bcbd6c-c77f-45bb-b646-ff45579201f9?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/70bcbd6c-c77f-45bb-b646-ff45579201f9?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/70bcbd6c-c77f-45bb-b646-ff45579201f9?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/70bcbd6c-c77f-45bb-b646-ff45579201f9?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/70bcbd6c-c77f-45bb-b646-ff45579201f9?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/70bcbd6c-c77f-45bb-b646-ff45579201f9?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/70bcbd6c-c77f-45bb-b646-ff45579201f9?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/1779)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
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-official-plugins#677
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?