Error processing plugins installed in OSS: list installed plugins failed: plugin_unique_identifier is not valid: /<author>/<name>:<version>@<checksum> #158

Open
opened 2026-02-16 00:20:12 -05:00 by yindo · 0 comments
Owner

Originally created by @vaddenz on GitHub (Jul 10, 2025).

Self Checks

To make sure we get to you in time, please check the following :)

  • 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."

Versions

  1. dify-plugin-daemon: langgenius/dify-plugin-daemon:0.1.2-local
  2. dify-api: latest

Describe the bug
When plugin daemon deployed with OSS storage enabled, the watcher fails to list installed plugin. The error log keep showing:

watcher.go:73: [ERROR]list installed plugins failed: plugin_unique_identifier is not valid: /junjiem/mcp_see_agent:0.2.2@2b54607cf4d6a03b39cdae1425af2d8bafd4dd87f3eef6dc3eaaa945c71c2231

This issue might be caused by InstalledBucket.List method which did not treat object path prefix properly. While listing installed plugins, the returned plugin unique identifier starts with a /, fails regex test and reports the plugin_unique_identifier is not valid error. In the end, all plugins fail registration and are unable to launch.

Related code:

  1. PluginManager.handleNewLocalPlugins

  2. InstalledBucket.List

Possible related issue

  1. Run failed: [siliconflow] Error: PluginInvokeError: {"args":null,"error_type":"PluginDaemonInnerError","message":"encountered an error: invalid character '\u003c' looking for beginning of value status: 502 Bad Gateway original response: \u003chtml\u003e"} (#112)

To Reproduce

  1. Deploy a plugin daemon instance with OSS storage type, e.g. huawei-obs
  2. Install a plugin
  3. Observe the plugin daemon log output
Originally created by @vaddenz on GitHub (Jul 10, 2025). **Self Checks** To make sure we get to you in time, please check the following :) - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify-plugin-daemon/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [x] "Please do not modify this template :) and fill in all the required fields." **Versions** 1. dify-plugin-daemon: `langgenius/dify-plugin-daemon:0.1.2-local` 2. dify-api: latest **Describe the bug** When plugin daemon deployed with OSS storage enabled, the watcher fails to list installed plugin. The error log keep showing: ``` watcher.go:73: [ERROR]list installed plugins failed: plugin_unique_identifier is not valid: /junjiem/mcp_see_agent:0.2.2@2b54607cf4d6a03b39cdae1425af2d8bafd4dd87f3eef6dc3eaaa945c71c2231 ``` This issue might be caused by `InstalledBucket.List` method which did not treat object path prefix properly. While listing installed plugins, the returned plugin unique identifier starts with a `/`, fails regex test and reports the `plugin_unique_identifier is not valid` error. **In the end, all plugins fail registration and are unable to launch.** Related code: 1. [PluginManager.handleNewLocalPlugins](https://github.com/langgenius/dify-plugin-daemon/blob/33c023b37507cfc9f179d4bffbaebf70b7a00664/internal/core/plugin_manager/watcher.go#L71) 2. [InstalledBucket.List](https://github.com/langgenius/dify-plugin-daemon/blob/33c023b37507cfc9f179d4bffbaebf70b7a00664/internal/core/plugin_manager/media_transport/installed_bucket.go#L62) Possible related issue 1. #112 **To Reproduce** 1. Deploy a plugin daemon instance with OSS storage type, e.g. huawei-obs 2. Install a plugin 3. Observe the plugin daemon log output
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugin-daemon#158