mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 11:28:35 -05:00
[GH-ISSUE #15702] issue: Failed uploading large markdown files to Knowledge #56309
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 @raymondhs on GitHub (Jul 14, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15702
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
v0.6.15
Ollama Version (if applicable)
No response
Operating System
Docker
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Large markdown files should upload successfully to the knowledge base through the Knowledge collection interface.
Actual Behavior
When attempting to upload markdown files larger than approximately 100KB, the upload fails silently. The file appears to start uploading but never completes (forever spinning). No error message is displayed to the user.
When uploading a folder, the completed progress count increases, but the large files are not shown in the list.
As a workaround, I had to divide the large files into ~100KB chunks, but this is not always ideal and it requires extra preprocessing steps.
Steps to Reproduce
Logs & Screenshots
DEBUG log was activated and there were a bunch of successful calls by
open_webui.retrieval.utils:generate_openai_batch_embeddings, so I don't think the issue comes from the backend embedding API. I checked the embedding backend API server logs and it was fine too. It looks like the embedding was completed.Additional Information
I have set my kube ingress configuration
nginx.ingress.kubernetes.io/proxy-body-size: 4096m, which should be large enough for file uploads.Any pointers are appreciated as I can't figure out what's wrong from the logs.
@taaa22 commented on GitHub (Jul 14, 2025):
The issue also occurs when you try to upload any document larger than 1 MB in the chat
@jannikstdl commented on GitHub (Jul 16, 2025):
This is likely due to ingress class configuration on K8s
In this case its often the "..is not a valid JSON"
@tjbck commented on GitHub (Jul 16, 2025):
Unable to reproduce here.
Related: #15023