Can't reach database server at `aws-0-ap-southeast-1.pooler.supabase.com:6543

[maikusobu]

I had tried 2 ways to make the connection:
first one conformed to the documents, it also resulted in error like that
the second:

DATABASE_URL="postgres://postgres.cekcaxveddzfhnmtamgx:[YOUR PASSWORD]@aws-0-ap-southeast-1.pooler.supabase.com:6543/postgres?pgbouncer=true&connection_limit=1"
DIRECT_URL="postgres://postgres.cekcaxveddzfhnmtamgx:[YOUR PASSWORD]@aws-0-ap-southeast-1.pooler.supabase.com:5432/postgres"

file schema.js

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider  = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DIRECT_URL")
}

[naeem-qv]

That is something not specific with supabase, I'm facing the same issue with prisma. I tried Neon, Supabase, vercel postgres and local postgreSQL, And found out it happens least with vercel postgres and never happens with local postgreSQL. I'm sure there's something wrong with prisma here

[ludralph]

Hi @maikusobu 👋

Thank you for raising this question.

Can you make sure your password doesn't have any characters in it like a @ for instance? Also try connecting with a Postgres GUI client from your computer, something like TablePlus or BeeKeeper Studio. You may also need to percentage encode special characters in your password.

[janpio]

PgAdmin is not Prisma, so you will have to possible percentage encode these characters as @ludralph shared.

[maikusobu]

@janpio it still not be fixed

[ludralph]

Hi @maikusobu, You would need to percent encode the & character in your password. You can take a look at characters that need to be encoded here.

[maikusobu]

@ludralph , i had changed, but the issue still persists. I think there's something wrong with prisma, because when I change the network, the prisma works fine but after sometimes it becomes wrong again

[naeem-qv]

@ludralph , i had changed, but the issue still persists. I think there's something wrong with prisma, because when I change the network, the prisma works fine but after sometimes it becomes wrong again

Exactly this happens. 👆 @ludralph

[naeem-qv]

Hi @maikusobu 👋

Thank you for raising this question.

Can you make sure your password doesn't have any characters in it like a @ for instance? Also try connecting with a Postgres GUI client from your computer, something like TablePlus or BeeKeeper Studio. You may also need to percentage encode special characters in your password.

Hello @ludralph 👋, I wanted to share this from a long time about this strange behavior from Prisma where a message shows in the terminal exactly same as "Can't reach database server at ...."
I'm 101% sure everytime that my connection string is correct and working. So running something like Prisma generate or Prisma studio in terminal solves the problem. But the problem is we can do this in the dev environment but not in the prod. Please suggest something I've tried many services like neon,vercel postgres, supabase, railway etc... but found this issue in everyone of them with prisma.

[ludralph]

Hi @naeem-qv, what version of Prisma are you using and do you have a reproduction that you can share?

[naeem-qv]

Hi @naeem-qv, what version of Prisma are you using and do you have a reproduction that you can share?

prisma v5.10.2, as it happens very rarely I can't give a solid reproduction for it. But one thing I'm sure that it happens with all serverless progress connection strings. I've never encountered it with localhost:5432

[irfnrdh]

any update?

[naeem-qv]

any update?

Sadly No😞

[Capovilaa]

It was fixed? I'm facing this same issue right know :(

[Capovilaa]

Are you using a company's network?

[naeem-qv]

It was fixed? I'm facing this same issue right know :(

No it's not 😢

[Capovilaa]

I just fixed this issue changing my network connection, I was in my company one and switched for my personal

[naeem-qv]

I just fixed this issue changing my network connection, I was in my company one and switched for my personal

Which db though?? 🤔

[fabianamino]

⨯ PrismaClientInitializationError:
Invalid prisma.user.findUnique() invocation:

Can't reach database server at aws-0-eu-central-1.pooler.supabase.com:6543
I have tried everything on the internet, but to no avail

[naeem-qv]

⨯ PrismaClientInitializationError:
Invalid prisma.user.findUnique() invocation:

Can't reach database server at aws-0-eu-central-1.pooler.supabase.com:6543
I have tried everything on the internet, but to no avail

Which db are you using??

[robertoyamanaka]

Hello, I was facing the same issue and solved it encoding some values in my db password.

In my case, the DB password included $ and & characters. These characters were causing connection issues due to their special meanings in URLs and environment variables. To resolve this, I URL-encoded these characters in my .env file. Specifically, I replaced $ with %24 and & with %26.

Hope this helps.

[maikusobu]

mine still the same

[Tarkbyte]

Hello, I am facing the same problem without being able to solve it, my password doesn't contain any special characters

[naeem-qv]

Hello, I am facing the same problem without being able to solve it, my password doesn't contain any special characters

Sadly me too, my password is a simple "abcd" string but still I'm facing the issue 😔

[sutek99]

Having this exact same issue (different AWS region). If I remove the "&pgbouncer=true" I can actually connect to the DB until I re-start the service (all happening on local). After I restart the service I start to get the errors regarding prepared statements (which makes sense).

When I add the "&pgbouncer=true" to the connection string I get the "PrismaClientInitializationError: Can't reach database server at ____" error.

[ludralph]

Hi @sutek99

For pgbouncer version 1.22.0 and above, can you please take a look at this recommended setup as stated in this issue

[batmanSix]

prisma version 5.12.1 Still appear Can't reach database server at `aws-0-ap-southeast-1.pooler.supabase.com:6543

[huseyin-lora]

Check out these sources:
https://vercel.com/guides/nextjs-prisma-postgres
https://supabase.com/partners/integrations/prisma

[AdarshJaiswal031]

Add the end of Database Url
?pgbouncer=true

Update the prisma to latest. My version
prisma@5.13.0

[AlamMena]

I encountered a similar issue with Supabase and Prisma. I resolved it by disabling connection pooling and copying the connection string.

pooling option on supabase

[Anonymous-hss]

facing the same issue changed my password even tried changin account didn't work !!

[JovanJevtic]

+1

[Anonymous-hss]

Hey everyone, I kind off found the solution for those of you who where using superbase db with prisma I would suggest not to use Superbase db, Just use Neon instead. Neon gave me Database_url and everything worked fine.

[JovanJevtic]

So, I have refreshed my supabase project and following the Prisma docs to the DATABASE_URL I added &pgbouncer=true. Also, I have updated prisma to 5.13.0. Now it's working

[lahammam]

the same error, it work in fibre optique but when I switch to another network, I get error
Please make sure your database server is running at aws-0-eu-central-1.pooler.supabase.com:5432.