I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
v0.8.8
Ollama Version (if applicable)
0.11.2
Operating System
macOS Sequoia
Browser (if applicable)
chrome
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
Expected Behavior
Filtered domains for web search should allow a web search only in those sites when signaled.
Actual Behavior
If filtered domains are listed, the web search isn't performed and the error shown is "An error occurred while searching the web" in the interface
Steps to Reproduce
Admin > Web Search > list some domain in Domain filters list
Then activate the web search in a chat and see what happens
Logs & Screenshots
Additional Information
No response
Originally created by @nsfregola-maker on GitHub (Mar 4, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22224
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.8.8
### Ollama Version (if applicable)
0.11.2
### Operating System
macOS Sequoia
### Browser (if applicable)
chrome
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### Expected Behavior
Filtered domains for web search should allow a web search only in those sites when signaled.
### Actual Behavior
If filtered domains are listed, the web search isn't performed and the error shown is "An error occurred while searching the web" in the interface
### Steps to Reproduce
Admin > Web Search > list some domain in _Domain filters list_
Then activate the web search in a chat and see what happens
### Logs & Screenshots
<img width="1206" height="730" alt="Image" src="https://github.com/user-attachments/assets/ebe9a139-6ab1-4756-bef7-417a57c610e2" />
<img width="595" height="89" alt="Image" src="https://github.com/user-attachments/assets/caa6571f-3aa8-4f61-9178-0771daa724c4" />
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-15 15:39:21 -05:00
@pr-validator-bot commented on GitHub (Mar 4, 2026):
⚠️ Invalid Issue Title
Hey @nsfregola-maker, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues.
Please update the title to reflect the content of your issue.
⚠️ Missing Issue Title Prefix
@nsfregola-maker, your issue title is missing a prefix (e.g., bug:, feat:, docs:).
Please update your issue title to include one of the following prefixes:
bug: Bug report or error you've encountered
feat: Feature request or enhancement suggestion
docs: Documentation issue or improvement request
question: Question about usage or functionality
help: Request for help or support
Example: bug: Login fails when using special characters in password
<!-- gh-comment-id:3998186450 -->
@pr-validator-bot commented on GitHub (Mar 4, 2026):
# ⚠️ Invalid Issue Title
Hey @nsfregola-maker, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues.
Please update the title to reflect the content of your issue.
---
# ⚠️ Missing Issue Title Prefix
@nsfregola-maker, your issue title is missing a prefix (e.g., `bug:`, `feat:`, `docs:`).
Please update your issue title to include one of the following prefixes:
- **bug**: Bug report or error you've encountered
- **feat**: Feature request or enhancement suggestion
- **docs**: Documentation issue or improvement request
- **question**: Question about usage or functionality
- **help**: Request for help or support
Example: `bug: Login fails when using special characters in password`
As per the docs, this is a FILTER list, not an allowlist
essentially: the domains you enter get FILTERED and are NOT fetched.
This is a security feature to prevent SSRF attacks.
Making this filter allow-list based (as you want it to: only search on rottentomatoes) would benefit you, but would destroy 99.999% of deployments out there that rely on this being a blocklist.
Also, you can't really use an allowlist for this anyways, since we are talking about the internet.
You can't make an allowlist for the internet
<!-- gh-comment-id:3998621659 -->
@Classic298 commented on GitHub (Mar 4, 2026):
@nsfregola-maker there is a misunderstanding.
As per the docs, this is a FILTER list, not an allowlist
essentially: the domains you enter get FILTERED and are NOT fetched.
This is a security feature to prevent SSRF attacks.
Making this filter allow-list based (as you want it to: only search on rottentomatoes) would benefit you, but would destroy 99.999% of deployments out there that rely on this being a blocklist.
Also, you can't really use an allowlist for this anyways, since we are talking about the internet.
You can't make an allowlist for the internet
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @nsfregola-maker on GitHub (Mar 4, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22224
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.8.8
Ollama Version (if applicable)
0.11.2
Operating System
macOS Sequoia
Browser (if applicable)
chrome
Confirmation
README.md.Expected Behavior
Filtered domains for web search should allow a web search only in those sites when signaled.
Actual Behavior
If filtered domains are listed, the web search isn't performed and the error shown is "An error occurred while searching the web" in the interface
Steps to Reproduce
Admin > Web Search > list some domain in Domain filters list
Then activate the web search in a chat and see what happens
Logs & Screenshots
Additional Information
No response
@pr-validator-bot commented on GitHub (Mar 4, 2026):
⚠️ Invalid Issue Title
Hey @nsfregola-maker, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:" or "feat:") make it difficult for volunteer contributors to understand and triage issues.
Please update the title to reflect the content of your issue.
⚠️ Missing Issue Title Prefix
@nsfregola-maker, your issue title is missing a prefix (e.g.,
bug:,feat:,docs:).Please update your issue title to include one of the following prefixes:
Example:
bug: Login fails when using special characters in password@Classic298 commented on GitHub (Mar 4, 2026):
@nsfregola-maker there is a misunderstanding.
As per the docs, this is a FILTER list, not an allowlist
essentially: the domains you enter get FILTERED and are NOT fetched.
This is a security feature to prevent SSRF attacks.
Making this filter allow-list based (as you want it to: only search on rottentomatoes) would benefit you, but would destroy 99.999% of deployments out there that rely on this being a blocklist.
Also, you can't really use an allowlist for this anyways, since we are talking about the internet.
You can't make an allowlist for the internet
@Classic298 commented on GitHub (Mar 4, 2026):
https://docs.openwebui.com/reference/env-configuration#web_fetch_filter_list