Can't reach database server at `db.prisma.io:5432`
Error [PrismaClientInitializationError]:
Invalid
prisma.****.findMany() invocation:
Can't reach database server at db.prisma.io:5432
Please make sure your database server is running at db.prisma.io:5432.30 Replies
You decided to hold for human wisdom. We'll chime in soon! Meanwhile,
#ask-ai is there if you need a quick second opinion.maybe your issue is related to this?
https://github.com/prisma/prisma/discussions/14187
GitHub
Can't reach database server at
postgres:5432 · prisma prisma ...Bug description I have a docker container running with postgres but prisma cant find the database server when i run npx prisma migrate dev In my docker GUI it says that I have a running container w...
make sure the connection url is correct
it is linked by vercel please take a look hichemchouaibi2@gmail.com
@🔨 Moderator
@Nurul
revalidating cache with key: ()=>a(...f)-items-[] Error [PrismaClientInitializationError]:
Invalid
prisma.*****.findMany() invocation:
Timed out fetching a new connection from the connection pool. More info: http://pris.ly/d/connection-pool (Current connection pool timeout: 10, connection limit: 5)
at async (../../dist/apps/egashop/.next/server/chunks/4898.js:1:16275) {
clientVersion: '6.17.1',
errorCode: undefined,
retryable: undefined
}Connection pool | Prisma Documentation
Prisma ORM's query engine creates a connection pool to store and manage database connections.
got the same thing here: (vercel integrated) may be related to this global incident: ?
I'm not sure it's vercel? I can't access prisma accelerate on my localhost. Or does prisma accelerate depend on vercel?
It seems to be a pretty widespread issue
https://discord.com/channels/937751382725886062/937751383124361286/1429749095479775334
thank you!
same here, I started receiving this error about 2 hours ago, from the PRD environment: invocation:\n\n\nThis request could not be understood by the server: {"type":"UnknownJsonError","body":{"code":"P6008","message":"Accelerate was not able to connect to your database. The underlying error is: error requesting Query Engine from pool"}}
Same here, started getting the error about anchour ago
Accelerate was not able to connect to your database. The underlying error is: error requesting Query Engine from poolsame wth is going on!
it's probably all trickle-down from the AWS outage
maybe we should just all go back to buying servers again
Does this happens a lot?!
Would be the second time accelerate has gone down for me in the last 3 months
same issue here
This happened to us after AWS outage, Acceelrate refuses to connect to DB.
Studio doesn't work, but status page shows everything is fine!
get a life dude, stop scamming
seems a big deal, even MercadoLibre is facing issues
This is why good old bare metal is better, now we stuck...!!
I'm seeing this issue too, prisma via vercel.
Brutal, AWS in north virgina has been cooked for 10 hours.
https://health.aws.amazon.com/health/status
:heart:
