mirror of
https://github.com/open-webui/open-webui.git
synced 2026-06-04 07:47:12 -05:00
[GH-ISSUE #20290] issue: #57809
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#57809
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 @rldet9 on GitHub (Dec 31, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20290
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.6.43
Ollama Version (if applicable)
ollama version is 0.12.10
Operating System
Linux (Docker container)
Browser (if applicable)
API only
Confirmation
README.md.Expected Behavior
I've identified multiple critical API issues related to knowledge base endpoints that affect programmatic access to knowledge bases and their files. These issues prevent proper automation and integration workflows.
Issue 1: GET /api/v1/knowledge/{id} Returns files: null Despite Files Existing
Expected Behavior
The endpoint should return a JSON object with a files array containing all files associated with the knowledge base.
Actual Behavior
The endpoint returns files: null for ALL knowledge bases, even though:
Files are visible in the UI
Files are stored in the database
The undocumented endpoint /api/v1/knowledge/{id}/files correctly returns all files
Steps to Reproduce
Create a knowledge base via UI or API
Upload files to the knowledge base
Verify files are visible in the UI
Make API call:
bashcurl -X GET "http://your-instance:8080/api/v1/knowledge/{knowledge_id}"
-H "Authorization: Bearer YOUR_JWT_TOKEN"
Actual Response
json{
"id": "knowledge-uuid",
"name": "My Knowledge Base",
"description": "...",
"files": null, // ❌ Should be an array with file objects
"created_at": 1234567890,
"updated_at": 1234567890
}
Logs & Screenshots
2025-12-31 10:26:28.899 | INFO | uvicorn.protocols.http.httptools_impl:send:476 - 172.26.0.9:49896 - "GET /api/v1/knowledge/a4eed2e6-b5cf-472b-9490-841022dc53df?id=a4eed2e6-b5cf-472b-9490-841022dc53df HTTP/1.1" 200
Additional Information
Undocumented Endpoint GET /api/v1/knowledge/{id}/files Works But Not in OpenAPI Spec
Discovery
While troubleshooting Issue 1, I discovered that the endpoint /api/v1/knowledge/{id}/files exists and works correctly, but:
❌ Not documented in the OpenAPI specification (/openapi.json)
❌ Not mentioned in official documentation
✅ Returns complete file information including content
@owui-terminator[bot] commented on GitHub (Dec 31, 2025):
🔍 Similar Issues Found
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
#19864 issue:
by Haervwe • Dec 10, 2025 •
bug#20019 issue:
by j63440490 • Dec 17, 2025 •
bug#19777 issue:
by Yaute7 • Dec 05, 2025 •
bug#20092 issue:
by VideoRyan • Dec 22, 2025 •
bug#20046 issue:
by pierrelouisbescond • Dec 19, 2025 •
bugShow 5 more related issues
#19877 issue:
by dotmobo • Dec 11, 2025 •
bug#19861 issue:
by QuitHub • Dec 10, 2025 •
bug#20107 issue:
by mengdeer589 • Dec 22, 2025 •
bug#19563 issue:
by naruto7g • Nov 28, 2025 •
bug#19211 issue:
by Byrnes9 • Nov 16, 2025 •
bug💡 Tips:
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
@pr-validator-bot commented on GitHub (Dec 31, 2025):
⚠️ Invalid Issue Title
Hey @rldet9, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:") make it difficult for volunteer contributors to understand and triage issues.
Please update the title to reflect the content of your issue.
@tjbck commented on GitHub (Dec 31, 2025):
you should use a dedicated endpoint to retrieve files.