Problem with Supavisor and Prisma
I'm trying to connect to Supavisor with Prisma an I get this error in the console:
✖ Introspecting based on datasource defined in prisma/schema.prisma
Error: P1001
Can't reach database server at
supabase.justware.it:5432
Please make sure your database server is running at supabase.justware.it:5432.
This is my connection URL:
postgresql://prisma.[TENANT]:[PSW]@supabase.justware.it:5432/postgres25 Replies
This is the error I'm getting from the Supavisor container
This is my docker-compose
This is my pooler.exs
I’m using Coolify to deploy my Supabase instance
can you connect with the default postgres user?
No, I keep getting the same errors
The command I tries to run was
npx prisma db pull
Have you tried with psql or any other db client?
No
Try it. If you can connect via psql then its a prisma issue
psql: errore: connection to server at "supabase.justware.it" (91.99.201.191), port 5432 failed: FATAL: Authentication error, reason: "Authentication query failed: %DBConnection.ConnectionError{message: "connection not available and request was dropped from queue after 10000ms. This means requests are coming in and your connection pool cannot serve them fast enough. You can address this by:\n\n 1. Ensuring your database is available and that you can connect to it\n 2. Tracking down slow queries and making sure they are running fast enough\n 3. Increasing the pool_size (although this increases resource consumption)\n 4. Allowing requests to wait longer by increasing :queue_target and :queue_interval\n\nSee DBConnection.start_link/2 for more information\n", severity: :error, reason: :queue_timeout}"
This is the error I'm getting
This is with user
postgres or prisma?Both
In your dashboard, check Database > roles. See how many active connections are there
51 out of 100
And 0 prisma connection
have you recently updated db password?
No
Cant think of any other reason why you're facing this issue. Maybe try restarting the containers. See if that resolves the issue
I’ve already tried
Maybe is somenthing related to the Coolify Proxy?
was this working earlier?
I never tried
I was using the Supabase client, but now I want to start using Prisma
I am setting up an instance on coolify with your compose file. Will test connection with postgres user and also look at logs issue
This is the updated docker-compose
And this is the updated vector.yml
This seems to be the default one with container_name field?
I fixed the issue about the vector container editing the official supabase docker-compose
I edited also the vector.yml file so it is compatible with coolify
Whit this new docker-compose everything seems to work fine. I’ll do some other testing and I’ll let you know
For now everything works fine