mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
Using OpenAI-API-compatible to connect to the privately deployed full-version DeepSeek model, saving failed with an error.（ReOpen） #586
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 @JiesenSun on GitHub (Aug 25, 2025).
The project is using Dify version 1.7.1, and it does include these two configurations. However, when integrating with the privately deployed DeepSeek-671B model, it still can’t be saved. What adjustments need to be made to these two configurations?
Originally posted by @crazywoola in #1542
@dosubot[bot] commented on GitHub (Aug 25, 2025):
Adjusting
PLUGIN_STORAGE_TYPEandPYTHON_ENV_INIT_TIMEOUTalone will not resolve the saving failure with DeepSeek-671B in Dify v1.7.1. The root cause is a plugin timeout that is not user-configurable in this version—if the DeepSeek model is slow to respond, the plugin daemon is killed by the default timeout. This is a known limitation introduced after v0.15.3, along with stricter credential validation, which causes issues with private large models like DeepSeek-671B. Users have reported that downgrading to v0.15.3 resolves these problems, but that's not ideal for most setups.Other common causes include Docker network misconfiguration (make sure to use
host.docker.internalor your host's LAN IP for the endpoint, and setSANDBOX_ENABLE_NETWORK=true), and credential validation errors (double-check model name, endpoint, and API key) [source 1][source 2].Newer Dify versions (after 1.7.1) add timeout controls for plugins and MCP tools, which directly address this issue [source]. If possible, consider upgrading to a newer version for more granular timeout and buffer settings.
In summary: no adjustment to these two configs will fix the saving failure in v1.7.1; the issue is with hardcoded timeouts and stricter validation in this version. Workarounds are to upgrade Dify, patch the plugin code, or (as a last resort) downgrade to v0.15.3.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@crazywoola commented on GitHub (Aug 25, 2025):
You can make it bigger
PLUGIN_PYTHON_ENV_INIT_TIMEOUT.If you are in mainland China, please switch to https://mirrors.tuna.tsinghua.edu.cn/help/pypi/ instead.
@shihuimin1012 commented on GitHub (Sep 1, 2025):
已经做大了，但是依旧无法保存或超时5分钟就会被kil
@shihuimin1012 commented on GitHub (Sep 1, 2025):
@JiesenSun 请问你解决了吗？
我遇到类似得问题，但是不是保存时候，是调用模型时，超时就会被killed by timeout；更改参数都无效
@JiesenSun commented on GitHub (Sep 2, 2025):
Only downgrading to version 0.15.3 works; I’ve tried all other versions but none of them work. It seems that the Dify team hasn’t paid much attention to this issue. Increasing PLUGIN_PYTHON_ENV_INIT_TIMEOUT didn’t help, and Nginx reported a 599 error.