mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 03:18:23 -05:00
[GH-ISSUE #2947] help; searxng web search 400 clinet error: Bad request #13075
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#13075
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 @qhmhl on GitHub (Jun 9, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/2947
Bug Report
Description
web search with searxng, feedback error "400 clinet error: Bad request"
Bug Summary:
[Provide a brief but clear summary of the bug]
400 Client Error: BAD REQUEST for url: http://192.168.3.6:38080/search?q=&q=%E5%B8%AE%E6%88%91%E6%9F%A5%E8%AF%A22024%E4%B8%AD%E5%9B%BD%E9%AB%98%E8%80%83%E5%85%B7%E4%BD%93%E6%97%B6%E9%97%B4&format=json&pageno=1&language=en-US&time_range=&categories=&theme=simple&image_proxy=0
Steps to Reproduce:
[Outline the steps to reproduce the bug. Be as detailed as possible.]
Expected Behavior:
[Describe what you expected to happen.]
Actual Behavior:
[Describe what actually happened.]
Environment
Open WebUI Version: [e.g., 0.1.120]
Ollama (if applicable): [e.g., 0.1.30, 0.1.32-rc1]
Operating System: [e.g., Windows 10, macOS Big Sur, Ubuntu 20.04]
Browser (if applicable): [e.g., Chrome 100.0, Firefox 98.0]
Reproduction Details
Confirmation:
Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
[Include relevant Docker container logs, if applicable]
Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
[Describe the method you used to install the project, e.g., manual installation, Docker, package manager, etc.]
Additional Information
[Include any additional details that may help in understanding and reproducing the issue. This could include specific configurations, error messages, or anything else relevant to the bug.]
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!