Adjusted 'timeout': Timeout (615.0, read=600.0, write=10.0, connect=5.0), "max_retries": 1, Not effective #296

Closed
opened 2026-02-16 10:18:51 -05:00 by yindo · 18 comments
Owner

Originally created by @kuku-jiusgan on GitHub (May 19, 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.1.3

Plugin version

0.0.16

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

当模型300S内没有输出时,会这样报错,但当我修改了 credentials_kwargs = {
"api_key": credentials['openai_api_key'],
"timeout": Timeout(615.0, read=600.0, write=10.0, connect=5.0),
"max_retries": 3,
}中的read为600后,没有生效

✔️ Error log

[openai_api_compatible] Error: PluginInvokeError: {"args":{},"error_type":"ConnectionError","message":"HTTPConnectionPool(host='10.0.0.111', port=10002): Read timed out."}

Originally created by @kuku-jiusgan on GitHub (May 19, 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)). - [ ] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.1.3 ### Plugin version 0.0.16 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 当模型300S内没有输出时,会这样报错,但当我修改了 credentials_kwargs = { "api_key": credentials['openai_api_key'], "timeout": Timeout(615.0, read=600.0, write=10.0, connect=5.0), "max_retries": 3, }中的read为600后,没有生效 ### ✔️ Error log [openai_api_compatible] Error: PluginInvokeError: {"args":{},"error_type":"ConnectionError","message":"HTTPConnectionPool(host='10.0.0.111', port=10002): Read timed out."}
yindo added the bug label 2026-02-16 10:18:51 -05:00
yindo closed this issue 2026-02-16 10:18:51 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Aug 17, 2025):

Hi, @kuku-jiusgan. I'm Dosu (https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a "Read timed out" ConnectionError after 300 seconds despite increasing read timeout to 600 seconds and setting max_retries to 3.
  • This happens in your self-hosted Docker environment using Dify v1.1.3 and plugin v0.0.16.
  • No further updates or comments have been provided since the initial report.
  • The issue remains unresolved.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here.
  • If I don’t hear back within 5 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 17, 2025): Hi, @kuku-jiusgan. I'm Dosu (https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a "Read timed out" ConnectionError after 300 seconds despite increasing read timeout to 600 seconds and setting max_retries to 3. - This happens in your self-hosted Docker environment using Dify v1.1.3 and plugin v0.0.16. - No further updates or comments have been provided since the initial report. - The issue remains unresolved. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here. - If I don’t hear back within 5 days, I will automatically close this issue. Thank you for your understanding and contribution!
Author
Owner

@1107186916 commented on GitHub (Aug 18, 2025):

Has it been solved? I have the same problem with the Qwen2.5-72B-Instruct-128K model of siliconflow.

my dify is 1.7.1

SiliconFlow plugins is 0.0.15

Image
@1107186916 commented on GitHub (Aug 18, 2025): Has it been solved? I have the same problem with the Qwen2.5-72B-Instruct-128K model of siliconflow. my dify is 1.7.1 SiliconFlow plugins is 0.0.15 <img width="1919" height="580" alt="Image" src="https://github.com/user-attachments/assets/95f07d26-6cf2-4a51-b906-80cbba98b3e7" />
Author
Owner

@dosubot[bot] commented on GitHub (Aug 18, 2025):

@crazywoola, could you please assist the user with their ongoing timeout issue related to the Qwen2.5-72B-Instruct-128K model in their Dify setup? They mentioned using Dify 1.7.1 and SiliconFlow plugin 0.0.15.

@dosubot[bot] commented on GitHub (Aug 18, 2025): @crazywoola, could you please assist the user with their ongoing timeout issue related to the Qwen2.5-72B-Instruct-128K model in their Dify setup? They mentioned using Dify 1.7.1 and SiliconFlow plugin 0.0.15.
Author
Owner

@shihuimin1012 commented on GitHub (Sep 12, 2025):

最终问题不解决,就一直关闭issues,你是官方吗?超时这个300,改什么都没用,好多人遇到了,这代表只要用本地模型的很多都会不好用,还不解决?

