github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-10 15:54:15 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

issue: /api/v1/files/ upload endpoint succeeds, but file is not processed (data.content remains empty) #5066

New Issue
Closed
opened 2025-11-11 16:11:15 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 16:11:15 -06:00
Owner
Copy Link

Originally created by @LosaLosSantos on GitHub (May 6, 2025).

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.6

Ollama Version (if applicable)

No response

Operating System

Windows 10

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have listed steps to reproduce the bug in detail.

Expected Behavior

After a successful POST /api/v1/files/, the file should be automatically processed and chunked in the backend, exactly as happens when uploading via the web UI. This ensures the file is ready to be added to a knowledge base and used in RAG flows.

Actual Behavior

Uploading file via POST /api/v1/files/ returns 200 OK with a valid file ID.

However, the uploaded file is not processed:

The corresponding data.content remains empty ({}), and when we try to add the file to a knowledge base via

Steps to Reproduce

Polling /api/v1/files/{id} repeatedly until data.content is populated appears to work only if the UI is open, suggesting the background worker might be linked to a frontend action.

Logs & Screenshots

Collection created: 3496278d-a417-4538-995c-936177edfb77
Loading: LD19SGI-QS1011-009 - Accessi Logici - v05.docx
Uploaded: 2e94bdba-cbd5-43e7-81f6-bd3edc4e0d49
Added to collection: {'detail': 'Extracted content is not available for this file. Please ensure that the file is processed before proceeding.'}
Loading: Strategia_italiana_per_l_Intelligenza_artificiale_2024-2026.pdf
Uploaded: 2aff2bd2-21ec-42e9-b100-5be2befd4357
Added to collection: {'detail': 'Extracted content is not available for this file. Please ensure that the file is processed before proceeding.'}

Additional Information

No response

Originally created by @LosaLosSantos on GitHub (May 6, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.6 ### Ollama Version (if applicable) _No response_ ### Operating System Windows 10 ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have listed steps to reproduce the bug in detail. ### Expected Behavior After a successful POST /api/v1/files/, the file should be automatically processed and chunked in the backend, exactly as happens when uploading via the web UI. This ensures the file is ready to be added to a knowledge base and used in RAG flows. ### Actual Behavior Uploading file via POST /api/v1/files/ returns 200 OK with a valid file ID. However, the uploaded file is not processed: The corresponding data.content remains empty ({}), and when we try to add the file to a knowledge base via ### Steps to Reproduce Polling /api/v1/files/{id} repeatedly until data.content is populated appears to work only if the UI is open, suggesting the background worker might be linked to a frontend action. ### Logs & Screenshots Collection created: 3496278d-a417-4538-995c-936177edfb77 Loading: LD19SGI-QS1011-009 - Accessi Logici - v05.docx Uploaded: 2e94bdba-cbd5-43e7-81f6-bd3edc4e0d49 Added to collection: {'detail': 'Extracted content is not available for this file. Please ensure that the file is processed before proceeding.'} Loading: Strategia_italiana_per_l_Intelligenza_artificiale_2024-2026.pdf Uploaded: 2aff2bd2-21ec-42e9-b100-5be2befd4357 Added to collection: {'detail': 'Extracted content is not available for this file. Please ensure that the file is processed before proceeding.'} ### Additional Information _No response_
GiteaMirror added the bug label 2025-11-11 16:11:15 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#5066
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?