I am using a Windows Server 2022 system, server (32-core CPU, 512GB RAM, A100 80GB GPU). I initially installed Dify version 1.8. Recently, Dify released a trial version 1.14rc1 (unstable). Since the new version supports skill configuration, I updated it. However, after the update, I couldn’t download plugins, and it consistently showed a timeout. I tried to fix it, and the methods I attempted include:
- Increased configuration time:
PYTHON_ENV_INIT_TIMEOUT: ${PLUGIN_PYTHON_ENV_INIT_TIMEOUT:-420}
PLUGIN_MAX_EXECUTION_TIMEOUT: ${PLUGIN_MAX_EXECUTION_TIMEOUT:-1000} - Modified the third-party download source URL:
PIP_MIRROR_URL=https://mirrors.aliyun.com/pypi/simple - Modified the MTU value
None of the above methods worked. Then I shut down the new version and opened my old version’s container, only to find that the old container’s data was lost, and all plugins were gone.
4. Each time I download a plugin, to prevent timeout tasks from locking up and affecting subsequent operations, I clear the timed-out tasks using a command:
For example: curl -X POST “http://plugin_daemon:5002/plugin/0bbd24bf-9506-4c16-8820-b41990a8b870/management/install/tasks/delete_all” -H ‘X-Api-Key: lYkiYYT6owG+71oLerGzA7GXCgOT++7ovaezWAjpCjf+Sjc3ZtU+qUEi’
Then I cleared all containers and datasets in Docker, intending to reinstall Dify. The first time I installed the stable latest version 1.13, but plugins still couldn’t be downloaded. Then I installed the old version 1.8, and still couldn’t download plugins. (Not being able to download plugins means download timeouts; even if occasionally successful, the Ollama plugin cannot add models, and the error log shows that the plugin was not correctly loaded into the registry).
However, on my personal computer (not a server), performing the same update operations had no issues at all. The server uses a wired connection in the data center, while the laptop uses Wi-Fi.
Question: Why did the initial old version download plugins without any problems, but after updating to the trial version, all Dify versions now experience plugin download timeouts, and this issue remains unresolved?
Error as shown in the figure:
