I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.
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
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 provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
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
}
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
Originally created by @rldet9 on GitHub (Dec 31, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20290
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
- [x] I am using the latest version of Open WebUI.
### 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
- [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 **provided every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### 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
GiteaMirror
added the bug label 2026-05-05 21:40:17 -05:00
If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
If you found a solution in any of these issues, please share it here to help others
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
<!-- gh-comment-id:3701928372 -->
@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:
1. [#19864](https://github.com/open-webui/open-webui/issues/19864) **issue:**
*by Haervwe • Dec 10, 2025 • `bug`*
2. [#20019](https://github.com/open-webui/open-webui/issues/20019) **issue:**
*by j63440490 • Dec 17, 2025 • `bug`*
3. [#19777](https://github.com/open-webui/open-webui/issues/19777) **issue:**
*by Yaute7 • Dec 05, 2025 • `bug`*
4. [#20092](https://github.com/open-webui/open-webui/issues/20092) **issue:**
*by VideoRyan • Dec 22, 2025 • `bug`*
5. [#20046](https://github.com/open-webui/open-webui/issues/20046) **issue:**
*by pierrelouisbescond • Dec 19, 2025 • `bug`*
<details>
<summary>Show 5 more related issues</summary>
6. [#19877](https://github.com/open-webui/open-webui/issues/19877) **issue:**
*by dotmobo • Dec 11, 2025 • `bug`*
7. [#19861](https://github.com/open-webui/open-webui/issues/19861) **issue:**
*by QuitHub • Dec 10, 2025 • `bug`*
8. [#20107](https://github.com/open-webui/open-webui/issues/20107) **issue:**
*by mengdeer589 • Dec 22, 2025 • `bug`*
9. [#19563](https://github.com/open-webui/open-webui/issues/19563) **issue:**
*by naruto7g • Nov 28, 2025 • `bug`*
10. [#19211](https://github.com/open-webui/open-webui/issues/19211) **issue:**
*by Byrnes9 • Nov 16, 2025 • `bug`*
</details>
---
💡 **Tips:**
- If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
- If you found a solution in any of these issues, please share it here to help others
*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.
<!-- gh-comment-id:3701929273 -->
@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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.