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

[GH-ISSUE #47] Chat errors out #33

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

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

Originally assigned to: @timothycarambat on GitHub.

Installed successfully on Windows Docker Desktop.
Chroma Local Install is being used as Vector DB.
Docker build was successful.

Workspace created successfully.
Document loaded successful.

However when I try to chat, a message pops up as below...

localhost:3001 says
Could not send chat

No other error or notification.
Gets no response in chat.

Kindly help.

Originally created by @AkashCS on GitHub (Jun 14, 2023). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/47 Originally assigned to: @timothycarambat on GitHub. Installed successfully on Windows Docker Desktop. Chroma Local Install is being used as Vector DB. Docker build was successful. Workspace created successfully. Document loaded successful. However when I try to chat, a message pops up as below... localhost:3001 says Could not send chat No other error or notification. Gets no response in chat. Kindly help.
yindo added the bug label 2026-02-22 18:17:33 -05:00
yindo closed this issue 2026-02-22 18:17:33 -05:00
yindo commented 2026-02-22 18:17:34 -05:00
Author
Owner
Copy Link
Copy Source

@AkashCS commented on GitHub (Jun 14, 2023):

Anything-LLM-Error

@AkashCS commented on GitHub (Jun 14, 2023): ![Anything-LLM-Error](https://github.com/Mintplex-Labs/anything-llm/assets/34915142/194fa75c-c747-4d81-8b40-eea5d02dfacd)
yindo commented 2026-02-22 18:17:34 -05:00
Author
Owner
Copy Link
Copy Source

@lifuzu commented on GitHub (Jun 14, 2023):

+1

@lifuzu commented on GitHub (Jun 14, 2023): +1
yindo commented 2026-02-22 18:17:34 -05:00
Author
Owner
Copy Link
Copy Source

@danglingptr0x0 commented on GitHub (Jun 14, 2023):

+1

@danglingptr0x0 commented on GitHub (Jun 14, 2023): +1
yindo commented 2026-02-22 18:17:34 -05:00
Author
Owner
Copy Link
Copy Source

@rewphus commented on GitHub (Jun 14, 2023):

+1

@rewphus commented on GitHub (Jun 14, 2023): +1
yindo commented 2026-02-22 18:17:34 -05:00
Author
Owner
Copy Link
Copy Source

@veramarvin commented on GitHub (Jun 15, 2023):

Hi, I'm experiencing the same error. I'm using Windows 11

@veramarvin commented on GitHub (Jun 15, 2023): Hi, I'm experiencing the same error. I'm using Windows 11
yindo commented 2026-02-22 18:17:34 -05:00
Author
Owner
Copy Link
Copy Source

@dennisnadeau commented on GitHub (Jun 15, 2023):

+1 using Win 10, set up is working fine, localhost:3002 says "Could not send chat."

@dennisnadeau commented on GitHub (Jun 15, 2023): +1 using Win 10, set up is working fine, localhost:3002 says "Could not send chat."
yindo commented 2026-02-22 18:17:34 -05:00
Author
Owner
Copy Link
Copy Source

@sigpoggy commented on GitHub (Jun 15, 2023):

I'm on intel mac with same problem - "Could not send chat."

Discovered I did not have all the api fields in the .env file filled out properly.

That fixed the problem for me. Documentation could be improved to make this process more clear.

@sigpoggy commented on GitHub (Jun 15, 2023): I'm on intel mac with same problem - "Could not send chat." Discovered I did not have all the api fields in the .env file filled out properly. That fixed the problem for me. Documentation could be improved to make this process more clear.
yindo commented 2026-02-22 18:17:34 -05:00
Author
Owner
Copy Link
Copy Source

@kolenyo2099 commented on GitHub (Jun 16, 2023):

With all things green, I'm having the same issue with a Mac M2. Everything else supposedly went well.

@kolenyo2099 commented on GitHub (Jun 16, 2023): With all things green, I'm having the same issue with a Mac M2. Everything else supposedly went well.
yindo commented 2026-02-22 18:17:34 -05:00
Author
Owner
Copy Link
Copy Source

@tabgab commented on GitHub (Jun 16, 2023):

Unfortunately, I get the same thing after fighting through the installation on a Mac M1.

@tabgab commented on GitHub (Jun 16, 2023): Unfortunately, I get the same thing after fighting through the installation on a Mac M1.
yindo commented 2026-02-22 18:17:34 -05:00
Author
Owner
Copy Link
Copy Source

@yaronsivan commented on GitHub (Jun 18, 2023):

All things green, I'm having the same issue with a Mac M2. The installation and all worked well.

@yaronsivan commented on GitHub (Jun 18, 2023): All things green, I'm having the same issue with a Mac M2. The installation and all worked well.
yindo commented 2026-02-22 18:17:34 -05:00
Author
Owner
Copy Link
Copy Source

@subarudad commented on GitHub (Jun 18, 2023):

+1 Mac M1

@subarudad commented on GitHub (Jun 18, 2023): +1 Mac M1
yindo commented 2026-02-22 18:17:34 -05:00
Author
Owner
Copy Link
Copy Source

@jmmathieu commented on GitHub (Jun 18, 2023):

same here, installed successfully in WSL2 using Docker instructions, all green, uploaded a test doc, now getting cannot send chat error.

@jmmathieu commented on GitHub (Jun 18, 2023): same here, installed successfully in WSL2 using Docker instructions, all green, uploaded a test doc, now getting cannot send chat error.
yindo commented 2026-02-22 18:17:35 -05:00
Author
Owner
Copy Link
Copy Source

@rhafiko commented on GitHub (Jun 18, 2023):

yes, for me same message: cannot send chat error.

Looking docker log, result as Internal Server Error
curl --location 'http://localhost:3001/api/workspace/new_workspace/chat'
--header 'Content-Type: text/plain'
--data '{message: "test", mode: "query"}'

Unexpected token m in JSON at position 1 SyntaxError: Unexpected token m in JSON at position 1
at JSON.parse ()
at reqBody (/app/server/utils/http/index.js:9:12)
at /app/server/endpoints/chat.js:11:43
at Layer.handle [as handle_request] (/app/server/node_modules/express/lib/router/layer.js:95:5)
at next (/app/server/node_modules/express/lib/router/route.js:144:13)
at Route.dispatch (/app/server/node_modules/express/lib/router/route.js:114:3)
at Layer.handle [as handle_request] (/app/server/node_modules/express/lib/router/layer.js:95:5)
at /app/server/node_modules/express/lib/router/index.js:284:15
at param (/app/server/node_modules/express/lib/router/index.js:365:14)
at param (/app/server/node_modules/express/lib/router/index.js:376:14)

@rhafiko commented on GitHub (Jun 18, 2023): yes, for me same message: cannot send chat error. Looking docker log, result as Internal Server Error curl --location 'http://localhost:3001/api/workspace/new_workspace/chat' \ --header 'Content-Type: text/plain' \ --data '{message: "test", mode: "query"}' Unexpected token m in JSON at position 1 SyntaxError: Unexpected token m in JSON at position 1 at JSON.parse (<anonymous>) at reqBody (/app/server/utils/http/index.js:9:12) at /app/server/endpoints/chat.js:11:43 at Layer.handle [as handle_request] (/app/server/node_modules/express/lib/router/layer.js:95:5) at next (/app/server/node_modules/express/lib/router/route.js:144:13) at Route.dispatch (/app/server/node_modules/express/lib/router/route.js:114:3) at Layer.handle [as handle_request] (/app/server/node_modules/express/lib/router/layer.js:95:5) at /app/server/node_modules/express/lib/router/index.js:284:15 at param (/app/server/node_modules/express/lib/router/index.js:365:14) at param (/app/server/node_modules/express/lib/router/index.js:376:14)
yindo commented 2026-02-22 18:17:35 -05:00
Author
Owner
Copy Link
Copy Source

@jkrobin commented on GitHub (Jun 21, 2023):

I'm getting the same "Could not send chat" on M1 Mac with docker install. All API variables show green in the UI.

I do see the following in the docker log:

PineconeClient: Error calling describeIndex: 404: Not Found [PineconeError: PineconeClient: Error calling describeIndex: 404: Not Found]

and

SELECT * FROM workspaces WHERE slug = 'jkr-anything-test-1'
SELECT * FROM workspace_documents WHERE workspaceId = 1 
Request failed with status code 429 Error: Request failed with status code 429
    at createError (/app/server/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/app/server/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/app/server/node_modules/axios/lib/adapters/http.js:322:11)
    at IncomingMessage.emit (node:events:525:35)
    at endReadableNT (node:internal/streams/readable:1359:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

Any suggestions welcome!

ALSO... can someone tell me if the pinecone index name in .env should the short name (e.g. "anything-test") or the long name (e.g. "anything-test-2aa184a.svc.us-west1-gcp-free.pinecone.io") shown in the Pinecone console?

Thanks!

@jkrobin commented on GitHub (Jun 21, 2023): I'm getting the same "Could not send chat" on M1 Mac with docker install. All API variables show green in the UI. I do see the following in the docker log: `PineconeClient: Error calling describeIndex: 404: Not Found [PineconeError: PineconeClient: Error calling describeIndex: 404: Not Found]` and ``` SELECT * FROM workspaces WHERE slug = 'jkr-anything-test-1' SELECT * FROM workspace_documents WHERE workspaceId = 1 Request failed with status code 429 Error: Request failed with status code 429 at createError (/app/server/node_modules/axios/lib/core/createError.js:16:15) at settle (/app/server/node_modules/axios/lib/core/settle.js:17:12) at IncomingMessage.handleStreamEnd (/app/server/node_modules/axios/lib/adapters/http.js:322:11) at IncomingMessage.emit (node:events:525:35) at endReadableNT (node:internal/streams/readable:1359:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) ``` Any suggestions welcome! ALSO... can someone tell me if the pinecone index name in .env should the short name (e.g. "anything-test") or the long name (e.g. "anything-test-2aa184a.svc.us-west1-gcp-free.pinecone.io") shown in the Pinecone console? Thanks!
yindo commented 2026-02-22 18:17:35 -05:00
Author
Owner
Copy Link
Copy Source

@danglingptr0x0 commented on GitHub (Jun 21, 2023):

I'm getting the same "Could not send chat" on M1 Mac with docker install. All API variables show green in the UI.

I do see the following in the docker log:

PineconeClient: Error calling describeIndex: 404: Not Found [PineconeError: PineconeClient: Error calling describeIndex: 404: Not Found]

and

SELECT * FROM workspaces WHERE slug = 'jkr-anything-test-1'
SELECT * FROM workspace_documents WHERE workspaceId = 1 
Request failed with status code 429 Error: Request failed with status code 429
    at createError (/app/server/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/app/server/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/app/server/node_modules/axios/lib/adapters/http.js:322:11)
    at IncomingMessage.emit (node:events:525:35)
    at endReadableNT (node:internal/streams/readable:1359:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

Any suggestions welcome!

ALSO... can someone tell me if the pinecone index name in .env should the short name (e.g. "anything-test") or the long name (e.g. "anything-test-2aa184a.svc.us-west1-gcp-free.pinecone.io") shown in the Pinecone console?

Thanks!

@jkrobin short name. also, I think your error is due to you picking the wrong name, since it seems to be erroring out due to a response from Pinecone and not the ui, if that makes sense

@danglingptr0x0 commented on GitHub (Jun 21, 2023): > I'm getting the same "Could not send chat" on M1 Mac with docker install. All API variables show green in the UI. > > I do see the following in the docker log: > > `PineconeClient: Error calling describeIndex: 404: Not Found [PineconeError: PineconeClient: Error calling describeIndex: 404: Not Found]` > > and > > ``` > SELECT * FROM workspaces WHERE slug = 'jkr-anything-test-1' > SELECT * FROM workspace_documents WHERE workspaceId = 1 > Request failed with status code 429 Error: Request failed with status code 429 > at createError (/app/server/node_modules/axios/lib/core/createError.js:16:15) > at settle (/app/server/node_modules/axios/lib/core/settle.js:17:12) > at IncomingMessage.handleStreamEnd (/app/server/node_modules/axios/lib/adapters/http.js:322:11) > at IncomingMessage.emit (node:events:525:35) > at endReadableNT (node:internal/streams/readable:1359:12) > at process.processTicksAndRejections (node:internal/process/task_queues:82:21) > ``` > > Any suggestions welcome! > > ALSO... can someone tell me if the pinecone index name in .env should the short name (e.g. "anything-test") or the long name (e.g. "anything-test-2aa184a.svc.us-west1-gcp-free.pinecone.io") shown in the Pinecone console? > > Thanks! @jkrobin short name. also, I think your error is due to you picking the wrong name, since it seems to be erroring out due to a response from Pinecone and not the ui, if that makes sense
yindo commented 2026-02-22 18:17:35 -05:00
Author
Owner
Copy Link
Copy Source

@ajosegun commented on GitHub (Jun 22, 2023):

@jkrobin I had the same issue today.

I used the shortname i.e 'anything-test-2aa184a.svc.us-west1-gcp-free.pinecone.io' to 'anything-test' for the index

@ajosegun commented on GitHub (Jun 22, 2023): @jkrobin I had the same issue today. I used the shortname i.e 'anything-test-2aa184a.svc.us-west1-gcp-free.pinecone.io' to '**anything-test**' for the index
yindo commented 2026-02-22 18:17:35 -05:00
Author
Owner
Copy Link
Copy Source

@jkrobin commented on GitHub (Jun 22, 2023):

Thanks to all for your input. My "Could not send chat" error was resolved after I found that my free OpenAI trial credits had expired. Once I set up a paid account on OpenAI the issue was resolved.

@jkrobin commented on GitHub (Jun 22, 2023): Thanks to all for your input. My "Could not send chat" error was resolved after I found that my free OpenAI trial credits had expired. Once I set up a paid account on OpenAI the issue was resolved.
yindo commented 2026-02-22 18:17:35 -05:00
Author
Owner
Copy Link
Copy Source

@tabgab commented on GitHub (Jun 23, 2023):

Thanks to @torkati44 for the idea. The problem is that OpenAI is not ready to handle the requests, as you do not have enough credits. I switched to a different account, and it started working. On a regular trial account, or even a 20-dollar/month chat account, you are severely rate limited. 

MODEL RPM TPM
CHAT
gpt-3.5-turbo 3 40,000

So it will throw an error. One, that is relatively uninformative, but this is the underlying cause.

Our corporate account on the other hand can do:

MODEL RPM TPM
CHAT
gpt-3.5-turbo 3,500 90,000

And it works fine with that.

@tabgab commented on GitHub (Jun 23, 2023): Thanks to @torkati44 for the idea. The problem is that OpenAI is not ready to handle the requests, as you do not have enough credits. I switched to a different account, and it started working. On a regular trial account, or even a 20-dollar/month chat account, you are severely rate limited.  | **MODEL** | **RPM** | **TPM** | | --- | --- | --- | | **CHAT** | | gpt-3.5-turbo | 3 | 40,000 | So it will throw an error. One, that is relatively uninformative, but this is the underlying cause. Our corporate account on the other hand can do: | **MODEL** | **RPM** | **TPM** | | --- | --- | --- | | CHAT | | gpt-3.5-turbo | 3,500 | 90,000 | And it works fine with that.
yindo commented 2026-02-22 18:17:35 -05:00
Author
Owner
Copy Link
Copy Source

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

Our rate limits seem fine.
A screenshot from OpenAI platform webpage:
https://platform.openai.com/account/rate-limits
image

Look what errors we get:
image

ChromaDB is not going to work with AnythingLLM after all ? Or is it something else that is the root cause of this failure here ?

@pligor commented on GitHub (Jun 24, 2023): Our rate limits seem fine. A screenshot from OpenAI platform webpage: https://platform.openai.com/account/rate-limits <img width="963" alt="image" src="https://github.com/Mintplex-Labs/anything-llm/assets/1448173/d54c16ee-ea11-4f56-8054-3fba5cf57ddf"> Look what errors we get: <img width="2538" alt="image" src="https://github.com/Mintplex-Labs/anything-llm/assets/1448173/d1eba9f2-3a50-4311-a5be-e35f6c4bad61"> ChromaDB is not going to work with AnythingLLM after all ? Or is it something else that is the root cause of this failure here ?
yindo commented 2026-02-22 18:17:35 -05:00
Author
Owner
Copy Link
Copy Source

@shrashansh commented on GitHub (Jun 24, 2023):

vectordb: unsupported platform linux_arm64. Please file a bug report at https://github.com/lancedb/lancedb/issues Error: vectordb: unsupported platform linux_arm64. Please file a bug report at https://github.com/lancedb/lancedb/issues
at getPlatformLibrary (/com.docker.devenvironments.code/server/node_modules/vectordb/native.js:25:15)
at Object. (/com.docker.devenvironments.code/server/node_modules/vectordb/native.js:33:21)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
at Module.load (node:internal/modules/cjs/loader:1119:32)
at Module._load (node:internal/modules/cjs/loader:960:12)
at Module.require (node:internal/modules/cjs/loader:1143:19)
at require (node:internal/modules/cjs/helpers:110:18)
at Object. (/com.docker.devenvironments.code/server/node_modules/vectordb/dist/index.js:29:124)
at Module._compile (node:internal/modules/cjs/loader:1256:14)

following issue. please help

@shrashansh commented on GitHub (Jun 24, 2023): vectordb: unsupported platform linux_arm64. Please file a bug report at https://github.com/lancedb/lancedb/issues Error: vectordb: unsupported platform linux_arm64. Please file a bug report at https://github.com/lancedb/lancedb/issues at getPlatformLibrary (/com.docker.devenvironments.code/server/node_modules/vectordb/native.js:25:15) at Object.<anonymous> (/com.docker.devenvironments.code/server/node_modules/vectordb/native.js:33:21) at Module._compile (node:internal/modules/cjs/loader:1256:14) at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) at Module.load (node:internal/modules/cjs/loader:1119:32) at Module._load (node:internal/modules/cjs/loader:960:12) at Module.require (node:internal/modules/cjs/loader:1143:19) at require (node:internal/modules/cjs/helpers:110:18) at Object.<anonymous> (/com.docker.devenvironments.code/server/node_modules/vectordb/dist/index.js:29:124) at Module._compile (node:internal/modules/cjs/loader:1256:14) following issue. please help
yindo commented 2026-02-22 18:17:35 -05:00
Author
Owner
Copy Link
Copy Source

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

The root cause is almost always that the .env is not setup properly or is missing values.

latest changes allow you to set .env while app is running (for those who cannot seem to set them on boot for numerous reasons). Also we just improved error messages during chat which should let you know if the service is offline, and API key is invalid, or xyz.

@timothycarambat commented on GitHub (Jun 26, 2023): The root cause is almost always that the .env is not setup properly or is missing values. latest changes allow you to set .env while app is running (for those who cannot seem to set them on boot for numerous reasons). Also we just improved error messages during chat which should let you know if the service is offline, and API key is invalid, or xyz.
yindo changed title from Chat errors out to [GH-ISSUE #47] Chat errors out 2026-06-05 14:33:06 -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 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#33
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?