Websearch completion API endpoint returns a "400 Bad Request" error when attempting to generate search queries. #1293

New Issue

2025-11-11T14:42:02-06:00

GiteaMirror commented

2025-11-11 14:42:02 -06:00

Originally created by @chrisoutwright on GitHub (Jun 17, 2024).

Bug Report

Description

Bug Summary:
[Provide a brief but clear summary of the bug]

Steps to Reproduce:

Search Query via SearXNG setup (different server in my case, all works), then using the codestral:latest model
webui send a POST request to the /api/task/query/completions endpoint.
Observe the "400 Bad Request" error in the server logs.

Expected Behavior:
The API should process the request and return a completion for the search query.

Actual Behavior:
The API returns a "400 Bad Request" error, indicating that the request is malformed or invalid.

Environment

Open WebUI Version: v0.3.5
Ollama (if applicable): 0.1.41
Operating System: Windows 10
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:

I have read and followed all the instructions provided in the README.md.
I am on the latest version of both Open WebUI
I have included the browser console logs.
I have included the Docker container logs.

Logs and Screenshots

INFO: 192.168.1.224:61335 - "POST /api/chat/completed HTTP/1.1" 200 OK
INFO: 192.168.1.224:61335 - "POST /api/v1/chats/ed344228-dfbb-4676-9e46-d0c1019fbca8 HTTP/1.1" 200 OK
INFO: 192.168.1.224:61335 - "GET /api/v1/chats/ HTTP/1.1" 200 OK
generate_title
codestral
INFO
.ollama.main:url: http://192.168.1.40:11436/
INFO: 192.168.1.224:61335 - "POST /api/task/title/completions HTTP/1.1" 200 OK
INFO: 192.168.1.224:61335 - "POST /api/v1/chats/ed344228-dfbb-4676-9e46-d0c1019fbca8 HTTP/1.1" 200 OK
INFO: 192.168.1.224:61335 - "GET /api/v1/chats/ HTTP/1.1" 200 OK
INFO: 192.168.1.224:61335 - "GET /api/v1/chats/ HTTP/1.1" 200 OK
['vkUrntTOf4wDb9PqAAAB']
INFO: 192.168.1.224:61338 - "GET /_app/immutable/nodes/4.6db5c43b.js HTTP/1.1" 304 Not Modified
INFO: 192.168.1.224:61339 - "GET /_app/immutable/nodes/9.e324168b.js HTTP/1.1" 304 Not Modified
INFO: 192.168.1.224:61339 - "GET /ollama/api/version HTTP/1.1" 200 OK
generate_search_query
INFO: 192.168.1.224:61343 - "POST /api/task/query/completions HTTP/1.1" 400 Bad Request
generate_search_query
INFO: 192.168.1.224:61344 - "POST /api/task/query/completions HTTP/1.1" 400 Bad Request
INFO:root
to web search with ('searxng', 'who won EM 2024 france austria')
INFO:root
to web search with ('searxng', 'who won EM 2024 france austria')

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

Manual installation

Additional Information

The issue seems to occur specifically when generating search query completions. Other API endpoints, such as chat completions, appear to work fine. This suggests the issue might be specific to the /api/task/query/completions endpoint or related request handling.

Originally created by @chrisoutwright on GitHub (Jun 17, 2024). # Bug Report ## Description **Bug Summary:** [Provide a brief but clear summary of the bug] **Steps to Reproduce:** 1. Search Query via SearXNG setup (different server in my case, all works), then using the codestral:latest model 2. webui send a POST request to the /api/task/query/completions endpoint. 3. Observe the "400 Bad Request" error in the server logs. **Expected Behavior:** The API should process the request and return a completion for the search query. **Actual Behavior:** The API returns a "400 Bad Request" error, indicating that the request is malformed or invalid. ## Environment - Open WebUI Version: v0.3.5 - Ollama (if applicable): 0.1.41 - Operating System: Windows 10 - **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:** - [x] I have read and followed all the instructions provided in the README.md. - [x] I am on the latest version of both Open WebUI - [ ] I have included the browser console logs. - [ ] I have included the Docker container logs. ## Logs and Screenshots ``` INFO: 192.168.1.224:61335 - "POST /api/chat/completed HTTP/1.1" 200 OK INFO: 192.168.1.224:61335 - "POST /api/v1/chats/ed344228-dfbb-4676-9e46-d0c1019fbca8 HTTP/1.1" 200 OK INFO: 192.168.1.224:61335 - "GET /api/v1/chats/ HTTP/1.1" 200 OK generate_title codestral INFO .ollama.main:url: http://192.168.1.40:11436/ INFO: 192.168.1.224:61335 - "POST /api/task/title/completions HTTP/1.1" 200 OK INFO: 192.168.1.224:61335 - "POST /api/v1/chats/ed344228-dfbb-4676-9e46-d0c1019fbca8 HTTP/1.1" 200 OK INFO: 192.168.1.224:61335 - "GET /api/v1/chats/ HTTP/1.1" 200 OK INFO: 192.168.1.224:61335 - "GET /api/v1/chats/ HTTP/1.1" 200 OK ['vkUrntTOf4wDb9PqAAAB'] INFO: 192.168.1.224:61338 - "GET /_app/immutable/nodes/4.6db5c43b.js HTTP/1.1" 304 Not Modified INFO: 192.168.1.224:61339 - "GET /_app/immutable/nodes/9.e324168b.js HTTP/1.1" 304 Not Modified INFO: 192.168.1.224:61339 - "GET /ollama/api/version HTTP/1.1" 200 OK generate_search_query INFO: 192.168.1.224:61343 - "POST /api/task/query/completions HTTP/1.1" 400 Bad Request generate_search_query INFO: 192.168.1.224:61344 - "POST /api/task/query/completions HTTP/1.1" 400 Bad Request INFO:root to web search with ('searxng', 'who won EM 2024 france austria') INFO:root to web search with ('searxng', 'who won EM 2024 france austria') ``` **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 Manual installation ## Additional Information The issue seems to occur specifically when generating search query completions. Other API endpoints, such as chat completions, appear to work fine. This suggests the issue might be specific to the /api/task/query/completions endpoint or related request handling.

GiteaMirror closed this issue