mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 03:18:23 -05:00
[GH-ISSUE #14746] issue: Bypass Web Loader in Web Search not working #56017
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 @williamgateszhao on GitHub (Jun 7, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14746
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.13
Ollama Version (if applicable)
No response
Operating System
Alpine Linux 6.12.22
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
When enabling
Bypass Web Loaderin admin/settings - Web Search, the web search should work normally.Actual Behavior
After enabling
Bypass Web Loader, the web search consistently returns empty results.Steps to Reproduce
Logs & Screenshots
No need to provide the log as the issue has already been identified.
Additional Information
This bug was introduced by commit
2eca6f6, which was inspired by my PR #11655 and @Youggls' PR #12845.Previously, in backend/open_webui/routers/retrieval.py, the
web_resultsin theprocess_web_searchfunction was a flat list. Thus, whenrequest.app.state.config.BYPASS_WEB_SEARCH_WEB_LOADERwas True, the logicfor result in search_resultswithpage_content=result.snippetworked correctly.However, in the current implementation,
web_resultsinprocess_web_searchis now a nested list (see line 1814). To access result.snippet, the list must first be flattened into a 1D array. The fix would be:Would you like me to submit a PR to implement this fix?
@PSL3D commented on GitHub (Jun 7, 2025):
I can confirm I am experiencing the exact same issue on the latest version with Docker Compose. docker inspect shows the SEARXNG_QUERY_URL environment variable is correctly set, but the application logs state that it is not found. Inter-container networking is confirmed working via curl.
@tjbck commented on GitHub (Jun 16, 2025):
Fixed with f3cae94028bd494cae7a29e62fad2ea55f910d89!