@shihuimin1012 commented on GitHub (Sep 12, 2025): 最终问题不解决,就一直关闭issues,你是官方吗?超时这个300,改什么都没用,好多人遇到了,这代表只要用本地模型的很多都会不好用,还不解决?
Author
Owner

@kuku-jiusgan commented on GitHub (Sep 12, 2025):

最终问题不解决,就一直关闭问题,你是官方吗?超时这个300,改什么都没用,好多人遇到了,这代表只要用本地模型的很多都会不好用,还不解决?

我自己已经解决,这个报错是插件的报错,要修改插件模块中的一个超时设置,但是特别麻烦,在docker环境里

@kuku-jiusgan commented on GitHub (Sep 12, 2025): > 最终问题不解决,就一直关闭问题,你是官方吗?超时这个300,改什么都没用,好多人遇到了,这代表只要用本地模型的很多都会不好用,还不解决? 我自己已经解决,这个报错是插件的报错,要修改插件模块中的一个超时设置,但是特别麻烦,在docker环境里
Author
Owner

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

@crazywoola 用户反馈最终问题未解决,超时300设置无效,且本地模型使用时仍有问题,尤其是在docker环境中,请帮忙跟进处理。

@dosubot[bot] commented on GitHub (Sep 12, 2025): @crazywoola 用户反馈最终问题未解决,超时300设置无效,且本地模型使用时仍有问题,尤其是在docker环境中,请帮忙跟进处理。
Author
Owner

@shihuimin1012 commented on GitHub (Sep 12, 2025):

问题最终没有解决,一直关闭的问题,你是官方吗?超时这个300,改什么都没用,很多人遇到了,这代表只用本地模型的很多都会用,还不好解决?

我自己已经解决了,这个报错是插件的报错,要修改插件模块中的一个超时设置,但是特别麻烦,在docker环境里

openai_api_compatible 你用的也是这个吗 请问最终如何解决的啊 我这一直超时

@shihuimin1012 commented on GitHub (Sep 12, 2025): > > 问题最终没有解决,一直关闭的问题,你是官方吗?超时这个300,改什么都没用,很多人遇到了,这代表只用本地模型的很多都会用,还不好解决? > > 我自己已经解决了,这个报错是插件的报错,要修改插件模块中的一个超时设置,但是特别麻烦,在docker环境里 openai_api_compatible 你用的也是这个吗 请问最终如何解决的啊 我这一直超时
Author
Owner

@shihuimin1012 commented on GitHub (Sep 12, 2025):

@kuku-jiusgan

@shihuimin1012 commented on GitHub (Sep 12, 2025): @kuku-jiusgan
Author
Owner

@kuku-jiusgan commented on GitHub (Sep 12, 2025):

问题最终没有解决,一直关闭的问题,你是官方吗?超时这个300,改什么都没用,很多人遇到了,这代表只用本地模型的很多都会用,还不好解决?

我自己已经解决了,这个报错是插件的报错,要修改插件模块中的一个超时设置,但是特别麻烦,在docker环境里

openai_api_compatible 你用的也是这个吗 请问最终如何解决的啊 我这一直超时

比较麻烦,进插件的docker环境,有个llm.py文件,进去找到超时相关的设置,把300改成你想要的时间就行

@kuku-jiusgan commented on GitHub (Sep 12, 2025): > > > 问题最终没有解决,一直关闭的问题,你是官方吗?超时这个300,改什么都没用,很多人遇到了,这代表只用本地模型的很多都会用,还不好解决? > > > > > > 我自己已经解决了,这个报错是插件的报错,要修改插件模块中的一个超时设置,但是特别麻烦,在docker环境里 > > openai_api_compatible 你用的也是这个吗 请问最终如何解决的啊 我这一直超时 比较麻烦,进插件的docker环境,有个llm.py文件,进去找到超时相关的设置,把300改成你想要的时间就行
Author
Owner

@shihuimin1012 commented on GitHub (Sep 16, 2025):

