Docker compose installation using official image ghcr.io/open-webui/open-webui:main
Environment
Open WebUI Version: main
Ollama: Native installation on host system
Operating System: AlmaLinux
Browser: Firefox
Confirmation:
I have read and followed all the instructions provided in the README.md.
I am on the latest version of both Open WebUI and Ollama.
I have included the Docker container logs.
I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
Expected Behavior:
Web search functionality should work with configured search backend (Bing).
Actual Behavior:
Web search returns empty content error:
[ERROR: The content provided is empty. Please ensure that there is text or data present before proceeding.]
Description
Bug Summary:
Web search functionality fails with empty content error when using Bing as search backend. The error occurs consistently across different search queries.
Reproduction Details
Steps to Reproduce:
Configure OpenWebUI with Bing search backend in docker-compose.yml
Start containers using docker-compose up -d
Access web interface and attempt any web search
Observe empty content error in UI and logs
Logs and Screenshots
Docker Container Logs:
Fetching pages: 0it [00:00, ?it/s]
INFO [open_webui.apps.retrieval.main] save_docs_to_vector_db: document e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b85
ERROR [open_webui.apps.retrieval.main] The content provided is empty. Please ensure that there is text or data present before proceeding.
Traceback (most recent call last):
File "/app/backend/open_webui/apps/retrieval/main.py", line 1330, in process_web_search
save_docs_to_vector_db(docs, collection_name, overwrite=True)
File "/app/backend/open_webui/apps/retrieval/main.py", line 799, in save_docs_to_vector_db
raise ValueError(ERROR_MESSAGES.EMPTY_CONTENT)
ValueError: The content provided is empty. Please ensure that there is text or data present before proceeding.
Additional Information
Using docker-compose with PostgreSQL database
Database tables are properly created and accessible
Basic chat functionality with Ollama works correctly
Ollama ist installed nativly directly on the server
Only web search functionality is affected
Tried with different search backends (DuckDuckGo, Bing) with same result
Test OpenWebui on my workstation with the Bing credentials that works fine. I asume there is a configuration issue with my docker network or config
I have configured the websearch inside the gui and not over the compose file
my docker compose file
Yes I know WEBUI_CHECK_UPDATE is an open point....
Originally created by @unicorn667 on GitHub (Dec 4, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7591
## Installation Method
Docker compose installation using official image ghcr.io/open-webui/open-webui:main
## Environment
- **Open WebUI Version:** main
- **Ollama:** Native installation on host system
- **Operating System:** AlmaLinux
- **Browser:** Firefox
**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 and Ollama.
- [x] I have included the Docker container logs.
- [x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
## Expected Behavior:
Web search functionality should work with configured search backend (Bing).
## Actual Behavior:
Web search returns empty content error:
```
[ERROR: The content provided is empty. Please ensure that there is text or data present before proceeding.]
```
## Description
**Bug Summary:**
Web search functionality fails with empty content error when using Bing as search backend. The error occurs consistently across different search queries.
## Reproduction Details
**Steps to Reproduce:**
1. Configure OpenWebUI with Bing search backend in docker-compose.yml
2. Start containers using docker-compose up -d
3. Access web interface and attempt any web search
4. Observe empty content error in UI and logs
## Logs and Screenshots
**Docker Container Logs:**
```
Fetching pages: 0it [00:00, ?it/s]
INFO [open_webui.apps.retrieval.main] save_docs_to_vector_db: document e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b85
ERROR [open_webui.apps.retrieval.main] The content provided is empty. Please ensure that there is text or data present before proceeding.
Traceback (most recent call last):
File "/app/backend/open_webui/apps/retrieval/main.py", line 1330, in process_web_search
save_docs_to_vector_db(docs, collection_name, overwrite=True)
File "/app/backend/open_webui/apps/retrieval/main.py", line 799, in save_docs_to_vector_db
raise ValueError(ERROR_MESSAGES.EMPTY_CONTENT)
ValueError: The content provided is empty. Please ensure that there is text or data present before proceeding.
```
## Additional Information
- Using docker-compose with PostgreSQL database
- Database tables are properly created and accessible
- Basic chat functionality with Ollama works correctly
- Ollama ist installed nativly directly on the server
- Only web search functionality is affected
- Tried with different search backends (DuckDuckGo, Bing) with same result
- Test OpenWebui on my workstation with the Bing credentials that works fine. I asume there is a configuration issue with my docker network or config
I have configured the websearch inside the gui and not over the compose file

my docker compose file
Yes I know WEBUI_CHECK_UPDATE is an open point....
`version: '3.8'
services:
postgres:
image: postgres:14.5
container_name: webui-postgres
restart: unless-stopped
environment:
POSTGRES_DB: webui
POSTGRES_USER: webui_user
POSTGRES_PASSWORD: password
POSTGRES_HOST_AUTH_METHOD: trust
volumes:
- postgres_data:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U webui_user -d webui"]
interval: 10s
timeout: 5s
retries: 5
networks:
- proxy-net
open-webui:
image: ghcr.io/open-webui/open-webui:main
container_name: open-webui
restart: unless-stopped
depends_on:
postgres:
condition: service_healthy
ports:
- "3000:8080"
environment:
- OLLAMA_API_BASE_URL=http://host.docker.internal:11434
- DATABASE_URL=postgresql://webui_user:password@postgres:5432/webui
- POSTGRES_HOST=postgres
- POSTGRES_DB=webui
- POSTGRES_USER=webui_user
- POSTGRES_PASSWORD=password
- CORS_ALLOW_ORIGIN=https://myurl
- HOST=0.0.0.0
- PORT=8080
- MICROSOFT_CLIENT_ID=12345456
- MICROSOFT_CLIENT_SECRET=12345456
- MICROSOFT_CLIENT_TENANT_ID=12345456
- OAUTH_PROVIDERS=microsoft
- ENABLE_OAUTH_SIGNUP=true
- BASE_URL=https://myurl
- WEBUI_CHECK_UPDATE=false
- WEBUI_NOTIFY_UPDATE=false
- WEBUI_DISABLE_UPDATE_CHECK=true
- DISABLE_LOCAL_REGISTRATION=true
volumes:
- /srv/docker/openwebui/data:/app/backend/data
extra_hosts:
- "host.docker.internal:host-gateway"
networks:
- proxy-net
volumes:
postgres_data:
name: webui-postgres-data
networks:
proxy-net:
external: True`
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 @unicorn667 on GitHub (Dec 4, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7591
Installation Method
Docker compose installation using official image ghcr.io/open-webui/open-webui:main
Environment
Confirmation:
Expected Behavior:
Web search functionality should work with configured search backend (Bing).
Actual Behavior:
Web search returns empty content error:
Description
Bug Summary:
Web search functionality fails with empty content error when using Bing as search backend. The error occurs consistently across different search queries.
Reproduction Details
Steps to Reproduce:
Logs and Screenshots
Docker Container Logs:
Additional Information
I have configured the websearch inside the gui and not over the compose file
my docker compose file
Yes I know WEBUI_CHECK_UPDATE is an open point....
`version: '3.8'
services:
postgres:
image: postgres:14.5
container_name: webui-postgres
restart: unless-stopped
environment:
POSTGRES_DB: webui
POSTGRES_USER: webui_user
POSTGRES_PASSWORD: password
POSTGRES_HOST_AUTH_METHOD: trust
volumes:
- postgres_data:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U webui_user -d webui"]
interval: 10s
timeout: 5s
retries: 5
networks:
- proxy-net
open-webui:
image: ghcr.io/open-webui/open-webui:main
container_name: open-webui
restart: unless-stopped
depends_on:
postgres:
condition: service_healthy
ports:
- "3000:8080"
environment:
- OLLAMA_API_BASE_URL=http://host.docker.internal:11434
- DATABASE_URL=postgresql://webui_user:password@postgres:5432/webui
- POSTGRES_HOST=postgres
- POSTGRES_DB=webui
- POSTGRES_USER=webui_user
- POSTGRES_PASSWORD=password
- CORS_ALLOW_ORIGIN=https://myurl
- HOST=0.0.0.0
- PORT=8080
- MICROSOFT_CLIENT_ID=12345456
- MICROSOFT_CLIENT_SECRET=12345456
- MICROSOFT_CLIENT_TENANT_ID=12345456
- OAUTH_PROVIDERS=microsoft
- ENABLE_OAUTH_SIGNUP=true
- BASE_URL=https://myurl
- WEBUI_CHECK_UPDATE=false
- WEBUI_NOTIFY_UPDATE=false
- WEBUI_DISABLE_UPDATE_CHECK=true
- DISABLE_LOCAL_REGISTRATION=true
volumes:
- /srv/docker/openwebui/data:/app/backend/data
extra_hosts:
- "host.docker.internal:host-gateway"
networks:
- proxy-net
volumes:
postgres_data:
name: webui-postgres-data
networks:
proxy-net:
external: True`