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 #5050] [Bug] Failed to move uploaded file to hot directory on Tencent Cloud Lighthouse (Docker) #4887

New Issue
Closed
opened 2026-06-05 14:50:41 -04:00 by yindo · 1 comment
yindo commented 2026-06-05 14:50:41 -04:00
Owner
Copy Link
Copy Source

Originally created by @bakusefu-sudo on GitHub (Feb 23, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5050

How are you running AnythingLLM?

Docker (local)

What happened?

Environment:
• Server: Tencent Cloud Lighthouse (Ubuntu 22.04, 2vCPU/4GB RAM)
• Installation: Docker (Image: mintplexlabs/anythingllm:latest)
• Browser/OS: Windows 11 / Chrome (Proxy: Bypassed for server IP)
Description of Problem:
I can access the WebUI and chat with DeepSeek normally. However, I cannot upload any documents (even a 1KB TXT file).
The error message in WebUI is: Failed to move uploaded file to hot directory.
The error in Docker logs is: ENOENT: no such file or directory, open '/collector/hotdir/...' OR EACCES: permission denied.
What I have tried (and failed):

  1. Running with --user root to fix permissions.
  2. Using named volumes (-v anythingllm_data:/app/storage) instead of bind mounts.
  3. Manually setting STORAGE_DIR and COLLECTOR_HOTDIR environment variables.
  4. chmod -R 777 on all relevant host and container directories.
  5. Disabling all local VPNs/proxies during upload.
    The Issue persists: The "Collector" module seems unable to move files from the temp directory to the storage directory within the container on this specific cloud provider.
    Question: Is there a specific storage driver or permission setting required for Tencent Cloud? Or is this a bug in the Collector's file handling logic on Node v18?
Image Image

Are there known steps to reproduce?

No response

Originally created by @bakusefu-sudo on GitHub (Feb 23, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/5050 ### How are you running AnythingLLM? Docker (local) ### What happened? Environment: • Server: Tencent Cloud Lighthouse (Ubuntu 22.04, 2vCPU/4GB RAM) • Installation: Docker (Image: mintplexlabs/anythingllm:latest) • Browser/OS: Windows 11 / Chrome (Proxy: Bypassed for server IP) Description of Problem: I can access the WebUI and chat with DeepSeek normally. However, I cannot upload any documents (even a 1KB TXT file). The error message in WebUI is: Failed to move uploaded file to hot directory. The error in Docker logs is: ENOENT: no such file or directory, open '/collector/hotdir/...' OR EACCES: permission denied. What I have tried (and failed): 1. Running with --user root to fix permissions. 2. Using named volumes (-v anythingllm_data:/app/storage) instead of bind mounts. 3. Manually setting STORAGE_DIR and COLLECTOR_HOTDIR environment variables. 4. chmod -R 777 on all relevant host and container directories. 5. Disabling all local VPNs/proxies during upload. The Issue persists: The "Collector" module seems unable to move files from the temp directory to the storage directory within the container on this specific cloud provider. Question: Is there a specific storage driver or permission setting required for Tencent Cloud? Or is this a bug in the Collector's file handling logic on Node v18? <img width="585" height="1266" alt="Image" src="https://github.com/user-attachments/assets/1b8b0089-00de-4b8d-8537-ba98697de10a" /> <img width="386" height="172" alt="Image" src="https://github.com/user-attachments/assets/6a32aea1-17a2-41d5-ab76-20831d4b3d3b" /> ### Are there known steps to reproduce? _No response_
yindo added the possible bug label 2026-06-05 14:50:41 -04:00
yindo closed this issue 2026-06-05 14:50:41 -04:00
yindo commented 2026-06-05 14:50:42 -04:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Feb 23, 2026):

This is specific to your deployment and is not a bug. We cannot assist with every self-host issue due to configuration problems.

if you are using the official command (or same thing in docker compose)

export STORAGE_LOCATION=$HOME/anythingllm && \
mkdir -p $STORAGE_LOCATION && \
touch "$STORAGE_LOCATION/.env" && \
docker run -d -p 3001:3001 \
--cap-add SYS_ADMIN \
-v ${STORAGE_LOCATION}:/app/server/storage \
-v ${STORAGE_LOCATION}/.env:/app/server/.env \
-e STORAGE_DIR="/app/server/storage" \
mintplexlabs/anythingllm:latest

The fact that collection/hotdir does not exist is the main issue indicates that whatever you are mounting the storage folder to is either read-only OR the docker user does not have access to write to.

I know you said you chmod the storage folders, but if you are trying to mount to a top-level directory like /anythingllm instead of a userspace one like ~/anythingllm you need to chmod the whole folder - otherwise the docker user will be unable to write folders/files to the space and you will get this issue.

<!-- gh-comment-id:3946153278 --> @timothycarambat commented on GitHub (Feb 23, 2026): This is specific to your deployment and is not a bug. We cannot assist with every self-host issue due to configuration problems. if you are using the official command (or same thing in docker compose) ```bash export STORAGE_LOCATION=$HOME/anythingllm && \ mkdir -p $STORAGE_LOCATION && \ touch "$STORAGE_LOCATION/.env" && \ docker run -d -p 3001:3001 \ --cap-add SYS_ADMIN \ -v ${STORAGE_LOCATION}:/app/server/storage \ -v ${STORAGE_LOCATION}/.env:/app/server/.env \ -e STORAGE_DIR="/app/server/storage" \ mintplexlabs/anythingllm:latest ``` The fact that `collection/hotdir` does not exist is the main issue indicates that whatever you are mounting the storage folder to is either read-only OR the docker user does not have access to write to. I know you said you chmod the storage folders, but if you are trying to mount to a top-level directory like `/anythingllm` instead of a userspace one like `~/anythingllm` you need to chmod the whole folder - otherwise the docker user will be unable to write folders/files to the space and you will get this issue.
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#4887
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?