问题最终没有解决,一直关闭的问题,你是官方吗?超时这个300,改什么都没用,很多人遇到了,这代表只用本地模型的很多都会用,还不好解决?

我自己已经解决了,这个报错是插件的报错,要修改插件模块中的一个超时设置,但是特别麻烦,在docker环境里

openai_api_compatible 你用的也是这个吗 请问最终如何解决的啊 我这一直超时

比较麻烦,进插件的docker环境,有个llm.py文件,进去找到超时相关的设置,把300改成你想要的时间就行

请问是进入插件的docker容器内有这个代码目录,修改嘛。我修改了,未起作用;

Image Image
@shihuimin1012 commented on GitHub (Sep 16, 2025): > > > > 问题最终没有解决,一直关闭的问题,你是官方吗?超时这个300,改什么都没用,很多人遇到了,这代表只用本地模型的很多都会用,还不好解决? > > > > > > > > > 我自己已经解决了,这个报错是插件的报错,要修改插件模块中的一个超时设置,但是特别麻烦,在docker环境里 > > > > > > openai_api_compatible 你用的也是这个吗 请问最终如何解决的啊 我这一直超时 > > 比较麻烦,进插件的docker环境,有个llm.py文件,进去找到超时相关的设置,把300改成你想要的时间就行 请问是进入插件的docker容器内有这个代码目录,修改嘛。我修改了,未起作用; <img width="735" height="119" alt="Image" src="https://github.com/user-attachments/assets/c919cb6f-95f1-417b-b00b-c51b7fd0102e" /> <img width="780" height="674" alt="Image" src="https://github.com/user-attachments/assets/9e005741-5521-456d-9eb0-a97e3e25ab6f" />
Author
Owner

@shihuimin1012 commented on GitHub (Sep 16, 2025):

@kuku-jiusgan

@shihuimin1012 commented on GitHub (Sep 16, 2025): @kuku-jiusgan
Author
Owner

@kuku-jiusgan commented on GitHub (Sep 16, 2025):

@kuku-jiusgan

Image

Image

