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.0
Ollama Version (if applicable)
0.5.13
Operating System
linux
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
Add text content to knowledge and it is added.
Actual Behavior
If "Add text content" is used while adding Knowledge they should bypass docling since they are already in text format. Currently they are sent do docling and that returns and error so the import fails.
Steps to Reproduce
Go to add knowledge and try "Add text content"
Paste text into the input area.
Click save
Error is seen:
Logs & Screenshots
Additional Information
This might also hold true for any file that is already text formatted when its uploaded.
I apologize for using screenshots, as I was having fits with getting formatting and stuff preserved.
Originally created by @geiseri on GitHub (Apr 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12357
### 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.0
### Ollama Version (if applicable)
0.5.13
### Operating System
linux
### 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
Add text content to knowledge and it is added.
### Actual Behavior
If "Add text content" is used while adding Knowledge they should bypass docling since they are already in text format. Currently they are sent do docling and that returns and error so the import fails.
### Steps to Reproduce
1. Go to add knowledge and try "Add text content"
2. Paste text into the input area.
3. Click save
4. Error is seen:
### Logs & Screenshots
### Additional Information
This might also hold true for any file that is already text formatted when its uploaded.
I apologize for using screenshots, as I was having fits with getting formatting and stuff preserved.
GiteaMirror
added the bug label 2026-05-15 11:45:52 -05:00
Got the problem, I'll get it fixed as soon as I can, probably this weekend. Thanks for reporting it!
<!-- gh-comment-id:2773903404 -->
@FabioPolito24 commented on GitHub (Apr 2, 2025):
Got the problem, I'll get it fixed as soon as I can, probably this weekend. Thanks for reporting it!
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 @geiseri on GitHub (Apr 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/12357
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.0
Ollama Version (if applicable)
0.5.13
Operating System
linux
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Add text content to knowledge and it is added.
Actual Behavior
If "Add text content" is used while adding Knowledge they should bypass docling since they are already in text format. Currently they are sent do docling and that returns and error so the import fails.
Steps to Reproduce
Logs & Screenshots
Additional Information
This might also hold true for any file that is already text formatted when its uploaded.
I apologize for using screenshots, as I was having fits with getting formatting and stuff preserved.
@tjbck commented on GitHub (Apr 2, 2025):
@FabioPolito24
@FabioPolito24 commented on GitHub (Apr 2, 2025):
Got the problem, I'll get it fixed as soon as I can, probably this weekend. Thanks for reporting it!
@geiseri commented on GitHub (Apr 8, 2025):
Seems fixed in #12486 so I will close this.