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 #3310] [BUG]: When deploying AnythingLLM using docker-compose.yml and accessing directly on port 3001 without using an Nginx proxy, the error message 'Could not respond to message. An error occurred while streaming response. network error' #2128

New Issue
Closed
opened 2026-02-22 18:28:15 -05:00 by yindo · 7 comments
yindo commented 2026-02-22 18:28:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @showcup on GitHub (Feb 21, 2025).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3310

How are you running AnythingLLM?

Docker (remote machine)

What happened?

When deploying AnythingLLM using docker-compose.yml and accessing directly on port 3001 without using an Nginx proxy, the error message 'Could not respond to message. An error occurred while streaming response. network error'

docker-compose.yml

version: '3.8'
services:
  anythingllm:
    image: mintplexlabs/anythingllm
    container_name: anythingllm
    ports:
    - "3001:3001"
    cap_add:
      - SYS_ADMIN
    user: "${UID}:${GID}"
    environment:
    # Adjust for your environment
      - STORAGE_DIR=/app/server/storage
    env_file:
      - .env
    volumes:
      - ./data:/app/server/storage
      - ./.env:/app/server/.env
    restart: always
    networks:
      - anything-llm
    extra_hosts:
      - "host.docker.internal:host-gateway"
networks:
  anything-llm:
    driver: bridge

.env

LLM_PROVIDER='ollama'
EMBEDDING_MODEL_PREF='nomic-embed-text:latest'
OLLAMA_BASE_PATH='http://192.168.31.2:11434'
OLLAMA_MODEL_PREF='deepseek-r1:7b'
OLLAMA_MODEL_TOKEN_LIMIT='4096'
EMBEDDING_ENGINE='ollama'
EMBEDDING_BASE_PATH='http://192.168.31.2:11434'
EMBEDDING_MODEL_MAX_CHUNK_LENGTH='8192'
JWT_SECRET='make this a large list of random numbers and letters 20+'
STORAGE_DIR='/app/server/storage'

Error screenshot

Image

Are there known steps to reproduce?

No response

Originally created by @showcup on GitHub (Feb 21, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3310 ### How are you running AnythingLLM? Docker (remote machine) ### What happened? When deploying AnythingLLM using docker-compose.yml and accessing directly on port 3001 without using an Nginx proxy, the error message 'Could not respond to message. An error occurred while streaming response. network error' **docker-compose.yml** ```yaml version: '3.8' services: anythingllm: image: mintplexlabs/anythingllm container_name: anythingllm ports: - "3001:3001" cap_add: - SYS_ADMIN user: "${UID}:${GID}" environment: # Adjust for your environment - STORAGE_DIR=/app/server/storage env_file: - .env volumes: - ./data:/app/server/storage - ./.env:/app/server/.env restart: always networks: - anything-llm extra_hosts: - "host.docker.internal:host-gateway" networks: anything-llm: driver: bridge ``` **.env** ``` LLM_PROVIDER='ollama' EMBEDDING_MODEL_PREF='nomic-embed-text:latest' OLLAMA_BASE_PATH='http://192.168.31.2:11434' OLLAMA_MODEL_PREF='deepseek-r1:7b' OLLAMA_MODEL_TOKEN_LIMIT='4096' EMBEDDING_ENGINE='ollama' EMBEDDING_BASE_PATH='http://192.168.31.2:11434' EMBEDDING_MODEL_MAX_CHUNK_LENGTH='8192' JWT_SECRET='make this a large list of random numbers and letters 20+' STORAGE_DIR='/app/server/storage' ``` **Error screenshot** ![Image](https://github.com/user-attachments/assets/9135aa96-77e8-49b6-9007-94d2b0375007) ### Are there known steps to reproduce? _No response_
yindo added the possible bugneeds info / can't replicateinvestigating labels 2026-02-22 18:28:15 -05:00
yindo closed this issue 2026-02-22 18:28:15 -05:00
yindo commented 2026-02-22 18:28:16 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 22, 2025):

All of this looks right at first glance, can you pull the container logs during the error? This should give an indication as to what is going wrong throwing that error.

@timothycarambat commented on GitHub (Feb 22, 2025): All of this looks right at first glance, can you pull the container logs during the error? This should give an indication as to what is going wrong throwing that error.
yindo commented 2026-02-22 18:28:16 -05:00
Author
Owner
Copy Link
Copy Source

