mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 10:58:17 -05:00
[GH-ISSUE #11387] issue: RAG broken on latest versions #31738
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 @galvanoid on GitHub (Mar 7, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/11387
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.5.20
Ollama Version (if applicable)
latest
Operating System
Ubuntu 24.04
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Accurate RAG or at least correct
Actual Behavior
I've been using open webui since almost the first versions. My main use is RAG in the legal sector.
I've always had very good, even surprising, results in reasoning in my field, using legal documents.
But for some time now I haven't been getting those results. I've spent many days doing endless tests, different embedding models, all possible parameters, I've installed tika, increased the context to 128k, even manually deleted the vector_db (which by the way, sometimes doesn't get deleted from configuration/administrator/documents).
In desperation, I started up an old VM, before I switched to SSD, where I have version 0.5.4 installed.
To my surprise, with exactly the same parameters, same embedding model, same chunk size, top k, same model, same context size, etc., putting one version against another (0.5.4 against the latest 0.5.15-20) the results were completely disparate.
While version 0.5.4 nails the results of the questions about documents, the newer versions give very bad results, sometimes almost completely fabricated and, when it gets it right, it does so only partially.
So I have reinstalled version 0.5.4 on my SSD machine and I confirm that the results are excellent, as they were before. With exact answers in relation to the documents provided.
There seems to be something wrong with later versions, which works fine in 0.5.
Steps to Reproduce
Logs & Screenshots
No logs.
Additional Information
No response