Can't reach database Error

[akarpov91]

Hi there,

I’m building a prototype NextJs app using Prisma ORM and Supabase PostgresSQL database.

However, I’m receiving the following error:

Server Error
Error: 
Invalid `prisma.course.create()` invocation:


  Can't reach database server at `db.wzlsuclrgwfuyuedoehj.supabase.co`:`5432`

Please make sure your database server is running at `db.wzlsuclrgwfuyuedoehj.supabase.co`:`5432`.

Details:

M1 MacOS Monteray 12.0.1

Next.js v12.0.4

prisma : 3.5.0

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

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

DATABASE_URL="postgresql://postgres:[password]@db.wzlsuclrgwfuyuedoehj.supabase.co:5432/postgres”

Any assistence would be greatly appreciated.

[ericmarked]

same

[ltanady]

Can you send your project references to [email protected]? We'll take a look at this.

[silentworks]

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

[nimeshmaharjan1]

It was working then suddenly I got this error but I have not changed the password.

[MrJadaml]

Yup, I keep having the same issue on multiple test projects I've spun up. Also even swapped out to a new Supabase project, which worked at first then also suddenly stopped working.

https://vercel.com/guides/nextjs-prisma-postgres

[devknight216]

That's right. I am having same issues while using Prisma and Supabase. Still not sure what the reason is. Seems they are still unstable, not ready to be used by community.

[gijs-ve]

I get similar issues, sometimes its working fine but at other times I receive the connection error again.

[pileroniel]

Same , I'm also facing the same issue with prisma and supabase. And I have to restart the server again for it to work

[NikolaosArgy]

I am building a prototype and I am having the same problem. Everything worked fine and suddenly it stopped. I changed the password but still I can't connect. The other project works fine (I have two projects on Supabase). I tested both projects on TablePlus and DBeaver. One project connected normally, but the other did not, both with the same error.

weirdly Prisma Studio works fine, but Apollo GraphQL Studio does not.

[CloudInnovator]

Look at the appropriate connection pooling to use. Note that all Posgres SQL features only work with Session pooling setting See this link for more details https://supabase.com/docs/guides/database/connecting-to-postgres#how-connection-pooling-works

[rayli09]

same on this

[silentworks]

What does same on this mean in your case? Please be more descriptive when leaving a comment.

[AurelianSpodarec]

Use google translate if needed

[Jordaneisenburger]

Having the same issue it was working fine all of the sudden it stops working.. I'm pretty sure it has a correlation to the Prisma client as my login form still works

Invalid `prisma.users.findMany()` invocation:


Can't reach database server at `db.crpvifgwvaqdzzoldkak.supabase.co`:`5432`

Please make sure your database server is running at `db.crpvifgwvaqdzzoldkak.supabase.co`:`5432`.

[Jordaneisenburger]

I just created a new Supabase project and it works again, no code changes at al besides switching the DB url's in .env

[darcy-vitacca]

What fixed it for me was that a free tier project had gone into inactive mode and I just had to restart it, not sure if this will help anyone.

[pablosr11]

Suddenly got this too. No changes to DB credentials. Restarted yesterday and it was still working fine.
One day later Can't reach database server at db.XXXXXXX.supabase.co:5432`` and connection timeout expired

Have tried connecting through pgadmin, prisma, and psql

[samjusaitis]

@p2pskins refer to this article: https://supabase.com/partners/integrations/prisma

[ajagatobby]

This solution solved it ASAP

[Oribi5]

This solved it for me instantly

[RsRsRahul]

This worked for me

[servehub-llc]

me too!

[jmilus]

Having this same issue with my dev environment (localhost). Curiously, my live site, hosted on Vercel and which uses the same database, works just fine.
Problem appeared overnight. Worked fine last night before bed, and now refuses to function with morning coffee. Restarted everything, updated everything...

[jmilus]

I should clarify: both my dev (local) build and my live build point to the exact same SupaBase project, so it wouldn't seem to be an issue with the project being inactive, as it works for one but not the other.

[nimeshmaharjan1]

I forgot what I did because has been a long time but I think it was just enabling the project because supabase disables it?

…

On Sat, 17 Jun 2023, 8:51 pm jmilus, ***@***.***> wrote: Having this same issue with my dev environment (localhost). Curiously, my live site, hosted on Vercel and which uses the same database, works just fine. Problem appeared overnight. Worked fine last night before bed, and now refuses to function with morning coffee. Restarted everything, updated everything... — Reply to this email directly, view it on GitHub <#4161 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUXM4BT5BQFE5NAYHYQTIZ3XLXBV3ANCNFSM5JA2I56Q> . You are receiving this because you commented.Message ID: ***@***.***>

[nimeshmaharjan1]

https://github.com/orgs/supabase/discussions/4161#discussioncomment-2262224 what about this?

[nimeshmaharjan1]

I remember having a ! In my password in my env file and I changed the password and it worked

[jmilus]

