Cannot access selfhosted qdrant vector store

nlogothetis · November 26, 2024, 12:05pm

Hi there,

I have a selfhosted qdrant running on a cloud, it is properly deployed with API key, but n8n cannot access any collections. Here is the strange part:
When I provide the credentials (API-Key and URL) the connection is always tested successfully, no matter what API key is provided, even the correct one.
When I use a qdrant vector store through the ‘official’ qdrant page, it works.
Anyone experience the same issues?

n8n version: 1.68.0
Database: default
EXECUTIONS_PROCESS default
Running n8n via Docker (compose)
Operating system: Linux

n8n · November 26, 2024, 12:05pm

It looks like your topic is missing some important information. Could you provide the following if applicable.

n8n version:
Database (default: SQLite):
n8n EXECUTIONS_PROCESS setting (default: own, main):
Running n8n via (Docker, npm, n8n cloud, desktop app):
Operating system:

Jon · December 8, 2024, 12:33am

Hey @nlogothetis

Are you running both in containers and are you trying to use 127.0.0.1 or localhost as the address for qdrant? If you are can you try 172.17.0.1 instead or the ip of the machine running qdrant

nlogothetis · December 11, 2024, 11:35pm

Hey Jon,

both running on my Hetzner Cloud, accessible through a URL. Both run in a docker container managed by Coolify. If I use tools like langflow or flowise, this problem does not occur, only in n8n.

Nafuna_TV · December 14, 2024, 6:45pm

Having the same issue on n8n on coolify. qdrant node goes green to say connectin successful then when i try, it wont work. Says unable to fetch. Log files on the containers show connections rejected, I dont know why

nlogothetis · December 23, 2024, 8:59pm

Hey there,
seems that nobody has a solution for this… I tried everything, even hardcode the API keys within the files in the container, no luck. Meanwhile I switched to Supabase, since QDrant is useless in n8n.

Gijs_Epping · January 27, 2025, 10:26am

Strainge thing is if you call Qdrant with a normal HTTP node it works fine.

carlosmachinp · January 29, 2025, 10:13pm

Same problem here. I have Qdrant in coolify. And I can call Qdrant from HTTP node but I get fetch failed when I try to use Qdrant vector store

nlogothetis · February 3, 2025, 6:01am

Hello there,

may I ask how your setup is with coolify? How did you connect the domain to Coolify? Are you using a reverse proxy like cloudflare?

Jack · February 4, 2025, 12:37pm

Same problem the N8N Qdrant node doesn’t work.

I can put a test PUT request through via an HTTP node using the same credentials and create a collection using the same credentials.

It looks like the N8N Qdrant integration is broken at the moment.

codeculture · February 7, 2025, 11:57am

Same problem for me, any solution?

I have qdrant running behind a proxy, can call the UI and N8N connection says “successful”, but on insert i get “fetch failed”.
If i try the same in qdrant cloud (just different credentials and url) it works out of the box.

Jack · February 12, 2025, 7:45pm

As a workaround I connected via http rather than https and it worked.

nlogothetis · February 20, 2025, 12:01am

Unfortunately it doesn’t work for me

githubber · February 21, 2025, 1:39pm

Same here

Both running on Docker next to each other. The API Key settings gives successful message all the time but the Vector Store can’t connect. The logs show fetch failed only.

I tried using both service address with plain HTTP (such as http://n8n-qdrant/) or HTTPS with a reverse proxy (such as https://qdrant.example.com/) but it doesn’t help. No matter I do, the node fails to connect. Regular request execution works. Also, the Qdrant dashboard works. All with the same API key. I don’t understand what’s the problem.

n8n Version: 1.80.0
Qdrant version: 1.13.4

githubber · February 21, 2025, 1:52pm

I also tried setting the URL to https://qdrant.example.com/collections/ if it helps but not. I suppose the protocol and the hostname should be enough.

githubber · February 21, 2025, 2:27pm

SOLVED!

I only exposed port 6333 (HTTP REST API) so far, but now, I exposed 6334 (gRPC API), and it works!

This is what I set now along with the API Key as Qdrant URL, and now the node works fine: http://n8n-qdrant:6333/

N8n probably tries to connect via gRPC or has the port numbers hardcoded, IDK.

nlogothetis · February 22, 2025, 9:17am

Hey githubber,

I don’t understand, you expose 6334, which (as far as I experienced) is always exposed if you deploy it, and then you use http://xxxxxxxx:6333 in the Credentials in n8n?
Unfortunately this doesnt work for me. Anything else you set up? How does the docker compose file look like? How (or on which platform (Coolify/Dokploy etc.)) did you host it?

githubber · February 22, 2025, 9:38am

This is exactly what I did. I exposed the gRPC port on the container and on the service, and it started working with http://n8n-qdrant:6333/ as the URL along with the API key. Previously, only the HTTP port was exposed, and I mapped it to port 80. Keeping it on 6333 and exposing 6334 solved it for me.

I’m on mobile now, so forgive me the screenshots form the code.

nlogothetis · February 22, 2025, 9:40am

OK, let me try this. And many many thanks for your quick reply

nlogothetis · February 22, 2025, 9:56am

I have this part of the definition:

ports:
  - 6333:6333
  - 6334:6334
expose:
  - 6333
  - 6334
  - 6335

But it still doesnt work.