Can't reach database server at `ep-icy-dust-a4s6p4wh.us-east-1.aws.neon.tech:5432
getting this error when using prisma genereate client command
21 Replies
correct-apricot•15mo ago
Hey! Sorry to hear that you're running into an issue.
A few questions:
1. Have you tried connecting using psql?
2. Are you able to run queries from the Neon console?
3. Are you running into this issue consistently?
passive-yellow•15mo ago
I'm facing same problem I have also used psql ans its giving error
psql: error: could not translate host name "ep-icy-poetry-a592kua9-pooler.us-east-2.aws.neon.tech" to address: Name or service not knowncorrect-apricot•15mo ago
Are you consistently running into this error?
passive-yellow•15mo ago
Yes
What should I do?
correct-apricot•15mo ago
hmm, are you using the example that's in the code snippets widget from the console?
Also, are you able to run queries in the console?
passive-yellow•15mo ago
where is the code snippets you are saying?
passive-yellow•15mo ago
is this?
passive-yellow•15mo ago
I have tried to run but its giving unknown error
correct-apricot•15mo ago
This is definitely odd. Do you mind trying again and giving us a timestamp? this way we can check logs on our end
passive-yellow•15mo ago
I have tried gain at IST 16:32
correct-apricot•15mo ago
Our support team will look into it. I'll let you know once I hear back from them. Sorry that you're running into an issue
passive-yellow•15mo ago
Thank you for the update! I'll wait to hear back from you and hope for a resolution soon.
I have tried to create new project and still same errors at
Aug 29, 2024 1:02:21.986 AM
GMT +05:30
correct-apricot•15mo ago
Do you mind sending an email to support@neon.tech? I notified them of your use case
passive-yellow•15mo ago
Sure
foreign-sapphire•15mo ago
facing the same issue
it has reach to the point that i today am looking to switch to supabase or something .... was previously working with Prisma ORM switched to NEON by a friends recommendation and just today my application wont load any changed giving me constant error..
Unhandled Runtime Error
Error:
Invalid
prisma.category.findMany() invocation:
Can't reach database server at ep-tight-sun-a5gljajj-pooler.us-east-2.aws.neon.tech:5432
Please make sure your database server is running at ep-tight-sun-a5gljajj-pooler.us-east-2.aws.neon.tech:5432.correct-apricot•15mo ago
Hey! Sorry to hear that you're running into this issue. Which Prisma version are you using and which deployment provider are you using?
foreign-sapphire•15mo ago
Prisma latest and deployment vercel
clever-tan•15mo ago
@Ali Sufiyan I send you an email via the support case that you raised 🙂
foreign-sapphire•15mo ago
sent you back an email with all the screenshots and errors i am getting because of poor neon db performance...
sensitive-blue•15mo ago
Hi, I am running into same error when trying to initialize connection, using Prisma ORM, but a few days later it worked correctly and my backend could properly send and recieve api calls to and from neon,: PrismaClientInitializationError: Can't reach database server at
ep-raspy-resonance-a2x5dsag-pooler.eu-central-1.aws.neon.tech:5432 Please make sure your database server is running at ep-raspy-resonance-a2x5dsag-pooler.eu-central-1.aws.neon.tech:5432 Prisma clientVersion: '5.18.0', errorCode: 'P1001'foreign-sapphire•15mo ago
so my issues has been solved by Yanic and its beasically something on our end, what i did was, went to wifi settings or wired which ever you are using and change the DNS to DHCP only or manual and put the DNS for ipv4 as 8.8.8.8 then save and if you are using ipv6 you can use 2001:4860:4860::8888 and then save and you should be good to go...
thank you soo much