Skip to content
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

[Bug] Unable to connect to ollama. #6

Closed
wwjCMP opened this issue May 3, 2024 · 7 comments
Closed

[Bug] Unable to connect to ollama. #6

wwjCMP opened this issue May 3, 2024 · 7 comments
Assignees

Comments

@wwjCMP
Copy link

wwjCMP commented May 3, 2024

Expected Behavior

Actual Behavior

I used http://192.168.101.19:11434, but the connection failed.

Steps to Reproduce the Problem

Specifications

  • Version: 1.2.3
  • Platform: window
  • Subsystem: linux
@taichimaeda
Copy link
Owner

Thanks for raising this.

I cannot reproduce this in my environment, so do you mind opening the devtools (Ctrl+Shift+i) and take a screenshot of whatever the error message you see in the "Console" tab?

@wwjCMP
Copy link
Author

wwjCMP commented May 18, 2024

image

@taichimaeda
Copy link
Owner

This is just my guess but 404 seems to suggest that the model is not available?

Make sure you have pulled the model in the terminal:

$ ollama pull --model llama2
$ ollama serve

@wwjCMP
Copy link
Author

wwjCMP commented May 26, 2024

The models I installed are not the standard versions, could this be the problem?

Repository owner deleted a comment from taichimaeda-ca Jun 2, 2024
@taichimaeda
Copy link
Owner

taichimaeda commented Jun 2, 2024

Thant's likely the case, do you mind letting me know the model and its version you're using so I can have a look?

@wwjCMP
Copy link
Author

wwjCMP commented Jun 2, 2024

image

@taichimaeda
Copy link
Owner

Makes sense. Since the current version of the plugin does not specify the tag, it seems to fallback to latest.

I've just pushed 48c9f28 which includes a setting to specify the model tag for Ollama. I'll release a new version after a bit more testing, hopefully this should fix it!

@taichimaeda taichimaeda self-assigned this Jun 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants