When using version 1.0.0 and trying to save a key, the SiliconFlow plugin does not save

[thinwonton]

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

1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When using version 1.0.0 and trying to save a key, the SiliconFlow plugin does not save.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[CorrectRoadH]

同遇到了

[sqkkyzx]

同样遇到，我没法保存任何模型提供商的配置

[maruilav]

me too

[BinaryCheater]

me too, in fact I met "Internal Server Error" in every plugin, and it's also hard to install a plugin, which may stuck or fail.
There is at least 30 issues about this problem
what a critical bug.

[50ZAIofficial]

me too, so sad :(

[zbaos260]

me too, in fact I met "Internal Server Error" in every plugin, and it's also hard to install a plugin, which may stuck or fail. There is at least 30 issues about this problem what a critical bug.

It seems that we can only wait for the official bug fix.

[CorrectRoadH]

Does it will be fixed in next release of dify?

[panxxpan]

Same problem here, try Global VPN, problem still there.

[AndriodStudent]

me too, so sad :() come bro!!!!!

[Yeuoly]

are there any detailed logs or screenshots of it? just try docker logs -f docker-plugin_daemon-1 or docker logs -f docker-api-1

for a temp solution if you are using internal network, adding an environment PIP_MIRROR_URL to plugin_daemon and use your mirror url like https://pypi.tuna.tsinghua.edu.cn/simple may solve the problem

[sqkkyzx]

Initially, I tried using the HTTP_PROXY and HTTPS_PROXY variables, but they didn't have any effect.

Additionally, I observed in the plugin_daemon that the dependencies have actually been installed successfully.

[Yeuoly]

Would you mind provide some logs inside both api and daemon container? As I can not reproduce this internal server error, logs are required to trace the bug

[app2smile]

The same situation.
In addition, when configuring ollama, there is also no response when saving

[Yeuoly]

The same situation. In addition, when configuring ollama, there is also no response when saving

pls add my wechat: Yeuoly, I guess we need to dig it out in your environment

[app2smile]

The same situation. In addition, when configuring ollama, there is also no response when saving

pls add my wechat: Yeuoly, I guess we need to dig it out in your environment

I have solved this problem By observing the logs of the plugin, I found that the reason for this situation is that the plugin did not initialize successfully. Although the frontend shows that the plugin was installed successfully, it was actually not successful

Error log:
[ERROR]init environment failed: failed to install dependencies: signal: killed, output: init process exited due to no activity for 120 seconds, retry in 30s

Solution:
Add the following configuration line after line 560 in the docker-compose.yaml file to increase the Python environment initialization timeout (plugin_daemon)
PYTHON_ENV_INIT_TIMEOUT: 2400