Signature Verification Failure and Plugins Not Appearing After Installation When Installing Dify Plugins Offline on Windows 10

[LonyHans]

Self Checks

• I have read the Contributing Guide and Language Policy.
• 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, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

Dify version

dify 1.10.1-fix.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After deploying Dify on Windows 10, the following issues occur when attempting to install some plugins offline:

Signature Verification Error when Installing the Ollama Plugin
Error Message:
PluginDaemonBadRequestError: plugin installation blocked: this plugin claims to be from Langgenius but lacks official signature verification. Set ENFORCE_LANGGENIUS_PLUGIN_SIGNATURES=false to allow installation (not recommended)

The problem persists even after modifying FORCE_VERIFYING_SIGNATURE=false

Plugin Not Displayed After Installing Elasticsearch
Docker container logs indicate successful installation:
stdio.go:173: [INFO] plugin quicksandzn/elasticsearch:0.0.5: Installed tool: elasticsearch
However, after refreshing the Dify page, the plugin does not appear in the list.

Attempted Solutions
Modified the following configurations in the .env file:
Increased timeout settings:

PLUGIN_PYTHON_ENV_INIT_TIMEOUT=1200
PLUGIN_MAX_EXECUTION_TIMEOUT=900

Disabled signature verification:

FORCE_VERIFYING_SIGNATURE=false

Adjusted package size limits:

PLUGIN_MAX_PACKAGE_SIZE=524288000
NGINX_CLIENT_MAX_BODY_SIZE=500M

Configured PIP mirror source:

PIP_MIRROR_URL=https://mirrors.aliyun.com/pypi/simple/

Restarted the Docker containers and retried the installation, but the issues remain unresolved.

✔️ Expected Behavior

When installing plugins offline, the signature verification should either be bypassed or pass successfully.

After successful plugin installation, the plugins should be displayed normally in the Dify interface.

❌ Actual Behavior

No response

[dosubot]

Hi @LonyHans! I'm Dosu and I’m helping the dify team.

The signature verification error persists because, in recent Dify versions, you must set both FORCE_VERIFYING_SIGNATURE=false and ENFORCE_LANGGENIUS_PLUGIN_SIGNATURES=false in your .env and docker-compose.yaml files to fully disable signature checks for offline plugin installation. Setting only one of these is not enough. After updating both variables, make sure to restart all Docker containers so the changes take effect. See this discussion and PR for details.

If plugins still don't appear in the UI after logs show a successful install, it usually means the plugin wasn't registered correctly. This can happen if the plugin manifest is invalid, if there are file permission or volume mount issues (especially on Windows/Docker), or if the plugin daemon and API are out of sync. Check the plugin_daemon logs for errors, and consider enabling debug logging (DEBUG=true and LOG_LEVEL=DEBUG) to get more details.

If you continue to have issues, double-check that both environment variables are present and set to false in all relevant config files, and that the plugin_daemon container is actually running with those values (you can verify with docker inspect or by printing envs in the container). For more, see related issues and troubleshooting and code references.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}