mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 19:08:59 -05:00
External VectorDB QDRANT #3299
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jjamgmv on GitHub (Jan 16, 2025).
Bug Report
Installation Method
[Describe the method you used to install the project, e.g., git clone, Docker, pip, etc.]
Environment
Open WebUI Version: 0.5.4
Ollama (if applicable): 0.5.4
Operating System: HELM
Browser (if applicable): EDGE
Confirmation:
Expected Behavior:
The service should successfully connect to Qdrant using the provided configuration values, allowing the creation and querying of collections without connection errors.
Actual Behavior:
The service throws an httpcore.ConnectTimeout error when attempting to connect to the configured Qdrant endpoint.
Description
Bug Summary:
The system cannot establish a connection to Qdrant using the provided URI and API key. This issue occurs when trying to save documents to the vector database.
Reproduction Details
Steps to Reproduce:
Configure the following environment variables in the application:
VECTOR_DB: qdrant
QDRANT_URI: "https://qdrant.XXX.com"
QDRANT_API_KEY: "XXX"
Upload a PDF file through the user interface or API.
Observe the logs generated during the file processing.
Logs and Screenshots
Browser Console Logs:Not applicable in this case.
Docker Container Logs:
httpcore.ConnectTimeout: timed out
fastapi.exceptions.HTTPException: 400: timed out
(See detailed logs provided above).
Screenshots/Screen Recordings (if applicable):Attach any relevant screenshots of the configuration or UI, if applicable.
Additional Information
The Qdrant endpoint configuration appears correct, but the error indicates a connectivity issue (e.g., firewall, DNS, SSL certificate, or incorrect endpoint).
It was verified that the endpoint is accessible from the work network using external tools like curl.
No prior configuration issues were identified in VECTOR_DB_CLIENT.
Note
This report includes all necessary information to reproduce and diagnose the issue. Please verify connectivity to the endpoint and check for potential network restrictions or incompatibilities with the HTTP client being used.