@showcup commented on GitHub (Feb 25, 2025):

All of this looks right at first glance, can you pull the container logs during the error? This should give an indication as to what is going wrong throwing that error.

Step 1: docker logs -f anythingllm, as shown below

Image

Step 2: When I type something into the chat box, the terminal automatically stops and the docker container adds a few errors

Image

@showcup commented on GitHub (Feb 25, 2025): > All of this looks right at first glance, can you pull the container logs during the error? This should give an indication as to what is going wrong throwing that error. Step 1: docker logs -f anythingllm, as shown below ![Image](https://github.com/user-attachments/assets/1f0ecd73-4602-4281-a376-d6918cdd3640) Step 2: When I type something into the chat box, the terminal automatically stops and the docker container adds a few errors ![Image](https://github.com/user-attachments/assets/583f7a6d-816c-4a20-87dc-2fe3f6043aae)
yindo commented 2026-02-22 18:28:16 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 25, 2025):

Almost certainly the pinned issue - https://github.com/Mintplex-Labs/anything-llm/issues/1331

TLDR; CPU is too old and does not support AVX2 instruction set. Can you confirm the type of CPU running the machine? This has to do with LanceDB as the vector db

@timothycarambat commented on GitHub (Feb 25, 2025): Almost certainly the pinned issue - https://github.com/Mintplex-Labs/anything-llm/issues/1331 TLDR; CPU is too old and does not support AVX2 instruction set. Can you confirm the type of CPU running the machine? This has to do with LanceDB as the vector db
yindo commented 2026-02-22 18:28:16 -05:00
Author
Owner
Copy Link
Copy Source

@showcup commented on GitHub (Feb 25, 2025):

Almost certainly the pinned issue - #1331

TLDR; CPU is too old and does not support AVX2 instruction set. Can you confirm the type of CPU running the machine? This has to do with LanceDB as the vector db

CPU model is intel I5 10400T QSRL

@showcup commented on GitHub (Feb 25, 2025): > Almost certainly the pinned issue - [#1331](https://github.com/Mintplex-Labs/anything-llm/issues/1331) > > TLDR; CPU is too old and does not support AVX2 instruction set. Can you confirm the type of CPU running the machine? This has to do with LanceDB as the vector db CPU model is intel I5 10400T QSRL
yindo commented 2026-02-22 18:28:16 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 26, 2025):

If you use another vector database solution does this error go away? Otherwise, this is something else entirely causing the container to exit.

@timothycarambat commented on GitHub (Feb 26, 2025): If you use another vector database solution does this error go away? Otherwise, this is something else entirely causing the container to exit.
yindo commented 2026-02-22 18:28:16 -05:00
Author
Owner
Copy Link
Copy Source

@showcup commented on GitHub (Feb 27, 2025):

If you use another vector database solution does this error go away? Otherwise, this is something else entirely causing the container to exit.

Ok, I will try using another vector database, think you very much .

@showcup commented on GitHub (Feb 27, 2025): > If you use another vector database solution does this error go away? Otherwise, this is something else entirely causing the container to exit. Ok, I will try using another vector database, think you very much .
yindo commented 2026-02-22 18:28:16 -05:00
Author
Owner
Copy Link
Copy Source

@pvmilk commented on GitHub (Sep 11, 2025):

If you use another vector database solution does this error go away? Otherwise, this is something else entirely causing the container to exit.

Ok, I will try using another vector database, think you very much .

@showcup any report on this? using other vector database works for you?

@pvmilk commented on GitHub (Sep 11, 2025): > > If you use another vector database solution does this error go away? Otherwise, this is something else entirely causing the container to exit. > > Ok, I will try using another vector database, think you very much . @showcup any report on this? using other vector database works for you?
yindo changed title from [BUG]: When deploying AnythingLLM using docker-compose.yml and accessing directly on port 3001 without using an Nginx proxy, the error message 'Could not respond to message. An error occurred while streaming response. network error' to [GH-ISSUE #3310] [BUG]: When deploying AnythingLLM using docker-compose.yml and accessing directly on port 3001 without using an Nginx proxy, the error message 'Could not respond to message. An error occurred while streaming response. network error' 2026-06-05 14:44:43 -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 investigating needs info / can't replicate 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#2128
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?