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

After upgrading DIFY to version 1.11.0, the Tongyi Qianwen plugin can only use version 0.0.46. Upgrading it causes errors. #904

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

Originally created by @jackleehui on GitHub (Dec 26, 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

1.11.0

Plugin version

0.1.16

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Only version 0.0.46 works; any upgrade results in errors.

Image

✔️ Error log

Image
Originally created by @jackleehui on GitHub (Dec 26, 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 1.11.0 ### Plugin version 0.1.16 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Only version 0.0.46 works; any upgrade results in errors. <img width="1440" height="527" alt="Image" src="https://github.com/user-attachments/assets/cb5db473-a734-4517-8a0a-e17e80cbb85c" /> ### ✔️ Error log <img width="1326" height="762" alt="Image" src="https://github.com/user-attachments/assets/66123cb9-2ea5-4760-b1e6-ba700fd0e783" />
yindo added the bug label 2026-02-16 10:20:54 -05:00
yindo closed this issue 2026-02-16 10:20:54 -05:00
yindo commented 2026-02-16 10:20:54 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 26, 2025):

This is a known issue with plugin upgrades in Dify: 500 Internal Server Errors often happen when the backend expects certain fields in the plugin response, but newer plugin versions (like Tongyi Qianwen >0.0.46) return data in a way that Dify 1.11.0 doesn't handle defensively. This can also be triggered by runtime panics (such as nil pointer dereference) in the plugin daemon, especially around endpoints like parameter-rules for newer models. The root cause is usually in the plugin or upstream API response, not Dify core itself.

Immediate workarounds include:

  • Double-checking your plugin configuration and credentials.
  • Using fallback/default values for expected keys in your workflow logic.
  • As a temporary fix, you can add an Nginx rule to intercept requests to /plugin/[uuid]/dispatch/model/schema and return a default JSON response to prevent backend errors:
location ~* ^/plugin/[0-9a-f-]+/dispatch/model/schema$ {
  default_type application/json;
  return 200 '{"code":0,"data":{"schema":{}},"message":"success"}';
}

After editing your Nginx config, restart the service for changes to take effect.
If the error persists, check the plugin daemon logs for more details—often the stack trace will point to a missing key or a nil pointer in the plugin code.

There is no explicit version lock in the Tongyi Qianwen plugin code, so the issue is likely due to changes in API usage or plugin dependencies that Dify 1.11.0 doesn't fully support yet. For now, staying on 0.0.46 or using the Nginx workaround is the most reliable path until a compatibility fix is released.
References: issue 1706, issue 1729.

To reply, just mention @dosu.

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

Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Dec 26, 2025): <!-- Answer --> This is a known issue with plugin upgrades in Dify: 500 Internal Server Errors often happen when the backend expects certain fields in the plugin response, but newer plugin versions (like Tongyi Qianwen >0.0.46) return data in a way that Dify 1.11.0 doesn't handle defensively. This can also be triggered by runtime panics (such as nil pointer dereference) in the plugin daemon, especially around endpoints like `parameter-rules` for newer models. The root cause is usually in the plugin or upstream API response, not Dify core itself. Immediate workarounds include: - Double-checking your plugin configuration and credentials. - Using fallback/default values for expected keys in your workflow logic. - As a temporary fix, you can add an Nginx rule to intercept requests to `/plugin/[uuid]/dispatch/model/schema` and return a default JSON response to prevent backend errors: ```nginx location ~* ^/plugin/[0-9a-f-]+/dispatch/model/schema$ { default_type application/json; return 200 '{"code":0,"data":{"schema":{}},"message":"success"}'; } ``` After editing your Nginx config, restart the service for changes to take effect. If the error persists, check the plugin daemon logs for more details—often the stack trace will point to a missing key or a nil pointer in the plugin code. There is no explicit version lock in the Tongyi Qianwen plugin code, so the issue is likely due to changes in API usage or plugin dependencies that Dify 1.11.0 doesn't fully support yet. For now, staying on 0.0.46 or using the Nginx workaround is the most reliable path until a compatibility fix is released. References: [issue 1706](https://github.com/langgenius/dify-official-plugins/issues/1706), [issue 1729](https://github.com/langgenius/dify-official-plugins/issues/1729). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/ae21c573-b280-41d1-b75c-f7813b2b2e8d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ae21c573-b280-41d1-b75c-f7813b2b2e8d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ae21c573-b280-41d1-b75c-f7813b2b2e8d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ae21c573-b280-41d1-b75c-f7813b2b2e8d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ae21c573-b280-41d1-b75c-f7813b2b2e8d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ae21c573-b280-41d1-b75c-f7813b2b2e8d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ae21c573-b280-41d1-b75c-f7813b2b2e8d?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20is%20a%20known%20issue%20with%20plugin%20upgrades%20in%20Dify%3A%20500%20Internal%20Server%20Errors%20often%20happen%20when%20the%20backend%20expects%20certain%20fields%20in%20the%20plugin%20response%2C%20but%20newer%20plugin%20versions%20%28like%20Tongyi%20Qianwen%20%3E0.0.46%29%20return%20data%20in%20a%20way%20that%20Dify%201.11.0%20doesn%27t%20handle%20defensively.%20This%20can%20also%20be%20triggered%20by%20runtime%20panics%20%28such%20as%20nil%20pointer%20dereference%29%20in%20the%20plugin%20daemon%2C%20especially%20around%20endpoints%20like%20%60parameter-rules%60%20for%20newer%20models.%20The%20root%20cause%20is%20usually%20in%20the%20plugin%20or%20upstream%20API%20response%2C%20not%20Dify%20core%20itself.%20%0A%0AImmediate%20workarounds%20include%3A%20%0A-%20Double-checking%20your%20plugin%20configuration%20and%20credentials.%0A-%20Using%20fallback/default%20values%20for%20expected%20keys%20in%20your%20workflow%20logic.%0A-%20As%20a%20temporary%20fix%2C%20you%20can%20add%20an%20Nginx%20rule%20to%20intercept%20requests%20to%20%60/plugin/%5Buuid%5D/dispatch/model/schema%60%20and%20return%20a%20default%20JSON%20response%20to%20prevent%20backend%20errors%3A%0A%0A%60%60%60nginx%0Alocation%20~%2A%20%5E/plugin/%5B0-9a-f-%5D%2B/dispatch/model/schema%24%20%7B%0A%20%20default_type%20application/json%3B%0A%20%20return%20200%20%27%7B%22code%22%3A0%2C%22data%22%3A%7B%22schema%22%3A%7B%7D%7D%2C%22message%22%3A%22success%22%7D%27%3B%0A%7D%0A%60%60%60%0AAfter%20editing%20your%20Nginx%20config%2C%20restart%20the%20service%20for%20changes%20to%20take%20effect.%20%20%0AIf%20the%20error%20persists%2C%20check%20the%20plugin%20daemon%20logs%20for%20more%20details%E2%80%94often%20the%20stack%20trace%20will%20point%20to%20a%20missing%20key%20or%20a%20nil%20pointer%20in%20the%20plugin%20code.%20%0A%0AThere%20is%20no%20explicit%20version%20lock%20in%20the%20Tongyi%20Qianwen%20plugin%20code%2C%20so%20the%20issue%20is%20likely%20due%20to%20changes%20in%20API%20usage%20or%20plugin%20dependencies%20that%20Dify%201.11.0%20doesn%27t%20fully%20support%20yet.%20For%20now%2C%20staying%20on%200.0.46%20or%20using%20the%20Nginx%20workaround%20is%20the%20most%20reliable%20path%20until%20a%20compatibility%20fix%20is%20released.%20%20%0AReferences%3A%20%5Bissue%201706%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1706%29%2C%20%5Bissue%201729%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1729%29.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify-official-plugins/issues/2339)
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#904
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?