I’m running both n8n and a self-hosted Supabase stack in Docker on the same user-defined network. Supabase uses Kong as an API gateway (container port 8000→host 18000) in front of PostgREST (“supabase-rest” on port 3000→3011). In n8n’s Supabase credentials I’ve tried http://supabase-kong:8000 (and https://supabase-kong:8443) with the correct Service Role Key, but it always returns “Unauthorized” or “Not Found.” From inside the network a bare curl http://kong:18000/rest/v1 gives 401 as expected, but n8n never authenticates. What exact Host URL and credential setup does the n8n Supabase node expect for a self-hosted Supabase+Kong deployment?
The domain looks super strange to me
If the supabase is local
Should be localhost ?
If you have set domain to it. Should be aaa .com or aaa .bb ?
Thanks for your comment!
n8n and Supabase (including Kong and PostgREST) run in separate Docker containers on the same custom network. Inside the n8n container, localhost points to n8n itself, not to Kong or other services.
To reach other containers, I use their service names like supabase-kong:8000. This works fine for Postgres and Zep, but for some reason Kong doesn’t respond, even though everything is set up the same. Still trying to figure out why.
1 Like