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 #3178] [BUG]: Run AnythingLLM in production without Docker Find #2041

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

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

How are you running AnythingLLM?

Docker (local)

What happened?

I use BARE_METAL.md to run the project, everything is normal, but after I upload the file, it prompts an error "Response could not be completed". I use cd server && NODE_ENV=production node index.js to run the server and cd collector && NODE_ENV=production node index.js to run the file server. What is the problem?

Are there known steps to reproduce?

  1. Boot the server in production
    cd server && NODE_ENV=production node index.js &

  2. Boot the collection in another process
    cd collector && NODE_ENV=production node index.js &

  3. enter it and uploard file

Originally created by @AIxiaoHanBao on GitHub (Feb 11, 2025). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/3178 ### How are you running AnythingLLM? Docker (local) ### What happened? I use BARE_METAL.md to run the project, everything is normal, but after I upload the file, it prompts an error "Response could not be completed". I use cd server && NODE_ENV=production node index.js to run the server and cd collector && NODE_ENV=production node index.js to run the file server. What is the problem? ### Are there known steps to reproduce? 1. Boot the server in production `cd server && NODE_ENV=production node index.js &` 2. Boot the collection in another process `cd collector && NODE_ENV=production node index.js &` 3. enter it and uploard file
yindo added the possible bug label 2026-02-22 18:27:52 -05:00
yindo closed this issue 2026-02-22 18:27:52 -05:00
yindo commented 2026-02-22 18:27:53 -05:00
Author
Owner
Copy Link
Copy Source

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

We will for sure need the logs from collector and backend to determine the root cause.

In the server/.env do you have STORAGE_DIR set? This should be an absolute path and most people forget that step. This is for sure an implementation thing, so closing as it is not a bug, but please respond and I can continue to debug what specifically might be blocking your deployment

@timothycarambat commented on GitHub (Feb 11, 2025): We will for sure need the logs from `collector` and `backend` to determine the root cause. In the server/.env do you have STORAGE_DIR set? This should be an absolute path and most people forget that step. This is for sure an implementation thing, so closing as it is not a bug, but please respond and I can continue to debug what specifically might be blocking your deployment
yindo commented 2026-02-22 18:27:53 -05:00
Author
Owner
Copy Link
Copy Source

@AIxiaoHanBao commented on GitHub (Feb 12, 2025):

是

I have set this location to hotdir under collector
question:

Image

@AIxiaoHanBao commented on GitHub (Feb 12, 2025): > 是 I have set this location to hotdir under collector question: ![Image](https://github.com/user-attachments/assets/bae415d3-fa11-4edc-af9c-12418df8f7bd)
yindo commented 2026-02-22 18:27:53 -05:00
Author
Owner
Copy Link
Copy Source

@AIxiaoHanBao commented on GitHub (Feb 12, 2025):

It has been solved. The problem is that the Ubuntu running with WSL under Windwos has a problem. There is no such problem when using pure Ubuntu.

@AIxiaoHanBao commented on GitHub (Feb 12, 2025): It has been solved. The problem is that the Ubuntu running with WSL under Windwos has a problem. There is no such problem when using pure Ubuntu.
yindo commented 2026-02-22 18:27:53 -05:00
Author
Owner
Copy Link
Copy Source

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

Ah if in WSL that will almost always cause issues, usually with file permissions or something to that effect

@timothycarambat commented on GitHub (Feb 12, 2025): Ah if in WSL that will almost always cause issues, usually with file permissions or something to that effect
yindo changed title from [BUG]: Run AnythingLLM in production without Docker Find to [GH-ISSUE #3178] [BUG]: Run AnythingLLM in production without Docker Find 2026-06-05 14:44:11 -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#2041
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?