I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
v0.6.34
Ollama Version (if applicable)
0.12.9
Operating System
Linux + Docker (Devuan Daedalus)
Browser (if applicable)
Google-Chrome-141.0.7390.122
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
When Google PSE is configured, I should see search results included in the model context window.
Side note: If I have my token restricted to just my domain (in the case of key leaks), I should still see search results and not have to make my PSE token insecure by letting unrestricted access to the token.
Expected results:
Actual Behavior
I get 403 from Google in the exception stack from Open WebUI. I've attached logs and evidence.
Deep research revealed Open WebUI is not sending the "Referer" header when reaching out to Google PSE.
I attached curl-requests.log as well so you can see the difference between the HTTP calls.
Originally created by @markizano on GitHub (Nov 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18870
### 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 am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.6.34
### Ollama Version (if applicable)
0.12.9
### Operating System
Linux + Docker (Devuan Daedalus)
### Browser (if applicable)
Google-Chrome-141.0.7390.122
### 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
When Google PSE is configured, I should see search results included in the model context window.
Side note: If I have my token restricted to just my domain (in the case of key leaks), I should still see search results and not have to make my PSE token insecure by letting unrestricted access to the token.
Expected results:
<img width="1214" height="692" alt="Image" src="https://github.com/user-attachments/assets/a451d7d6-6759-46a8-a1aa-0ad15006ceb6" />
### Actual Behavior
I get 403 from Google in the exception stack from Open WebUI. I've attached logs and evidence.
Deep research revealed Open WebUI is not sending the "Referer" header when reaching out to Google PSE.
I attached [curl-requests.log](https://github.com/user-attachments/files/23292113/curl-requests.log) as well so you can see the difference between the HTTP calls.
<img width="1386" height="282" alt="Image" src="https://github.com/user-attachments/assets/ae7d910d-02e7-483f-9b49-ada226e42dfb" />
### Steps to Reproduce
1. Follow install instructions.
2. Navigate to Admin.
3. Configure [Google PSE](https://developers.google.com/custom-search/v1/overview) as per [the documentation](https://docs.openwebui.com/category/-web-search/). (note about this below).
4. Open a new chat and ask a question with "web search" enabled.
5. Observe the exception from the logs indicating the 403.
Credentials configuration note:
<img width="642" height="752" alt="Image" src="https://github.com/user-attachments/assets/3cd3ae5b-41c0-4fbd-abd2-12faaee26f8a" />
I had my key configured to be restricted to just my domain.
### Logs & Screenshots
[stack-trace.log](https://github.com/user-attachments/files/23292103/stack-trace.log)
### Additional Information
I have forked the project and [have submitted a PR](https://github.com/open-webui/open-webui/pull/18871) with the fix!
GiteaMirror
added the bug label 2026-05-15 14:19:45 -05:00
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 @markizano on GitHub (Nov 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18870
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.34
Ollama Version (if applicable)
0.12.9
Operating System
Linux + Docker (Devuan Daedalus)
Browser (if applicable)
Google-Chrome-141.0.7390.122
Confirmation
README.md.Expected Behavior
When Google PSE is configured, I should see search results included in the model context window.
Side note: If I have my token restricted to just my domain (in the case of key leaks), I should still see search results and not have to make my PSE token insecure by letting unrestricted access to the token.
Expected results:
Actual Behavior
I get 403 from Google in the exception stack from Open WebUI. I've attached logs and evidence.
Deep research revealed Open WebUI is not sending the "Referer" header when reaching out to Google PSE.
I attached curl-requests.log as well so you can see the difference between the HTTP calls.
Steps to Reproduce
Credentials configuration note:
I had my key configured to be restricted to just my domain.
Logs & Screenshots
stack-trace.log
Additional Information
I have forked the project and have submitted a PR with the fix!
@tjbck commented on GitHub (Nov 4, 2025):
Should be addressed in dev!