langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 19:50:06 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

There is a problem with the ollama configuration model #14955

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

Originally created by @YinSonglin1997 on GitHub (Jun 27, 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 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.

Dify version

1.5.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After installing the ollama plugin in the latest version of dify, when configuring the model, it prompts that the configuration is successful, but the model just doesn't display.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @YinSonglin1997 on GitHub (Jun 27, 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 [search for existing issues](https://github.com/langgenius/dify/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.5.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce After installing the ollama plugin in the latest version of dify, when configuring the model, it prompts that the configuration is successful, but the model just doesn't display. ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🤔 cant-reproduce label 2026-02-21 19:19:31 -05:00
yindo closed this issue 2026-02-21 19:19:31 -05:00
yindo commented 2026-02-21 19:19:31 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 27, 2025):

The Ollama model not displaying after a successful configuration is likely due to the plugin daemon not reporting Ollama as an available provider/model to Dify. The UI only shows models that the backend receives from the plugin daemon, so even if configuration succeeds, the model won't appear unless the daemon reports it correctly. This can happen if the plugin isn't running, isn't compatible with Dify v1.5.0, or if there are issues in the provider registration or database records.

To troubleshoot: check the plugin daemon logs and the API endpoint /plugin/{tenant}/management/models to see if Ollama is listed. Make sure the Ollama plugin is running and compatible with your Dify version. If you have database access, verify that the provider/model records for Ollama are present and enabled. Recent changes in model status handling and Ollama integration may also affect this, so reviewing recent updates or fixes (like this PR and this one) could help if you're running a very recent or custom build.

If the daemon is running and Ollama still doesn't appear, enabling debug logging on both Dify and the plugin daemon may reveal backend errors or misconfigurations that prevent the model from being listed.

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 (Jun 27, 2025): <!-- Answer --> The Ollama model not displaying after a successful configuration is likely due to the plugin daemon not reporting Ollama as an available provider/model to Dify. The UI only shows models that the backend receives from the plugin daemon, so even if configuration succeeds, the model won't appear unless the daemon reports it correctly. This can happen if the plugin isn't running, isn't compatible with Dify v1.5.0, or if there are issues in the provider registration or database records. To troubleshoot: check the plugin daemon logs and the API endpoint `/plugin/{tenant}/management/models` to see if Ollama is listed. Make sure the Ollama plugin is running and compatible with your Dify version. If you have database access, verify that the provider/model records for Ollama are present and enabled. Recent changes in model status handling and Ollama integration may also affect this, so reviewing recent updates or fixes (like [this PR](https://github.com/langgenius/dify/pull/20614) and [this one](https://github.com/langgenius/dify/pull/11449)) could help if you're running a very recent or custom build. If the daemon is running and Ollama still doesn't appear, enabling debug logging on both Dify and the plugin daemon may reveal backend errors or misconfigurations that prevent the model from being listed. <!-- 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/88f5797b-fb93-4d98-b33c-a72b52494c17?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/88f5797b-fb93-4d98-b33c-a72b52494c17?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/88f5797b-fb93-4d98-b33c-a72b52494c17?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/88f5797b-fb93-4d98-b33c-a72b52494c17?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/88f5797b-fb93-4d98-b33c-a72b52494c17?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/88f5797b-fb93-4d98-b33c-a72b52494c17?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/88f5797b-fb93-4d98-b33c-a72b52494c17?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/issues/21631)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🤔 cant-reproduce
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#14955
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?