@kuku-jiusgan commented on GitHub (Sep 16, 2025): > [@kuku-jiusgan](https://github.com/kuku-jiusgan) ![Image](https://github.com/user-attachments/assets/542c19f8-0144-45b5-a7a6-c9c8e26acc8a) ![Image](https://github.com/user-attachments/assets/2915f358-db35-4ab8-93c0-9a33dbae790d)
Author
Owner

@shihuimin1012 commented on GitHub (Sep 16, 2025):

@kuku-jiusgan

Image

Image

我用的openai_api_compatible插件,和你最初的修改地方一样。但是没起作用。
我修改的models/openai_api_compatible/models/common_openai.py 文件;

当模型300S内没有输出时,会这样报错,但当我修改了 credentials_kwargs = {
"api_key": credentials['openai_api_key'],
"timeout": Timeout(615.0, read=600.0, write=10.0, connect=5.0),
"max_retries": 3,
}中的read为600后,没有生效

为何你最后修改了llm。py文件 是改用ollma了嘛

@shihuimin1012 commented on GitHub (Sep 16, 2025): > > [@kuku-jiusgan](https://github.com/kuku-jiusgan) > > ![Image](https://github.com/user-attachments/assets/542c19f8-0144-45b5-a7a6-c9c8e26acc8a) > > ![Image](https://github.com/user-attachments/assets/2915f358-db35-4ab8-93c0-9a33dbae790d) 我用的openai_api_compatible插件,和你最初的修改地方一样。但是没起作用。 **我修改的**models/openai_api_compatible/models/common_openai.py 文件; 当模型300S内没有输出时,会这样报错,但当我修改了 credentials_kwargs = { "api_key": credentials['openai_api_key'], "timeout": Timeout(615.0, read=600.0, write=10.0, connect=5.0), "max_retries": 3, }中的read为600后,没有生效 为何你最后修改了llm。py文件 是改用ollma了嘛
Author
Owner

@kuku-jiusgan commented on GitHub (Sep 16, 2025):

@kuku久岸

Image
Image

我用的openai_api_compatible插件,和你最初的修改地方一样。但是没起作用。 我修改的models/openai_api_compatible/models/common_openai.py 文件;

当模型300S内没有输出时,会这样报错,但当我修改了 credentials_kwargs = { “api_key”: credentials['openai_api_key'], “timeout”: Timeout(615.0, read=600.0, write=10.0, connect=5.0), “max_retries”: 3, }中的read为600后,没有生效

为何你最后修改了llm。py文件 是改用ollma了嘛

不是,llm.py是Dify的llm.py文件,需要进到容器里修改

Image

这是之前也是git上有个伙计问我当时的截图,然后他的路径,你可以按照这个路径找一下

@kuku-jiusgan commented on GitHub (Sep 16, 2025): > > > [@kuku久岸](https://github.com/kuku-jiusgan) > > > > > > ![Image](https://github.com/user-attachments/assets/542c19f8-0144-45b5-a7a6-c9c8e26acc8a) > > ![Image](https://github.com/user-attachments/assets/2915f358-db35-4ab8-93c0-9a33dbae790d) > > 我用的openai_api_compatible插件,和你最初的修改地方一样。但是没起作用。 **我修改的**models/openai_api_compatible/models/common_openai.py 文件; > > 当模型300S内没有输出时,会这样报错,但当我修改了 credentials_kwargs = { “api_key”: credentials['openai_api_key'], “timeout”: Timeout(615.0, read=600.0, write=10.0, connect=5.0), “max_retries”: 3, }中的read为600后,没有生效 > > 为何你最后修改了llm。py文件 是改用ollma了嘛 不是,llm.py是Dify的llm.py文件,需要进到容器里修改 <img width="681" height="447" alt="Image" src="https://github.com/user-attachments/assets/b82f22a6-8b11-43bc-b2a8-4aa6fb4c2b68" /> 这是之前也是git上有个伙计问我当时的截图,然后他的路径,你可以按照这个路径找一下
Author
Owner

@shihuimin1012 commented on GitHub (Sep 16, 2025):

@kuku久岸

Image
Image

我用的openai_api_compatible插件,和你最初的修改地方一样。但是没起作用。 我修改的models/openai_api_compatible/models/common_openai.py 文件;
当模型300S内没有输出时,会这样报错,但当我修改了 credentials_kwargs = { “api_key”: credentials['openai_api_key'], “timeout”: Timeout(615.0, read=600.0, write=10.0, connect=5.0), “max_retries”: 3, }中的read为600后,没有生效
为何你最后修改了llm。py文件 是改用ollma了嘛

不是,llm.py是Dify的llm.py文件,需要进到容器里修改

Image 这是之前也是git上有个伙计问我当时的截图,然后他的路径,你可以按照这个路径找一下

我找找,感谢;

也就是说除了修改,models/openai_api_compatible/models/common_openai.py 这个文件,还需要修改llm.py 才可以搞定这个超时是啊?而不是官方说的llm.py是ollma插件的。

Image
@shihuimin1012 commented on GitHub (Sep 16, 2025): > > > > [@kuku久岸](https://github.com/kuku-jiusgan) > > > > > > > > > ![Image](https://github.com/user-attachments/assets/542c19f8-0144-45b5-a7a6-c9c8e26acc8a) > > > ![Image](https://github.com/user-attachments/assets/2915f358-db35-4ab8-93c0-9a33dbae790d) > > > > > > 我用的openai_api_compatible插件,和你最初的修改地方一样。但是没起作用。 **我修改的**models/openai_api_compatible/models/common_openai.py 文件; > > 当模型300S内没有输出时,会这样报错,但当我修改了 credentials_kwargs = { “api_key”: credentials['openai_api_key'], “timeout”: Timeout(615.0, read=600.0, write=10.0, connect=5.0), “max_retries”: 3, }中的read为600后,没有生效 > > 为何你最后修改了llm。py文件 是改用ollma了嘛 > > 不是,llm.py是Dify的llm.py文件,需要进到容器里修改 > > <img alt="Image" width="681" height="447" src="https://private-user-images.githubusercontent.com/29033025/489982042-b82f22a6-8b11-43bc-b2a8-4aa6fb4c2b68.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTgwMTc0OTgsIm5iZiI6MTc1ODAxNzE5OCwicGF0aCI6Ii8yOTAzMzAyNS80ODk5ODIwNDItYjgyZjIyYTYtOGIxMS00M2JjLWIyYTgtNGFhNmZiNGMyYjY4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA5MTYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwOTE2VDEwMDYzOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTkzMTVkNWE2YWY5YTAyNzFlMjE5NzNmYTZiOGQwMzhjMTk4ZmEwMjAyZjBjOGY3MGFlNDhiOTE2NGI0MDQ1NmQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.aSgv7MaNYmEymhNnlDhsFtLLHiTk8BqRrmlNjwoNt3c"> > 这是之前也是git上有个伙计问我当时的截图,然后他的路径,你可以按照这个路径找一下 我找找,感谢; 也就是说除了修改,models/openai_api_compatible/models/common_openai.py 这个文件,还需要修改llm.py 才可以搞定这个超时是啊?而不是官方说的llm.py是ollma插件的。 <img width="1866" height="1044" alt="Image" src="https://github.com/user-attachments/assets/a6822b74-01da-4a83-b382-031e24c4e910" />
Author
Owner

@kuku-jiusgan commented on GitHub (Sep 16, 2025):

@shihuimin1012 是的,但是看文件路径,确实是open_api下的。 我觉得应该是ollama下也有个llmpy文件,所以 机器人有点混淆

@kuku-jiusgan commented on GitHub (Sep 16, 2025): @shihuimin1012 是的,但是看文件路径,确实是open_api下的。 我觉得应该是ollama下也有个llmpy文件,所以 机器人有点混淆
Author
Owner

@shihuimin1012 commented on GitHub (Sep 16, 2025):

@shihuimin1012 是的,但是看文件路径,确实是open_api下的。 我觉得应该是ollama下也有个llmpy文件,所以 机器人有点混淆

感谢感谢,我修改成功了,终于不是5min就timeout了

@shihuimin1012 commented on GitHub (Sep 16, 2025): > [@shihuimin1012](https://github.com/shihuimin1012) 是的,但是看文件路径,确实是open_api下的。 我觉得应该是ollama下也有个llmpy文件,所以 机器人有点混淆 感谢感谢,我修改成功了,终于不是5min就timeout了
Author
Owner

@dosubot[bot] commented on GitHub (Oct 2, 2025):

Hi, @kuku-jiusgan. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported persistent "Read timed out" errors after 300 seconds despite increasing read timeout and max_retries settings.
  • The problem occurs in a self-hosted Docker environment with Dify v1.1.3 and plugin v0.0.16.
  • You and another user found that modifying timeout settings in the plugin's llm.py file inside the Docker container is necessary.
  • Changes to common_openai.py alone do not resolve the timeout issue.
  • The issue appears resolved by directly adjusting the timeout in llm.py within the Docker container.

Next Steps:

  • Please confirm if this timeout adjustment is still relevant with the latest version of dify-official-plugins.
  • If it is, feel free to keep the discussion open by commenting; otherwise, I will automatically close this issue in 5 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Oct 2, 2025): Hi, @kuku-jiusgan. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported persistent "Read timed out" errors after 300 seconds despite increasing read timeout and max_retries settings. - The problem occurs in a self-hosted Docker environment with Dify v1.1.3 and plugin v0.0.16. - You and another user found that modifying timeout settings in the plugin's llm.py file inside the Docker container is necessary. - Changes to common_openai.py alone do not resolve the timeout issue. - The issue appears resolved by directly adjusting the timeout in llm.py within the Docker container. **Next Steps:** - Please confirm if this timeout adjustment is still relevant with the latest version of dify-official-plugins. - If it is, feel free to keep the discussion open by commenting; otherwise, I will automatically close this issue in 5 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#296