pyspur icon indicating copy to clipboard operation
pyspur copied to clipboard

Qdrant connection troubles

Open martinmalek opened this issue 8 months ago • 1 comments

I'm running a self hosted qdrant with an internal dns at https://qdrant.mydomain.org. Port 443 redirecting to 6333.

However it seems that the client insists on using the grpc port at 6334 which of course isn't available in this setup.

Is the grpc connection needed?

Error processing documents: <_InactiveRpcError of RPC that terminated with: status = StatusCode.UNAVAILABLE details = "failed to connect to all addresses; last error: UNKNOWN: ipv4:192.168.70.20:6334: Failed to connect to remote host: getsockopt(SO_ERROR): No route to host (113)" debug_error_string = "UNKNOWN:Error received from peer {grpc_message:"failed to connect to all addresses; last error: UNKNOWN: ipv4:192.168.70.20:6334: Failed to connect to remote host: getsockopt(SO_ERROR): No route to host (113)", grpc_status:14, created_time:"2025-04-15T15:49:16.395599507+00:00"}" >

martinmalek avatar Apr 15 '25 15:04 martinmalek

I noticed in the code you prefer the GRPC way

self._client = qdrant_client.QdrantClient(
      url=QDRANT_URL,
      port=int(QDRANT_PORT),
      grpc_port=int(QDRANT_GRPC_PORT),
      api_key=QDRANT_API_KEY,
      prefer_grpc=True,
      timeout=10,)

I got around it by creating a new k8s ingress with nginx.ingress.kubernetes.io/backend-protocol: "GRPC" and setting QDRANT_GRPC_PORT: "443"

martinmalek avatar Apr 15 '25 17:04 martinmalek