Abhinav
Abhinav
PostsComments
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
but still very unsatisfactory performance. The retrieval from database is taking forever and getting errors almost every 3rd time
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
By adding binaryTargets = ["native"] like this in the schema file 
generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native"]
}
generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native"]
}
I was able to solve this problem
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
Yes, basically supabase has some weird problem where it just doesn't connect. DBeaver showed connection timeout. I tried everything like making another project (with different hosting place) but it finally worked when I turned on VPN and then tried 2-3 times. Now it works for local deployment but still shows some error in vercel deployment. 
Unhandled Rejection: PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-1.0.x".
We detected that you are using Next.js, learn how to fix this: https://pris.ly/d/engine-not-found-nextjs.
This is likely caused by a bundler that has not copied "libquery_engine-rhel-openssl-1.0.x.so.node" next to the resulting bundle.
Ensure that "libquery_engine-rhel-openssl-1.0.x.so.node" has been copied next to the bundle or in "node_modules/.pnpm/@[email protected][email protected]/node_modules/.prisma/client".
We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation
The following locations have been searched:
/var/task/node_modules/.pnpm/@[email protected][email protected]/node_modules/.prisma/client
/var/task/.next/server
/vercel/path0/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client
/var/task/.prisma/client
/tmp/prisma-engines
at wa (/var/task/.next/server/chunks/452.js:64:841)
at async Object.loadLibrary (/var/task/.next/server/chunks/452.js:111:10446)
at async wt.loadEngine (/var/task/.next/server/chunks/452.js:112:452)
at async wt.instantiateLibrary (/var/task/.next/server/chunks/452.js:111:13267) {
clientVersion: '5.15.0',
errorCode: undefined
}
Node.js process exited with exit status: 128. The logs above can help with debugging the issue.
Unhandled Rejection: PrismaClientInitializationError: Prisma Client could not locate the Query Engine for runtime "rhel-openssl-1.0.x".
We detected that you are using Next.js, learn how to fix this: https://pris.ly/d/engine-not-found-nextjs.
This is likely caused by a bundler that has not copied "libquery_engine-rhel-openssl-1.0.x.so.node" next to the resulting bundle.
Ensure that "libquery_engine-rhel-openssl-1.0.x.so.node" has been copied next to the bundle or in "node_modules/.pnpm/@[email protected][email protected]/node_modules/.prisma/client".
We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation
The following locations have been searched:
/var/task/node_modules/.pnpm/@[email protected][email protected]/node_modules/.prisma/client
/var/task/.next/server
/vercel/path0/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client
/var/task/.prisma/client
/tmp/prisma-engines
at wa (/var/task/.next/server/chunks/452.js:64:841)
at async Object.loadLibrary (/var/task/.next/server/chunks/452.js:111:10446)
at async wt.loadEngine (/var/task/.next/server/chunks/452.js:112:452)
at async wt.instantiateLibrary (/var/task/.next/server/chunks/452.js:111:13267) {
clientVersion: '5.15.0',
errorCode: undefined
}
Node.js process exited with exit status: 128. The logs above can help with debugging the issue.
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
Thanks a lot for your time, big help!
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
even with VPN it didn't work first time
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
it's so weird
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
USED VPN and worked
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
FINALLY WORKED
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
tried everything
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
No description
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
cool I will try changing DNS and other stuff. Will let you know. Thanks a lot! Big big help.
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
it doesn't go after this
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
No description
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
do you think it's a network issue?
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
let me try tableplus
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
nopes doesn't work : (
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
will something like tableplus work?
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
No description
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
seems like the database is not working? how can I test it?
56 replies
PPrisma
Created by Abhinav on 6/7/2024 in #help-and-questions
Can't reach database server at `aws-0-ap-south-1.pooler.supabase.com:5432`
yes the issue still persists.
56 replies