P
Prisma2mo ago
neutron

Server has closed the connection.

Error: P1017: Server has closed the connection.  ELIFECYCLE  Command failed with exit code 1. Error: Command "pnpm i; pnpm run prisma:generate; pnpm run migrate:deploy" exited with 1
12 Replies
Prisma AI Help
Prisma AI Help2mo ago
You decided to hold for human wisdom. We'll chime in soon! Meanwhile, #ask-ai is there if you need a quick second opinion.
Nurul
Nurul2mo ago
@neutron Can you please share the email id with which you signed up?
neutron
neutronOP2mo ago
hichemchouaibi2@gmail.com @Nurul (Prisma) i have also Invalid%20%60prisma.ad.upsert()%60%20invocation%3A%0A%0A%0AServer%20has%20closed%20the%20connection
Error [PrismaClientInitializationError]:
Invalid `prisma.st.findUnique()` invocation:


Server has closed the connection.
....

Error [PrismaClientInitializationError]:
Invalid `prisma.st.findUnique()` invocation:


Server has closed the connection.
....
Error [PrismaClientInitializationError]:
Invalid `prisma.st.findUnique()` invocation:


Server has closed the connection.
....
⨯ Error [PrismaClientInitializationError]:
Invalid `prisma.st.findUnique()` invocation:


Server has closed the connection.
...
}
Error [PrismaClientInitializationError]:
Invalid `prisma.st.findUnique()` invocation:


Server has closed the connection.
....

Error [PrismaClientInitializationError]:
Invalid `prisma.st.findUnique()` invocation:


Server has closed the connection.
....
Error [PrismaClientInitializationError]:
Invalid `prisma.st.findUnique()` invocation:


Server has closed the connection.
....
⨯ Error [PrismaClientInitializationError]:
Invalid `prisma.st.findUnique()` invocation:


Server has closed the connection.
...
}
Nurul
Nurul2mo ago
We are checking
neutron
neutronOP2mo ago
@Nurul (Prisma) did you find it ?
Nurul
Nurul2mo ago
Yes, we are working on fixing this. I'll post an update shortly
neutron
neutronOP2mo ago
please don't forgert revalidating cache with key: ()=>e(...n)-items-[] Error [PrismaClientKnownRequestError]: Invalid prisma.it.findMany() invocation: Timed out fetching a new connection from the connection pool. i think is the same issue
Nurul
Nurul2mo ago
Please check now?
neutron
neutronOP2mo ago
wait it works what is the problem please?
Nurul
Nurul2mo ago
We had an issue in US east region, we are doing a postmortem to identify the cause of the issue and will share it
neutron
neutronOP2mo ago
@Nurul (Prisma) same Invalid prisma.item.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. at async (../../dist/apps/egashop/.next/server/chunks/8298.js:1:4914) { code: 'P1001', meta: [Object], clientVersion: '6.17.0' }
Nurul
Nurul2mo ago
This should be resolved by now. Do you still get the same error ?

Did you find this page helpful?