Skip to content

Support QDRANT_URL with path prefix (reverse proxy deployments) #135

Description

@nadhub

When Qdrant is deployed behind a reverse proxy with a path prefix (e.g. https://myhost.com/qdrant), the current code passes the full URL to AsyncQdrantClient(location=...). The Qdrant Python client interprets this as a host and attempts to connect on port 6333, ignoring the path — causing a ConnectTimeout.

The fix is to parse the URL, extract the path as a prefix parameter, and pass it along with the correct port to AsyncQdrantClient.

This is a common deployment pattern (Kubernetes ingress, Nginx reverse proxy, Traefik, etc.).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions