Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #1875] [BUG]: llama 3 cannot be found for local installed ollama #1219

New Issue
Closed
opened 2026-02-22 18:23:46 -05:00 by yindo · 2 comments
yindo commented 2026-02-22 18:23:46 -05:00
Owner
Copy Link
Copy Source

Originally created by @byzheng on GitHub (Jul 15, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1875

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

I freshly installed anything-llm in my Windows 11 laptop.

It is working for LLM Providers, Anything-LLM with llama3, but very slow (no GPU usage)

Following the suggestions (https://github.com/Mintplex-Labs/anything-llm/issues/1398), I separately installed ollama and pull model with ollama pull llama3 which is working on command line.

Then I configure LLM Providers in Anything LLM to select model llama3-latest. However, I get an error message.

Ollama call failed with status code 404: model "llama2" not found, try pulling it first

Are there known steps to reproduce?

No response

Originally created by @byzheng on GitHub (Jul 15, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1875 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? I freshly installed anything-llm in my Windows 11 laptop. It is working for LLM Providers, Anything-LLM with llama3, but very slow (no GPU usage) Following the suggestions (https://github.com/Mintplex-Labs/anything-llm/issues/1398), I separately installed ollama and pull model with `ollama pull llama3` which is working on command line. Then I configure LLM Providers in Anything LLM to select model llama3-latest. However, I get an error message. ``` Ollama call failed with status code 404: model "llama2" not found, try pulling it first ``` ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-02-22 18:23:46 -05:00
yindo closed this issue 2026-02-22 18:23:46 -05:00
yindo commented 2026-02-22 18:23:46 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jul 16, 2024):

Open your LLM prefs, select another model (if one is not selected) and reselect what you intended to use - seems that it did not save your config during onboarding

@timothycarambat commented on GitHub (Jul 16, 2024): Open your LLM prefs, select another model (if one is not selected) and reselect what you intended to use - seems that it did not save your config during onboarding
yindo commented 2026-02-22 18:23:46 -05:00
Author
Owner
Copy Link
Copy Source

@fsiler commented on GitHub (Dec 17, 2024):

I am having this same issue and reselecting the model did not help. Win 11 Pro x86, Ollama, hoping to use llama3.2 and get same error.

@fsiler commented on GitHub (Dec 17, 2024): I am having this same issue and reselecting the model did not help. Win 11 Pro x86, Ollama, hoping to use llama3.2 and get same error.
yindo changed title from [BUG]: llama 3 cannot be found for local installed ollama to [GH-ISSUE #1875] [BUG]: llama 3 cannot be found for local installed ollama 2026-06-05 14:39:35 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label possible 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: Mintplex-Labs/anything-llm#1219
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?