fix: [ISSUE] Bundled qdrant server (v1.8.3) incompatible with qdrant-client 1.16, vector db test connection fails with 404 error

[amanattrish]

Describe the bug

On a fresh setup (./run-platform.sh), adding the bundled Qdrant as a vector database during onboarding fails. "Test Connection" returns: "Error testing ''. Unexpected Response: 404 (Not Found)..."

To reproduce

1. Run ./run-platform.sh and log in.
2. Onboarding >> Connect a Vector Database >> Qdrant.
3. Add Name of vector DB, URL: http://unstract-vector-db:6333, no API key.
4. Click Test Connection.

Expected behavior

It should connect without any problem.

Environment details

• Version v0.173.0 of unstarct
• OS: Ubuntu

Screenshots

[amanattrish]

Root Cause:

The Python client and the bundled server are far apart in version. Backend logs:
qdrant.py:67: UserWarning: Qdrant client version 1.16.2 is incompatible with server version 1.8.3. Major versions should match and minor version difference must not exceed 1.
...
Error occured while testing adapter Unexpected Response: 404 (Not Found)

Network connectivity is fine (curl to the container returns the version JSON). The 1.16 client calls an API path the 1.8.3 server does not have, so it gets a 404

The two pins have drifted:

• docker/docker-compose-dev-essentials.yaml pins qdrant/qdrant:v1.8.3, last touched in Version roll over for qdrant client #185 (Mar 2024)
• unstract/sdk1/pyproject.toml pins qdrant-client>=1.16.0,<1.17.0, bumped in [FIX] Pin qdrant-client<1.17.0 and enhance uv-lock transitive dep detection #1845 (Mar 2026)

[amanattrish]

Suggested fix:
Bump the Qdrant server image to a 1.16.x tag to match the client. v1.16.1 lines up with the installed client version.