Qdrant Vector Store fails with Qdrant 1.19.x because bundled @qdrant/js-client-rest is outdated

[gokhanmms]

Bug Description

The built-in Qdrant Vector Store node fails with fetch failed when connecting to Qdrant Server 1.19.x.

The same Qdrant server and credentials work correctly with the separately maintained official n8n-nodes-qdrant community node. That node can list collections and successfully execute operations such as Get Collection.

The issue appears to be the same compatibility problem previously reported in #22159.

n8n currently bundles @qdrant/js-client-rest as ^1.16.2 in @n8n/nodes-langchain, while the Qdrant server is running 1.19.x.

Qdrant's JavaScript client performs a version compatibility check and rejects server versions when the minor version difference is too large. As a result, the built-in Qdrant Vector Store fails before the request completes and n8n only surfaces the generic fetch failed error.

This also affects the collection dropdown, which displays:

Could not load list
fetch failed

Entering the collection name manually does not solve the issue. Executing the Vector Store node still results in fetch failed.

The setup had been working correctly for a long time before the Qdrant server version moved ahead of the client bundled by n8n.

The official Qdrant team has also confirmed that this is caused by the fixed/outdated @qdrant/js-client-rest version bundled with the built-in n8n Qdrant Vector Store node.

Qdrant Vector Store → Could not load list / fetch failed

Official Qdrant node → Get Collection

Could you please update the bundled Qdrant client and consider avoiding a fixed client/server compatibility gap that causes the integration to break again whenever Qdrant advances by several minor versions?

To Reproduce

1. Run Qdrant Server 1.19.x.
2. Run n8n 2.37.10
3. Add the built-in "Qdrant Vector Store" node.
4. Configure valid Qdrant credentials.
5. Open the Qdrant Collection dropdown.
6. Observe that the collection list fails to load with:
   "Could not load list - fetch failed".
7. Enter a valid collection name manually.
8. Execute the Qdrant Vector Store node.
9. Observe that execution also fails with:
   "fetch failed".
10. Add the separately maintained official n8n-nodes-qdrant community node using the same Qdrant URL and credentials.
11. Observe that collections load correctly and operations such as Get Collection execute successfully.

Expected behavior

The built-in Qdrant Vector Store node should work with the current stable Qdrant Server version.

The collection dropdown should list available collections, and Vector Store operations should execute successfully.

The bundled @qdrant/js-client-rest dependency should be updated to a version compatible with Qdrant 1.19.x.

This is effectively a recurrence of #22159, which was previously fixed by upgrading the bundled Qdrant client.

Debug Info

Additional context:

Qdrant Server: 1.19.x

The separately maintained n8n-nodes-qdrant community node works correctly against the same server using the same credentials.

The built-in @n8n/n8n-nodes-langchain package currently declares:

"@qdrant/js-client-rest": "^1.16.2"

Related previous issue:
#22159 - Qdrant Vector Store node cannot be compatible with Qdrant server v1.16.0 because the client version is fixed.

Debug info

core

• n8nVersion: 2.37.10
• platform: docker (self-hosted)
• nodeJsVersion: 26.5.1
• nodeEnv: production
• database: postgres
• executionMode: scaling (single-main)
• concurrency: -1
• license: enterprise (production)
• consumerId: 5e1c0a76-9e94-4128-83b5-30806ab75913

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: database

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/152.0.0.0 safari/537.36
• isTouchDevice: false

cluster

• instanceCount: 2
• versions: 2.37.10
• instances:
  • instanceKey: d3f69121-66e1-48ef-9024-42b9e0603f6e, hostId: worker-ae4a357067e2, instanceType: worker, instanceRole: unset, version: 2.37.10
  • instanceKey: 0d3beaef-c507-43b8-bd2c-18e941c9172e, hostId: main-cad1de6004e0, instanceType: main, instanceRole: leader, version: 2.37.10
• checks:
  • check: hostid-clash, status: succeeded, warnings: -
  • check: lifecycle, status: succeeded, warnings: -
  • check: split-brain, status: succeeded, warnings: -
  • check: version-mismatch, status: succeeded, warnings: -

Generated at: 2026-09-05T07:28:48.942Z

Operating System

Ubuntu 24.04.4

n8n Version

2.37.10

Node.js Version

26.5.1

Database

PostgreSQL

Execution mode

main (default)

Hosting

self hosted

[n8n-assistant]

Hey @gokhanmms,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-9420".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-9420