Neon•9mo ago

Can't reach database server

Getting this a few times a day

PrismaClientKnownRequestError: Invalid

prisma.user.findUnique()

prisma.user.findUnique()

prisma.user.findUnique()

prisma.user.findUnique() invocation:

Can't reach database server at

ep-tight-voice-SERVERID-pooler.us-east-1.aws.neon.tech:5432

ep-tight-voice-SERVERID-pooler.us-east-1.aws.neon.tech:5432

ep-tight-voice-SERVERID-pooler.us-east-1.aws.neon.tech:5432

ep-tight-voice-SERVERID-pooler.us-east-1.aws.neon.tech:5432

Please make sure your database server is running at

ep-tight-voice-SERVERID-pooler.us-east-1.aws.neon.tech:5432

ep-tight-voice-SERVERID-pooler.us-east-1.aws.neon.tech:5432

ep-tight-voice-SERVERID-pooler.us-east-1.aws.neon.tech:5432

ep-tight-voice-SERVERID-pooler.us-east-1.aws.neon.tech:5432.

I have auto-scaling enabled, so what am I missing here? Codebase is Next.js + Prisma. I suspect there are places with

Promise.all

Promise.all

Promise.all

Promise.all that are cloggling the connection pool, but other than that what can I do to troubleshoot this better? TIA

scattered-teal•4/23/25, 7:06 PM

yes i am also getting this

scattered-teal•4/23/25, 7:07 PM

how can we solve this

instant-harlequin•4/23/25, 7:28 PM

I suggest looking at the connection / connection pool timeout docs here: https://neon.tech/docs/guides/prisma#connection-timeouts

Neon

Connect from Prisma to Neon - Neon Docs

Prisma is an open source, next generation ORM that lets you to manage and interact with your database. This guide covers the following topics Connect to Neon from Prisma Use connection pooling with Pr...

dead-brown•4/24/25, 4:14 PM

same thing happening to me

specific-silver•4/24/25, 4:56 PM

yeah oddly enough this has been happening for us more in the last 2-3 weeks whereas it wasn't a problem before.

instant-harlequin•4/24/25, 6:50 PM

hm. That timing aligns with the Prisma ORM 6.6.0 release. https://www.prisma.io/blog/prisma-orm-6-6-0-esm-support-d1-migrations-and-prisma-mcp-server

This info from the Prisma team is related to another Neon-Prisma issue, but perhaps it applies — and maybe worth a try.

"We did some changes to driver adapters in the 6.6.0 release though.
Some users do not properly install prisma as a dev dependency but use e.g. npx prisma generate . This can lead to the generated code using the latest 6.6.0 interfaces, but the installed client is still older (e.g. 6.5.0). Most often this causes no obvious issues as we rarely changed the interfaces. But with 6.6.0 we did.

So maybe let the user try to properly update prisma client and cli to 6.6.0. "

Iinstant-harlequin hm. That timing aligns with the Prisma ORM 6.6.0 release. https://www.prisma.io/...

brilliant-limeOP•4/28/25, 10:07 PM

We are using prisma 6.2.1 here, both client and cli.

Currently getting this:

Invalid

prisma.user.findUnique()

prisma.user.findUnique()

invocation:

Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 15, connection limit: 20)

DATABASE_URL=postgres://USER:PASS@SERVER-pooler.us-east-1.aws.neon.tech:5432/DBNAME?sslmode=require&connect_timeout=15&connection_limit=20&pool_timeout=15

DATABASE_URL=postgres://USER:PASS@SERVER-pooler.us-east-1.aws.neon.tech:5432/DBNAME?sslmode=require&connect_timeout=15&connection_limit=20&pool_timeout=15

DIRECT_URL=postgres://USER:PASS@SERVER.us-east-1.aws.neon.tech:5432/DBNAME?sslmode=requireDIRECT_URL=postgres://USER:PASS@SERVER.us-east-1.aws.neon.tech:5432/DBNAME?sslmode=require

