-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: Allow Web Search RAG to Continue on Invalid Hostname Resolution #2839
Comments
i add at the end, now the error as below. |
Hello, I'm still encountering this issue; here is the debug prompt. Could anyone assist?
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Description
Bug Summary:
When using the Web Search RAG feature, if the search engine returns a hostname that the server cannot resolve, all search results are blocked from proceeding to the next step of RAG processing.
Steps to Reproduce:
1.Use the Web Search RAG feature with a URL that points to a hostname that cannot be resolved by the DNS.
2.Observe that once the unresolvable hostname is encountered, all other valid search results are also blocked and do not proceed to the next step.
Expected Behavior:
If a hostname cannot be resolved, that specific URL should be ignored, and the Web Search RAG should continue processing the remaining valid URLs without interruption.
Actual Behavior:
The Web Search RAG stops processing all URLs and answer directly through the models when encountering an unresolvable hostname.
Environment
Open WebUI Version: v0.2.4
Ollama (if applicable): 0.1.39
Operating System: Windows 11, wsl2, Debian
Browser (if applicable): [e.g., Chrome 100.0, Firefox 98.0]
Reproduction Details
Confirmation:
Logs and Screenshots
Command Console Logs:
Installation Method
manual installation
The text was updated successfully, but these errors were encountered: