Cannot connect supabase vector store to n8n without URL credentials.

[sappireflames000]

Hello, I am locally hosting n8n and supabase within a ubuntu 24.02 machine inside docker. Both containers are fresh, without any customization. HOWEVER. I cannot connect to supabase using only the URL and service role secret. I always end with AUTH error with wrong credentials. I MUST use the dashboard credentials inside the URL EX: http://[USER DASHBOARD]:[PASSWORD DASHBOARD]@[LOCAL DOMAIN]:8000. Both installs are fresh like I said, as well as the ubuntu VM I am running them in, But my workflows are complaining about this. Giving errors such as: Request cannot be constructed from a URL that includes credentials. Any help on this matter would be much appreciated. I honestly don't understand what my problem is here. I've reinstalled multiple times, it doesn't make sense.

[onestardao]

short answer: the problem is using credentials inside the URL. many libs (and n8n’s nodes) refuse URLs with embedded user:pass and expect a clean base URL + a separate auth key/credential field. this causes the “request cannot be constructed from a URL that includes credentials” error you see.

quick checklist (try in this order)

1. use the base supabase url only (no user:pass@host), e.g. https://your-project.supabase.co
2. put the service_role or anon key into n8n’s credential field / env var (DO NOT embed in the URL)
3. for server-side vector ops use the service_role key (server-to-server), anon is for client flows
4. confirm n8n can reach the host (docker network / port mapping) and that the key you supply matches the project
5. if the node still errors, switch to passing the url+key via environment variables (safer in docker) and restart

maps to ProblemMap No.14 (bootstrap/credential ordering).
want me to paste the minimal n8n credential snippet + docker env example?

[dtoebe]

yes

[onestardao]

This error happens because n8n (and many libs) don’t accept embedded user/pass in the URL.
Use a clean Supabase URL (e.g. https://your-project.supabase.co) + pass the API key in the credential field or env var.
It maps to a bootstrap/credential ordering issue (ProblemMap No.14).
Full triage + Dr. WFGY ER here if you want the detailed checklist:
👉 https://github.com/onestardao/WFGY/blob/main/ProblemMap/GlobalFixMap/README.md