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 to 1.8.1, the ollama plugin cannot control whether LLM is think enabled or not #637

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

Originally created by @JAVA-LW on GitHub (Sep 10, 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.8.1

Plugin version

0.0.7

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After upgrading dify to 1.8.1, I found that my ollama big model plugin couldn't control whether the model was thinking or not. I was using qwen 30B instead.

✔️ Error log

No response

Originally created by @JAVA-LW on GitHub (Sep 10, 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.8.1 ### Plugin version 0.0.7 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce After upgrading dify to 1.8.1, I found that my ollama big model plugin couldn't control whether the model was thinking or not. I was using qwen 30B instead. ### ✔️ Error log _No response_
yindo added the bug label 2026-02-16 10:20:00 -05:00
yindo closed this issue 2026-02-16 10:20:00 -05:00
yindo commented 2026-02-16 10:20:01 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 10, 2025):

The Ollama plugin v0.0.7 does support the 'think' parameter, which lets you control whether the model uses "thinking mode"—but after upgrading to Dify 1.8.1, you may lose control over this and other model settings due to breaking changes in credential management. Migrated Ollama models can end up referencing invalid credential IDs, making them unusable or uncontrollable even if the UI looks fine. Newly created Ollama models after the upgrade work as expected because their credentials are registered correctly details.

To restore control, manually check your database: make sure each Ollama model’s credential_id in the provider_models table matches a valid entry in provider_model_credentials. If not, create a new credential entry and update the reference. Restart all related Docker containers (dify, plugin_daemon, ssrf_proxy) after making changes to clear any cache or backend state issues. Also, confirm your Ollama service is accessible from inside the Dify container and that your models are loaded in Ollama step-by-step.

If you still can't control the LLM, try creating a new Ollama model in Dify—this should work and let you pass the 'think' parameter as intended. If problems persist, check backend logs for silent errors or credential issues.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Sep 10, 2025): <!-- Answer --> The Ollama plugin v0.0.7 does support the 'think' parameter, which lets you control whether the model uses "thinking mode"—but after upgrading to Dify 1.8.1, you may lose control over this and other model settings due to breaking changes in credential management. Migrated Ollama models can end up referencing invalid credential IDs, making them unusable or uncontrollable even if the UI looks fine. Newly created Ollama models after the upgrade work as expected because their credentials are registered correctly [details](https://github.com/langgenius/dify-official-plugins/issues/1671). To restore control, manually check your database: make sure each Ollama model’s `credential_id` in the `provider_models` table matches a valid entry in `provider_model_credentials`. If not, create a new credential entry and update the reference. Restart all related Docker containers (`dify`, `plugin_daemon`, `ssrf_proxy`) after making changes to clear any cache or backend state issues. Also, confirm your Ollama service is accessible from inside the Dify container and that your models are loaded in Ollama [step-by-step](https://github.com/langgenius/dify-official-plugins/issues/1671). If you still can't control the LLM, try creating a new Ollama model in Dify—this should work and let you pass the 'think' parameter as intended. If problems persist, check backend logs for silent errors or credential issues. <!-- 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/127b31fa-08c4-4974-815c-bd93ab480df1?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/127b31fa-08c4-4974-815c-bd93ab480df1?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/127b31fa-08c4-4974-815c-bd93ab480df1?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/127b31fa-08c4-4974-815c-bd93ab480df1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/127b31fa-08c4-4974-815c-bd93ab480df1?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/127b31fa-08c4-4974-815c-bd93ab480df1?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/127b31fa-08c4-4974-815c-bd93ab480df1?feedback_type=other)</sup>&nbsp;&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/1692)
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#637
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?