mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
OpenAI plugin request timeout when setting API-KEY #561
Reference in New Issue
Block a user
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?
Originally created by @icejean on GitHub (Aug 14, 2025).
Self Checks
Dify version
1.7.2
Plugin version
openai-0.2.3
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
I 'v setup proxy environment in my local docker installation of the latest Dify 1.7.2, and can access OpenAI in the containers:
But when I install OpenAI plugin from model supplier and try to set the API-KEY, it always runs to an "Request timeout" error message in a few seconds less than 15. I think there may be a bug somewhere other than the setting of proxy, because I can access OpenAI through the OpenAI-API-compatible plugin.
I'v read issue#22100, issue#20336 and issue#4186, and verify that changing the setting in .env of PLUGIN_MAX_EXECUTION_TIMEOUT takes no effect, 15 seconds is much more less than the default value 600 seconds.
So there must be something wrong in somewhere else.
✔️ Error log
Here's the log of the setting API-KEY operation:
The ssrf_proxy service log 'FIRSTUP_PARENT' indicates that ssrf_proxy did transform the request to upper proxy correctly, but the time out message of api service followed soon, in less than 15 seconds.
@dosubot[bot] commented on GitHub (Aug 30, 2025):
Hi, @icejean. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!
@icejean commented on GitHub (Aug 30, 2025):
It's O.K. with the latest version 1.8.0, thanks for your information.
@dosubot[bot] commented on GitHub (Aug 30, 2025):
Thank you for the update and confirmation that the issue is resolved in version 1.8.0. We appreciate you letting us know. We'll go ahead and close this issue now.