mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-08 04:16:03 -05:00
[GH-ISSUE #16816] issue: Document embedding doesn't work - active: hybrid search/reranker in v.0.6.23 #33583
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 @eXt73 on GitHub (Aug 22, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16816
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.23
Ollama Version (if applicable)
0.11.5
Operating System
Linux - Ubuntu 24.04
Browser (if applicable)
Brave v1.81.136
Confirmation
README.md.Expected Behavior
The document should be properly embedded, then searched by Qwen3, reranked by bge-reranker-v2-m3 and the fragments prepared in this way are sent to LLM 'on the front end'
Actual Behavior
In version v.0.6.23, document embedding and hybrid search/reranker stopped working in v.0.6.23. It looks like the document is embedded, but in reality, the LLM model doesn't receive it. When we disable reranker, the embedding itself works correctly - I use hf.co/Qwen/Qwen3-Embedding-4B-GGUF:Q8_0 via ollama, and as a reranker: BAAI/bge-reranker-v2-m3. Everything worked perfectly until version v.0.6.22.
Steps to Reproduce
I'm skipping the obvious parts:
Logs & Screenshots
Additional Information
No response
@uuuhuuu commented on GitHub (Aug 22, 2025):
Same problem, after upgrading to version 0.6.23, none of my RAGs are working anymore. Same problem with 0.6.24.
@alpilotx commented on GitHub (Aug 22, 2025):
Yes, it seems - according to logs - it always bails out with some error like this
@tjbck commented on GitHub (Aug 22, 2025):
Should be addressed in dev with
fbff4e19de, testing wanted here!@tjbck commented on GitHub (Aug 22, 2025):
@XYKiwi03 milvus error, unrelated to this post.
@alpilotx commented on GitHub (Aug 22, 2025):
I tried this fix (just quickly, manually "updated" my 0.6.24) , and it seems to work!