mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-31 14:00:34 -05:00
SearxNG Search Issues in 0.3.3 #1226
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 @ProjectMoon on GitHub (Jun 12, 2024).
Bug Report
Description
Bug Summary:
Searching stalls or sometimes fails when using SearxNG. It will report an error about invalid URLs.
Steps to Reproduce:
Enable web search and configure a searxNG URL like
https://search.example.com/search?q=<query>.Expected Behavior:
Search results are shown and fed to the LLM for context.
Actual Behavior:
The search either stalls (prints "searching" in the logs but does nothing) or errors out (reports error about invalid URL).
The invalid URL error actually comes from the search result URLs themselves, not the actual search query. I added a print statement to verify this, and it was failing to validate one of the top 3 result URLs, even though it is a valid URL.
Environment
Open WebUI Version: 0.3.3
Ollama (if applicable): 0.1.43 (though don't think it is applicable)
Operating System: Gentoo Linux
Browser (if applicable): Firefox 126
Reproduction Details
Confirmation:
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
(This includes my added
printstatement)Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
Docker
Additional Information
I'm not sure what causes the stall vs validation failure.
@YetheSamartaka commented on GitHub (Jun 12, 2024):
I have exactly the same issue on Ubuntu 24.04 with searxng after updating from 0.3.1 to 0.3.3. Also the logs are pretty much the same for me.
@Lakr233 commented on GitHub (Jun 12, 2024):
Add
- ENABLE_RAG_LOCAL_WEB_FETCH=Truefixed the problem.@justinh-rahb commented on GitHub (Jun 12, 2024):
Confirmed bug on 0.3.3 here, and your fix resolves it as well.
@ProjectMoon commented on GitHub (Jun 12, 2024):
Yes, this works. Looks like the commit is being reverted too?
@justinh-rahb commented on GitHub (Jun 12, 2024):
Indeed, would highly recommend reverting that envvar as soon as it's merged to main.
@tjbck commented on GitHub (Jun 12, 2024):
Reverted, merging soon!