mirror of
https://github.com/open-webui/open-webui.git
synced 2026-11-17 15:53:59 -06:00
[GH-ISSUE #24017] issue: Web search breaks persistently after setting Fetch URL Content Length Limit to 80000 #35682
Reference in New Issue
Block a user
Originally created by @mero20j1 on GitHub (Apr 22, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24017
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.9.1
Ollama Version (if applicable)
No response
Operating System
Ubuntu
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
Summary
I found what looks like a persistent configuration bug in web search / retrieval settings.
When I set Fetch URL Content Length Limit to 80000 in the OpenWebUI web search settings, web search starts failing.
The main problem is that the failure persists even after changing the value back in the UI.
At that point, the instance seems stuck in a broken state until I restore from backup.
⸻
Environment
Example setup:
⸻
What I changed
In Admin Settings → Web Search / Retrieval, I set:
After that, web search started failing.
Even if I later:
…the issue remains.
I had to restore from backup to get back to a working state.
⸻
Expected behavior
Changing Fetch URL Content Length Limit should either:
It should not leave the web search pipeline in a permanently broken state.
⸻
Actual behavior
After setting Fetch URL Content Length Limit = 80000, OpenWebUI starts failing during web search / retrieval.
Observed errors include:
Error processing chat payload: 'NoneType' object has no attribute 'strip'
500 Server Error: Internal Server Error for url: http://192.168.1.172:3002/v1/scrape
Unsupported input type: NoneType. Expected one of: str, dict, PIL.Image.Image, np.ndarray, torch.Tensor
and in the traceback:
query_embeddings = await embedding_function(queries, ...)
queries = [None]
This suggests that somewhere in the pipeline, OpenWebUI ends up passing None instead of a text query.
⸻
Reproduction steps
⸻
Important observation
This looks persistent.
It is not just a temporary runtime issue.
Even after changing the setting again, the instance stays broken until restoring a previous backup.
So this may be:
⸻
Additional notes
I also observed that OpenWebUI stores retrieval/web settings in the SQLite config JSON (webui.db, table config), under nested keys such as:
It may be worth checking whether setting this value to 80000 causes an inconsistent state in one or both locations.
⸻
Related symptoms seen during debugging
Other errors seen while debugging web search in this same setup:
(separate issue, fixed locally by adding import requests)
But the specific issue in this report is:
setting Fetch URL Content Length Limit to 80000 appears to corrupt web search behavior in a persistent way.
⸻
Logs
Example errors:
Error processing chat payload: 'NoneType' object has no attribute 'strip'
Error extracting content from URLs: 500 Server Error: Internal Server Error for url: http://192.168.1.172:3002/v1/scrape
Unsupported input type: NoneType. Expected one of: str, dict, PIL.Image.Image, np.ndarray, torch.Tensor
Actual Behavior
After setting Fetch URL Content Length Limit to 80000, web search becomes unstable and starts failing.
Even after reverting the value in the UI and restarting the container, the issue persists.
Observed errors include:
At this point, web search remains broken until restoring a previous backup, suggesting a persistent corrupted state in the configuration or retrieval pipeline.
Steps to Reproduce
Steps to Reproduce
Logs & Screenshots
See desc
Additional Information
No response
@tjbck commented on GitHub (Apr 24, 2026):
Addressed in dev.