I never changed my password from the original that Supabase generated. I just re-generated a new one (using Suapbase's generator) and I'm still getting the same result.

[jmilus]

It appears I have solved it. I discovered that the connection string in my database settings (under Connection Pooling) was using a different port from the one in my env file. No idea why that would have changed, as it wasn't anything I would have initiated.

[devknight216]

The issues are not related to password at all I think.

[nimeshmaharjan1]

Haven't encountered this issue after the first time On Sat, 17 Jun 2023, 9:26 pm Nimesh Maharjan, ***@***.***> wrote:

…

I forgot what I did because has been a long time but I think it was just enabling the project because supabase disables it? On Sat, 17 Jun 2023, 8:51 pm jmilus, ***@***.***> wrote: > Having this same issue with my dev environment (localhost). Curiously, my > live site, hosted on Vercel and which uses the same database, works just > fine. > Problem appeared overnight. Worked fine last night before bed, and now > refuses to function with morning coffee. Restarted everything, updated > everything... > > — > Reply to this email directly, view it on GitHub > <#4161 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AUXM4BT5BQFE5NAYHYQTIZ3XLXBV3ANCNFSM5JA2I56Q> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

[tylerbecks]

https://stackoverflow.com/questions/73866587/prisma-error-p1001-cant-reach-database-server-at-db-xocheossqzkirwnhzxxm-sup

This solved it for me. For context, my connection was slow and it was throwing this error intermittently.

[KuhlTime]

This is what Supabase Support told me: This might happen due to the connection being temporarily blocked by Supabase, see
https://supabase.com/docs/guides/platform/troubleshooting#connection-refused

---

For the time my connection was blocked, I was able to use a VPN (Germany → USA → Supabase) to connect to the instance. After some while, I could then connect normally again.

[wvovaw]

I found that I cannot connect my development environment to supabase while connected via VPN. Apparently supabase has blacklisted the IP server where my VPN is hosted.

[MarionbDev]

Here's the error I found???
In my .env file I have this :
DATABASE_URL="postgresql://postgres:[my_password]@db.sxcvldvzpvnaynwnugko.supabase.co:5432/postgres"
My password is in alphabets.
and in my PRISMA file :
generator client {
provider = "prisma-client-js"
}

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

I have, I think, tried everything!!!!

[kagawa0710]

I had the same error and was able to solve it.
In my case, the password contained symbols, so I encoded it as a url and it worked.

[stevejpurves]

great solution, this works fine!

[OdapX]

this worked for me, isn't this a bug from supabase side ?

[Ciscodefran]

Run 'prisma migrate dev' and check if previewFeatures = ["multiSchema"] property needed in your schema.prisma file.

[angelxtrme]

Create new password. Use only Letters either in capital or not. This solved this problem.

[MooJhingjit]

Thanks, This solved this issue for me

[adityayaduvanshi]

Get the Database URI from database settings. it will look like this
"postgres://postgres.[USER]:[YOUR-PASSWORD]@aws-0-ap-southeast-1.pooler.supabase.com:5432/postgres"

You have to add "connect_timeout=300" in the end of the URI.

This will fix it

[pwilczewski]

I suddenly experienced this error this morning - everything had been working last night. For some reason the database connection string in supabase had changed from:

postgresql://postgres:[MY-PASSWORD]@db.[MY-DATABASE].supabase.co:5432/postgres

To:

postgres://postgres.[MY-DATABASE]:[MY-PASSWORD]@aws-0-us-east-1.pooler.supabase.com:5432/postgres

To my knowledge I hadn't changed any settings in supabase. But updating to the new connection string resolved the error for me.

[adityayaduvanshi]

Yeah its because Supabase is migrating to IPV6.

Use this link and it will fix the error
postgres://postgres.[MY-DATABASE]:[MY-PASSWORD]@aws-0-us-east-1.pooler.supabase.com:5432/postgres?connect_timeout=300

[AdventureBear]

this fixed it for me. thanks

[leofmoura]

Thanks, spent 2hours trying to fix this. GOLD.

[tinegaCollins]

GOLD

[AdventureBear]

Ha;ving the same issues. It was working fine last night and this AM getting the same types of errors.
Ido have symbols in my PW, so I guess I'll try updating the PW. I restarted the DB server. Seems weird that it happens all of a sudden.

Changed my password and no luck still.

[AdventureBear]

fixed it by updating my connection string as show in this thread.
it would be great if this could be alerted on the dashboard. I did see the migration alert but mine had been migrated and I didn't realize it except that it stopped working.

Just a friendly suggestion for a UI improvement. This cost me about an hour of troubleshooting today (when I should have been working at my real J-O-B, lol).

[Hiperultimate]

For people who are recently having this issue I have a fix for it.

This is the message I found on Supabase dashboard > Project Settings > Database > URI
"Direct database access via IPv4 and pgBouncer will be removed from January 26th 2024
We strongly recommend using connection pooling to connect to your database. You'll only need to change the connection string that you're using in your application to the pooler's connection string."

Supabase have updated something behind the scenes and because of it the connection string is now a bit different. Just use the new one and you will be fine after you add the db password in it.

[johannesludloff]

For me the default setting under "Connection pooling configuration" for my db was "Transaction mode", however for all Postgres features to work you need "Session". At least for me it fixed the issue. Also had to change connection string though.

[Eronred]

After updating the database URL, the issue was fixed. However, receiving an alert whenever the database URL is updated would be helpful

[frankdavidcorona]

Hi, I've configured my project using NextJS and Prisma as ORM and my connection strings look like this:

# Connect to Supabase via connection pooling with Supavisor.
DATABASE_URL="postgres://postgres.vghrgcxiebaxjgjmhrum:[PASSWORD]@aws-0-us-east-1.pooler.supabase.com:5432/postgres?connect_timeout=300"

# Direct connection to the database. Used for migrations.
DIRECT_URL="postgresql://postgres:[PASSWORD]@db.vghrgcxiebaxjgjmhrum.supabase.co:5432/postgres?connect_timeout=300"

Then I tried to run this command to upload my current schemas from Prisma ORM but I still had this connection string error:

npx prisma migrate dev --name init
Environment variables loaded from .env
Prisma schema loaded from src/prisma/schema.prisma
Datasource "db": PostgreSQL database "postgres", schema "public" at "db.vghrgcxiebaxjgjmhrum.supabase.co:5432"

Error: P1001: Can't reach database server at `db.vghrgcxiebaxjgjmhrum.supabase.co`:`5432`

Please make sure your database server is running at `db.vghrgcxiebaxjgjmhrum.supabase.co`:`5432`.

[henningsieh]

Same here... since 2 or 3 weeks I think and in incomprehensible and irregular intervals.

 ⨯ Error [PrismaClientInitializationError]:
Invalid `prisma.report.findMany()` invocation:

Can't reach database server at `aws-0-eu-central-1.pooler.supabase.com`:`5432`

Please make sure your database server is running at `aws-0-eu-central-1.pooler.supabase.com`:`5432`.

[CloudInnovator]

Same here... since 2 or 3 weeks I think and in incomprehensible and irregular intervals.

 ⨯ Error [PrismaClientInitializationError]:

Invalid `prisma.report.findMany()` invocation:



Can't reach database server at `aws-0-eu-central-1.pooler.supabase.com`:`5432`



Please make sure your database server is running at `aws-0-eu-central-1.pooler.supabase.com`:`5432`.

This could be due to a host of reasons associated with connectivity. If you have poor internet connectivity then this error pops up. This is the hardest to debug of all the reasons. I have been blessed with poor internet, that's how I know 😬 Unfortunately, this has more to do with latency associated with all cloud services not supabase. My answer assumes that you have a running instance and followed proper guidance on
connections, password and pooling.

[leomerida15]

Hi there,

I’m building a prototype NextJs app using Prisma ORM and Supabase PostgresSQL database.

However, I’m receiving the following error:

Server Error
Error: 
Invalid `prisma.course.create()` invocation:


  Can't reach database server at `db.wzlsuclrgwfuyuedoehj.supabase.co`:`5432`

Please make sure your database server is running at `db.wzlsuclrgwfuyuedoehj.supabase.co`:`5432`.

Details:

M1 MacOS Monteray 12.0.1

Next.js v12.0.4

prisma : 3.5.0

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

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

DATABASE_URL="postgresql://postgres:[password]@db.wzlsuclrgwfuyuedoehj.supabase.co:5432/postgres”

Any assistence would be greatly appreciated.

I managed to solve the error by running the migration script with bunjs, I tested it with several networks using bunjs and it worked on all of them regardless of the internet speed.

bun prisma migrate dev

[sashaskull]

Somehow Supabase had banned my IP and it was appearing under Network Bans. After removing the said IP it started working straight away.

[AbdullahAlhariri]

Quote from supabase:

Direct database connections will start resolving to an IPv6 address. Starting from January 26, 2024, projects will be gradually migrated to this behavior. If you connect to your database using the REST or GraphQL endpoints, this doesn't affect you. If you use the database connection string, see the GitHub discussion on how to prepare for IPv6.

I had to follow how to prepare for IPv6, I only needed to change my connection string. and everything works smoothly now

[alexshenker]

When runing npm run build in my NextJS (14.2.3) project, random statically generated pages randomly throw this error, its never the same pages that fail to build:

PrismaClientKnownRequestError: 
Invalid `prisma.composer.findFirst()` invocation:

Can't reach database server at `aws-0-us-east-1.pooler.supabase.com`:`5432`

Please make sure your database server is running at `aws-0-us-east-1.pooler.supabase.com`:`5432`.

I'm using the new connection string DATABASE_URL=postgres://postgres.[DB ID]:[Password]@aws-0-us-east-1.pooler.supabase.com:5432/postgres.

I've attempted nearly all of the solutions offered in this thread. None of them worked. The only thing that enabled a successful build, is appending ?connection_limit=1 to the end of my DB string. anything above '1' leads to the same intermittent errors for random pages.

This is not ideal, so any ideas are appreciated.

[e-Naeim]

thanks! I've been strugling with it the whole day. I hope someone can explain and provide a solution

[Sameerthe-Big-O]

For me guys it was just a type carefully copy and paste the connection string