N
Neon17mo ago
exotic-emerald

Error: P1001: Can't reach database server at `ep-twilight-river-<Pwd>-pooler.us-east-2.aws.neon.t

Hello I am facing this issue in production. I have already done prisma generate and prisma migrate dev in development server. It is working fine in development server. However, it gives me this error on production server. I am using the following stack with versions: digital ocean droplet as my server, NextJS v14.2.4, prisma v^5.15.1, prisma/adapter-neon v^5.15.1 prisma/client v^5.15.1", My database url is : postgresql://researchmonkey_owner:<Password>@ep-twilight-river-a5yd76tk-pooler.us-east-2.aws.neon.tech/podcastmonkey?sslmode=require
4 Replies
optimistic-gold
optimistic-gold17mo ago
See if this solves your issue https://community.neon.tech/t/error-p1001-while-migrating-with-prisma/808
The error you got most likely means that the Prisma query engine timed out before the Neon compute was activated. You can adjust your Neon connection string by adding a connect_timeout parameter that defines the maximum number of seconds to wait for a new connection to be opened. The default value is 5 seconds. A higher setting should provide the time required to avoid connection timeout issues.
postgresql://researchmonkey_owner:<Password>@ep-twilight-river-a5yd76tk-pooler.us-east-2.aws.neon.tech/podcastmonkey?sslmode=require&connect_timeout=10
postgresql://researchmonkey_owner:<Password>@ep-twilight-river-a5yd76tk-pooler.us-east-2.aws.neon.tech/podcastmonkey?sslmode=require&connect_timeout=10
Neon
Error P1001 while migrating with Prisma
I get the following error message after running "npx prisma migrate dev* Error: P1001 Can't reach database server at "ep-black-silence...": "5432" I copied the links as given in Neon like here: I copied the links in my file .env DATABASE_URL=postgres://mrexito.rg:XXX@ep-lively-breeze-417358.eu-central-1.aws.neon.tech/MainDB SHADOW_DATAB...
exotic-emerald
exotic-emeraldOP17mo ago
I have made the changes but I'm still getting the same error.
solid-orange
solid-orange17mo ago
However, it gives me this error on production server.
Hey @Hussain, Can you share more about the error you're facing?
quickest-silver
quickest-silver6mo ago
facing same issue, did you guys fixed it ?

Did you find this page helpful?