Bug: Plugin load/install error when importing DSL with plugins (self-hosted Docker)

[erbanku]

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

1.11.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Important

@crazywoola Please DO NOT mark this as a duplicate or close it right away. I’ve searched extensively, and while similar issues exist, this one is different.

1. Importing a DSL file with plugins included
2. Plugins are not installed automatically
3. UI shows 'Plugin load error' for each plugin (see screenshot)
4. Checked history issues and can't find any issue to solve this

Bug log in API container:

[GIN] 2026/01/03 - 15:36:39 | 200 |    2.041321ms |      172.18.0.2 | POST     "/plugin/526cbb9c-ffec-4d93-812a-6b4f81c917b9/dispatch/model/schema"

2026/01/03 15:37:03 /app/internal/db/executor.go:259 record not found
[0.800ms] [rows:0] SELECT * FROM "tool_installations" WHERE tenant_id = '526cbb9c-ffec-4d93-812a-6b4f81c917b9' AND plugin_id = 'langgenius/tavily' ORDER BY "tool_installations"."id" LIMIT 1
[GIN] 2026/01/03 - 15:37:03 | 200 |    1.023592ms |      172.18.0.2 | GET      "/plugin/526cbb9c-ffec-4d93-812a-6b4f81c917b9/management/tool?provider=tavily&plugin_id=langgenius%2Ftavily"

2026/01/03 15:37:03 /app/internal/db/executor.go:259 record not found
[0.397ms] [rows:0] SELECT * FROM "tool_installations" WHERE tenant_id = '526cbb9c-ffec-4d93-812a-6b4f81c917b9' AND plugin_id = 'langgenius/json_process' ORDER BY "tool_installations"."id" LIMIT 1
[GIN] 2026/01/03 - 15:37:03 | 200 |     557.369µs |      172.18.0.2 | GET      "/plugin/526cbb9c-ffec-4d93-812a-6b4f81c917b9/management/tool?provider=json_process&plugin_id=langgenius%2Fjson_process"

2026/01/03 15:37:04 /app/internal/db/executor.go:259 record not found
[0.348ms] [rows:0] SELECT * FROM "tool_installations" WHERE tenant_id = '526cbb9c-ffec-4d93-812a-6b4f81c917b9' AND plugin_id = 'langgenius/json_process' ORDER BY "tool_installations"."id" LIMIT 1

✔️ Expected Behavior

Plugins in imported DSL files should be installed automatically, without manual intervention or errors.

❌ Actual Behavior

Plugins are not installed, and a modal shows repeated 'Plugin load error' messages for each plugin when importing DSL files that contain plugins.

[erbanku]

I am not sure what is causing this (setting signature-related settings to false, changing PIP mirrors, etc., as suggested by previous issues) not to work.

Not sure if the tool_installations table schema has an issue (I think this may not be the cause):

-- Generated by the database client.
CREATE TABLE tool_installations(
    id uuid NOT NULL DEFAULT uuid_generate_v4(),
    created_at timestamp with time zone,
    updated_at timestamp with time zone,
    tenant_id uuid NOT NULL,
    provider varchar(127) NOT NULL,
    plugin_unique_identifier varchar(255),
    plugin_id varchar(255),
    PRIMARY KEY(id)
);
CREATE INDEX idx_tool_installations_plugin_id ON public.tool_installations USING btree (plugin_id);
CREATE INDEX idx_tool_installations_plugin_unique_identifier ON public.tool_installations USING btree (plugin_unique_identifier);
CREATE INDEX idx_tool_installations_provider ON public.tool_installations USING btree (provider);
CREATE INDEX idx_tool_installations_tenant_id ON public.tool_installations USING btree (tenant_id);

[dosubot]

The usual fixes like disabling signature checks or changing PIP mirrors help only if the root cause is Python package download or verification failures. In your case, the persistent "record not found" errors and plugin load failures point to deeper issues—most often with database state, Docker networking, or plugin daemon communication.

Here’s what’s most likely going wrong and what you can check next:

• If the plugin daemon and API containers aren’t on the same Docker network, or if environment variables like PLUGIN_DAEMON_URL and SANDBOX_ENABLE_NETWORK aren’t set correctly, plugin installation can silently fail—even if PIP and signature settings are fine. Make sure your containers can talk to each other and to the internet on port 443. Reference
• If the dify_plugin database or its tool_installations table is missing, corrupted, or out of sync, plugin install records won’t be created, leading to the errors you see. Sometimes, leftover or broken records from previous installs block new ones. Cleaning up the relevant records in tool_installations for your tenant, flushing Redis cache, and removing stale plugin files from Docker volumes can resolve this. Reference
• If your plugins are missing required manifest fields (like use_template, template, or scope), or are incompatible with Dify 1.11.x, installation can fail without clear error messages. Try updating your plugins to the latest versions. Reference
• Network/firewall issues or proxy misconfigurations can block the backend from fetching plugin manifests from the Dify marketplace, which is required during DSL import. Check for any outbound restrictions or SSL/proxy issues. Reference
• After Docker volume resets or environment changes, you may need to run migration commands inside your containers to sync plugin state:

  uv run flask extract-plugins --workers=20
  uv run flask install-plugins --workers=2
  uv run flask migrate-data-for-plugin
  

  Skipping these can leave the backend in an incomplete state. Reference

If you’ve checked all of the above and still see the issue, collect detailed logs from both the plugin_daemon and API containers during a failed import—look for errors beyond just "record not found" (like schema mismatches or permission errors). This will help pinpoint where the process is breaking down.

Let me know if you want step-by-step instructions for any of these checks or cleanups.

To reply, just mention @dosu.

---

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

   

[erbanku]

@dosubot Your answer is useless; try again.

[dosubot]

Here's what's actually happening under the hood: when you import a DSL file with plugins, Dify is supposed to call its PluginService, which checks permissions, fetches or downloads the plugin package, and then tells the plugin daemon to install it. If any step fails—like a permission check, a network error, or the plugin daemon not responding—no record gets created in the tool_installations table, and you get the "Plugin load error" in the UI. This is not just a UI bug; it means the backend install process never finished or never started for those plugins (source, source).

To debug this for your case:

1. Check the plugin_daemon logs (not just the API logs) right when you import the DSL. Look for permission errors, signature errors, or network failures—anything besides "record not found".
2. Make sure your system features (plugin installation scope, marketplace-only flags) allow installing the plugins referenced in your DSL. If your config restricts installs to "official only" or "marketplace only", and your plugin doesn't qualify, the install will silently fail (source).
3. Confirm that the plugin_daemon and API containers are on the same Docker network and can reach each other. If the POST to /management/install/identifiers fails, nothing gets installed (source).
4. As a test, try manually installing one of the same plugins from the Dify UI or via PluginService.install_from_marketplace_pkg. If that works, the problem is in the DSL import logic; if it fails, it's a global install/config issue.

If you see any errors in the plugin_daemon logs during the import, that's your smoking gun. If not, double-check your feature flags and permissions. This is almost always a backend install failure, not a frontend bug.

To reply, just mention @dosu.

---

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