mirror of
https://github.com/open-webui/open-webui.git
synced 2026-03-10 07:43:10 -05:00
issue: RAG_FILE_MAX_COUNT does not apply to prompts through the UI #5511
Reference in New Issue
Block a user
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?
Originally created by @KyleMasterson on GitHub (Jun 11, 2025).
Originally assigned to: @jackthgu on GitHub.
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.13
Ollama Version (if applicable)
No response
Operating System
ghcr.io/open-webui/open-webui
Browser (if applicable)
Version 137.0.7151.69 (Official Build) (arm64)
Confirmation
README.md.Expected Behavior
Providing
RAG_FILE_MAX_COUNTshould limit the maximum number of files that can be uploaded in a promptActual Behavior
Problem
Providing
RAG_FILE_MAX_COUNTdoes not limit the maximum number of files that can be uploaded in a prompt.Impact
Despite the fact that we have a
RAG_FILE_MAX_SIZEof 10mb, users are able to upload an unlimited number of files, rendering this file size limit useless. To address this, we attempted to set theRAG_FILE_MAX_COUNTwhich we hoped would limit the single prompt max file upload to (10mb * file count). However, this is not the case, as file upload counts are still unbounded.These unbounded file uploads are ultimately overwhelming our open-webui instance and causing frequent outages
Steps to Reproduce
Logs & Screenshots
Container logs:
Chrome console logs:
Additional Information
No response
@tjbck commented on GitHub (Jun 16, 2025):
This was an intended behaviour, if you were to try to chat with the files attached it wouldn't have let you to continue, however, chat input attachement-level filtering has also been applied with
d802c718a4@KyleMasterson commented on GitHub (Jun 16, 2025):
@tjbck unfortunately that is untrue, I was able to submit that chat message with all 20 files attached, and was not limited/restricted in any way from doing so.
I'll apply 0.6.15 once it's ready and reply here again if this issue persists