github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-31 14:00:34 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #15135] issue: When BYPASS_WEB_SEARCH_WEB_LOADER is set to true for internet search, the data was not properly populated #17480

New Issue
Closed
opened 2026-04-19 23:15:12 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-19 23:15:12 -05:00
Owner
Copy Link

Originally created by @Yuan-HuiBin on GitHub (Jun 19, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15135

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Git Clone

Open WebUI Version

0.6.13

Ollama Version (if applicable)

No response

Operating System

windows 11 and Ubuntu 22.04

Browser (if applicable)

chrome

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

When this variable is true, it should default to using existing data to return to the LLM, but it's returning an empty array instead

Actual Behavior

The type of result is list.

Steps to Reproduce

Using web search with search engine set to 'external', when the 'bypass web loader' switch is enabled, no data is returned to the LLM. Actually, the logs indicate that data has been found through search. Looking at the code in routers/retrieval.py, in the process_web_search method, within the if request.app.state.config.BYPASS_WEB_SEARCH_WEB_LOADER: condition, for result in search_results, the result type is list, which causes the value extraction to fail.

Logs & Screenshots

Image

Additional Information

The type of result is list.

When using web search with external search engine and the bypass web loader switch enabled:
Issue: No data returned to LLM
Logs: Show search data was actually found
Root cause: In routers/retrieval.py, process_web_search method, within the BYPASS_WEB_SEARCH_WEB_LOADER condition, the result type in 'for result in search_results' is list, causing value extraction failure."

Originally created by @Yuan-HuiBin on GitHub (Jun 19, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/15135 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Git Clone ### Open WebUI Version 0.6.13 ### Ollama Version (if applicable) _No response_ ### Operating System windows 11 and Ubuntu 22.04 ### Browser (if applicable) chrome ### 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 When this variable is true, it should default to using existing data to return to the LLM, but it's returning an empty array instead ### Actual Behavior The type of result is list. ### Steps to Reproduce Using web search with search engine set to 'external', when the 'bypass web loader' switch is enabled, no data is returned to the LLM. Actually, the logs indicate that data has been found through search. Looking at the code in routers/retrieval.py, in the process_web_search method, within the if request.app.state.config.BYPASS_WEB_SEARCH_WEB_LOADER: condition, for result in search_results, the result type is list, which causes the value extraction to fail. ### Logs & Screenshots ![Image](https://github.com/user-attachments/assets/3c40caf0-c659-4d45-a95e-973348268040) ### Additional Information The type of result is list. When using web search with external search engine and the bypass web loader switch enabled: Issue: No data returned to LLM Logs: Show search data was actually found Root cause: In routers/retrieval.py, process_web_search method, within the BYPASS_WEB_SEARCH_WEB_LOADER condition, the result type in 'for result in search_results' is list, causing value extraction failure."
GiteaMirror added the bug label 2026-04-19 23:15:12 -05:00
GiteaMirror commented 2026-04-19 23:15:14 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Jun 19, 2025):

0.6.13 is NOT the latest version. Please update to the latest main.

<!-- gh-comment-id:2986802364 --> @tjbck commented on GitHub (Jun 19, 2025): 0.6.13 is NOT the latest version. Please update to the latest main.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#17480
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?