-
Notifications
You must be signed in to change notification settings - Fork 10.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add ollama error #14330
Comments
Hey @xuesd! 👋 I'm here to help you squash bugs, answer questions, and even guide you on becoming a contributor. Let's tackle this issue together! I found a similar solved discussion that might help you resolve the issue with adding an Ollama configuration:
Additionally, here are some troubleshooting steps you can follow to resolve the error when adding an Ollama configuration with the local address:
These steps should help in making the Ollama service accessible from the Docker container [2]. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other |
I don't think there is a model called |
Thank you, I have abbreviated it here. Originally it was deepseek-r1:14b, which is the same mistake |
Self Checks
Dify version
1.0.0-beta
Cloud or Self Hosted
Self Hosted (Source)
Steps to reproduce
When adding the ollama configuration in the model supplier interface, the ollama is set to local 192.168.xx.xx: 11434, and the backend will prompt an error message
✔️ Expected Behavior
add ollama success
❌ Actual Behavior
the backend will prompt an error message
The text was updated successfully, but these errors were encountered: