Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-24 20:15:39 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #127] "Fetch failed" of what exactly ? #88

New Issue
Closed
opened 2026-02-22 18:17:50 -05:00 by yindo · 4 comments
yindo commented 2026-02-22 18:17:50 -05:00
Owner
Copy Link
Copy Source

Originally created by @pligor on GitHub (Jun 27, 2023).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/127

Many thanks for all the fixes announced today.

Using Macbook M2 Pro (Apple Silicon Chip)

Rebuilt everything from scratch using this command:
docker-compose down && docker-compose build --no-cache && docker-compose up -d

This issue is clear in this screenshot:
image

Cannot make sense if the root cause is that the system is failing to connect to websockets, or whether something else is not working
By the way how could the system connect to localhost:3000 for websockets ? I believe there is nothing listening in port 3000 and the docker configuration is not suggesting this port to be used for any connections..

Fyi System Settings seem to be setup ok

image

Originally created by @pligor on GitHub (Jun 27, 2023). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/127 Many thanks for all the fixes announced today. Using Macbook M2 Pro (Apple Silicon Chip) Rebuilt everything from scratch using this command: `docker-compose down && docker-compose build --no-cache && docker-compose up -d` This issue is clear in this screenshot: ![image](https://github.com/Mintplex-Labs/anything-llm/assets/1448173/94abef99-1913-4760-b0dc-949633dc97b3) Cannot make sense if the root cause is that the system is failing to connect to websockets, or whether something else is not working By the way how could the system connect to localhost:3000 for websockets ? I believe there is nothing listening in port 3000 and the docker configuration is not suggesting this port to be used for any connections.. Fyi System Settings seem to be setup ok ![image](https://github.com/Mintplex-Labs/anything-llm/assets/1448173/2364a873-a9d4-44d9-9f17-8f0dd53e02a5)
yindo added the question label 2026-02-22 18:17:50 -05:00
yindo closed this issue 2026-02-22 18:17:50 -05:00
yindo commented 2026-02-22 18:17:51 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 28, 2023):

fetch failed when using chroma is a nondescript error that the library returns which means the chroma instance is not accessible or not working

@timothycarambat commented on GitHub (Jun 28, 2023): fetch failed when using chroma is a nondescript error that the library returns which means the chroma instance is not accessible or not working
yindo commented 2026-02-22 18:17:51 -05:00
Author
Owner
Copy Link
Copy Source

@pligor commented on GitHub (Jun 28, 2023):

You are right. The default one is misleading.

We needed this one: CHROMA_ENDPOINT='http://host.docker.internal:8000' # Allow docker to look on host port, not container.

@pligor commented on GitHub (Jun 28, 2023): You are right. The default one is misleading. We needed this one: `CHROMA_ENDPOINT='http://host.docker.internal:8000' # Allow docker to look on host port, not container.`
yindo commented 2026-02-22 18:17:51 -05:00
Author
Owner
Copy Link
Copy Source

@nidupb commented on GitHub (Aug 2, 2023):

For anyone running in the error, here is the complete video guide for using AnythingLLM with Chroma : https://www.youtube.com/watch?v=xRIEKjOosaM&t=558s

@nidupb commented on GitHub (Aug 2, 2023): For anyone running in the error, here is the complete video guide for using AnythingLLM with Chroma : https://www.youtube.com/watch?v=xRIEKjOosaM&t=558s
yindo commented 2026-02-22 18:17:51 -05:00
Author
Owner
Copy Link
Copy Source

@jflaflamme commented on GitHub (Aug 15, 2023):

Building on @pligor comment, for host.docker.internal to work, you need to do the following on your container --add-host=host.docker.internal:host-gateway

I would recommend this instead if you are running Chroma DB server locally on docker (this can be done on running containers)

docker network connect docker_anything-llm chroma_server_1

Then update your Chroma Endpoint URL with Anything-llm UI settings (or .env) to use http://chroma_server_1:8000

image

However, I guess it would be better for most users to directly be able to reach: "host.docker.internal".
I have done a PR for the modified docker-compose and .env.example


extra_hosts:
      - "host.docker.internal:host-gateway"
@jflaflamme commented on GitHub (Aug 15, 2023): Building on @pligor comment, for ` host.docker.internal` to work, you need to do the following on your container` --add-host=host.docker.internal:host-gateway` I would recommend this instead if you are running Chroma DB server locally on docker (this can be done on running containers) `docker network connect docker_anything-llm chroma_server_1` Then update your Chroma Endpoint URL with Anything-llm UI settings (or .env) to use `http://chroma_server_1:8000` ![image](https://github.com/Mintplex-Labs/anything-llm/assets/712558/d133de4f-4d62-4397-920b-d75c4427f186) However, I guess it would be better for most users to directly be able to reach: "host.docker.internal". I have done a PR for the modified docker-compose and .env.example ``` extra_hosts: - "host.docker.internal:host-gateway" ```
yindo changed title from "Fetch failed" of what exactly ? to [GH-ISSUE #127] "Fetch failed" of what exactly ? 2026-06-05 14:33:25 -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 question
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#88
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?