Connection pool | Prisma Documentation

Prisma ORM's query engine creates a connection pool to store and manage database connections.

brilliant-limeOP•5/1/25, 7:57 PM

Updated to 6.6.0, still happening

wispy-olive•5/8/25, 3:58 PM

@leofc

Can you share if the problem persists if you use https://github.com/neondatabase/examples/tree/main/with-nextjs-prisma-edge with your Neon database?

brilliant-limeOP•5/8/25, 4:50 PM

@Rishi Raj Jain you mean using this prisma client? https://github.com/neondatabase/examples/blob/main/with-nextjs-prisma-edge/lib/prisma.server.ts

wispy-olive•5/8/25, 4:51 PM

Exactly!

brilliant-limeOP•5/8/25, 6:23 PM

Awesome, we moved our plan, not sure if this relates, but monitoring it. Thanks

elderly-tomato•5/15/25, 6:42 AM

@leofc I am facing same issue, did you fixed it ?

instant-harlequin•5/15/25, 8:23 AM

Hi @leofc what issue are you seeing?

brilliant-limeOP•5/15/25, 8:21 PM

@Daniel

Ex: Invalid prisma.salesOrderItem.update()prisma.salesOrderItem.update() invocation:

Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 15, connection limit: 20)

Connection pool | Prisma Documentation

Prisma ORM's query engine creates a connection pool to store and manage database connections.

brilliant-limeOP•5/15/25, 8:59 PM

@Levan Parastashvili it didn't happen for a while, I only upgrade my plan (was a legacy Vercel client) but it happened yesterday again

instant-harlequin•5/15/25, 10:27 PM

It looks like you have increased your pool timeout and connection limit. Have you looked at the size of the machine where your application runs? As I understand it, that determines the number of connections available in the Prisma connection pool. https://neon.tech/docs/guides/prisma#connection-pool-timeouts

Failing that, I'd open a ticket with Neon support to investigate further: https://console.neon.tech/app/projects?modal=support

brilliant-limeOP•5/16/25, 5:31 PM

@Daniel application is running in Vercel (Pro Plan) and not sure if I can find the number of physical CPUs. I assume you have hundreds of Vercel customers, so which number do you see here

instant-harlequin•5/16/25, 7:08 PM

Unfortunately, we don't have a window into Vercel compute sizes where your app runs — we can only see the Neon database computes.

brilliant-limeOP•5/20/25, 3:36 PM

@Daniel messaged the support but no answer. Last time I messaged that (for a sales call) it took one week to get a response

brilliant-limeOP•5/20/25, 3:36 PM

Not impressed with Neon at this point

instant-harlequin•5/20/25, 4:24 PM

Hi @leofc My apologies. Can you provide me with your support ticket number (four digit number) ? I'll ping the team directly.

brilliant-limeOP•5/20/25, 9:25 PM

#6538 - thank you

instant-harlequin•5/21/25, 10:08 AM

Hi @leofc I see the new issue in our support system. For paid plans, support is within 3 business days.
https://neon.tech/docs/introduction/support
In the meantime, it looks like you're on Vercel Pro, so I'd reach out there to see if you can determine the machine/vm size where your app runs, as that impacts your Prisma connection pool size.
I'd also reach out the Prisma team to see if they have anything to offer.
@Rishi Raj Jain is there anything else here you can recommend?

brilliant-limeOP•5/21/25, 5:21 PM

Thanks @Daniel - I posted in their support forum a few days ago: https://community.vercel.com/t/vercel-prisma-neon-and-connection-issues/10813

Vercel Community

Vercel, Prisma, Neon and connection issues

Running my application in Vercel (Pro Plan) and seeing these errors sometimes: Invalid prisma.customer.findMany()prisma.customer.findMany() invocation: Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 15, connection limit: 20) and Invalid prisma.salesOrder.findFirst()prisma.salesOrder.findFirst() invo...

Can't reach database server

Similar Threads

Similar Threads

Similar Threads