langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Regarding the plugin erro #728

New Issue
Closed
opened 2026-02-16 10:20:19 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:20:19 -05:00
Owner
Copy Link
Copy Source

Originally created by @jf-jl on GitHub (Oct 17, 2025).

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 Dify issues & Dify Official Plugins, 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

2.0.0base2

Plugin version

langgenius/dify-plugin-daemon:0.3.0b1-local

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After downgrading from version 2.0.0 Beta 2 to 1.9, I found that all APIs stopped working. Then I restored it back to 2.0.0 Beta 2, but now the frontend frequently shows the following error message:

“Failed to parse response from plugin daemon to PluginDaemonBasicResponse [PluginListResponse], url: plugin/968d3fa7-e302-4820-926d-a6584b7d24e1/management/list.”

Image

✔️ Error log

dify-api-1.txt
dify-db-1.txt
dify-plugin_daemon-1.txt

Originally created by @jf-jl on GitHub (Oct 17, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/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. ### Dify version 2.0.0base2 ### Plugin version langgenius/dify-plugin-daemon:0.3.0b1-local ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce After downgrading from version 2.0.0 Beta 2 to 1.9, I found that all APIs stopped working. Then I restored it back to 2.0.0 Beta 2, but now the frontend frequently shows the following error message: “Failed to parse response from plugin daemon to PluginDaemonBasicResponse [PluginListResponse], url: plugin/968d3fa7-e302-4820-926d-a6584b7d24e1/management/list.” <img width="413" height="147" alt="Image" src="https://github.com/user-attachments/assets/ad7ab3ea-3ab1-4123-afc7-16881fa56f15" /> ### ✔️ Error log [dify-api-1.txt](https://github.com/user-attachments/files/22964542/dify-api-1.txt) [dify-db-1.txt](https://github.com/user-attachments/files/22964543/dify-db-1.txt) [dify-plugin_daemon-1.txt](https://github.com/user-attachments/files/22964544/dify-plugin_daemon-1.txt)
yindo added the bug label 2026-02-16 10:20:19 -05:00
yindo closed this issue 2026-02-16 10:20:19 -05:00
yindo commented 2026-02-16 10:20:19 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 2, 2025):

Hi, @jf-jl. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that downgrading from Dify 2.0.0 Beta 2 to 1.9 caused all APIs to stop working.
  • Restoring to 2.0.0 Beta 2 resulted in frequent plugin daemon response parsing errors on the frontend.
  • You are using version 2.0.0base2 with the langgenius/dify-plugin-daemon:0.3.0b1-local plugin in a self-hosted Docker setup.
  • Relevant error logs were provided for troubleshooting.
  • No further updates or comments have been made since the initial report.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here.
  • If I do not hear back within 5 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Nov 2, 2025): Hi, @jf-jl. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that downgrading from Dify 2.0.0 Beta 2 to 1.9 caused all APIs to stop working. - Restoring to 2.0.0 Beta 2 resulted in frequent plugin daemon response parsing errors on the frontend. - You are using version 2.0.0base2 with the langgenius/dify-plugin-daemon:0.3.0b1-local plugin in a self-hosted Docker setup. - Relevant error logs were provided for troubleshooting. - No further updates or comments have been made since the initial report. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of dify-official-plugins by commenting here. - If I do not hear back within 5 days, I will automatically close this issue. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#728
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?