P
Prisma•2mo ago
Mitolius

Random accelerate network error

hello, i'm migrating a big project to prisma, at the moment i migrate my dev environment to make all the tests. I'm using Prisma Postgres on starter plan with a NextJS app and an expressjs external api, both connect using prisma accelerate. Sometime I got this error: 
Cannot fetch data from service:
Unable to connect to the Accelerate API. This may be due to a network or DNS issue. Please check your connection and the Accelerate connection string. For details, visit https://www.prisma.io/docs/accelerate/troubleshoot.
Cannot fetch data from service:
Unable to connect to the Accelerate API. This may be due to a network or DNS issue. Please check your connection and the Accelerate connection string. For details, visit https://www.prisma.io/docs/accelerate/troubleshoot.
Can I do something about it ? could upgrading plan solve the problem ? Is it a known problem as Prisma Postgres is in beta (for production i will take a aws postgres db) Thanks
9 Replies
Prisma AI Help
Prisma AI Help•2mo ago
You selected to wait for the human sages. They'll share their wisdom soon. Grab some tea while you wait, or check out #ask-ai if you'd like a quick chat with the bot anyway!
Nurul
Nurul•2mo ago
Hello @Mitolius 👋 Can you please share with me your GitHub Handle or the email with which you signed up? I would like to take a look at the logs to check this
Mitolius
MitoliusOP•2mo ago
Nurul
Nurul•2mo ago
Thanks! I assume this is happening in Development environment of SMTT-PRO project, right? Do you have a timestamp on when this error occured? Did you get any request id in the logs?
Mitolius
MitoliusOP•2mo ago
Ok, I found the logs, I have multiple error message, i suspect it all come from the same inital error: You search on your side starting at 2025-01-19 00:15 (UTC), I don't have any more information as it's random and happen rarely. The exact same code is running for 3 days without errors 
2025-01-19T00:15:41.037Z [ERROR]: SYNC [CUSTOMER]: Error  PrismaClientKnownRequestError: 
Invalid `prisma.syncConfigs.findUnique()` invocation:


Cannot fetch data from service:
Unable to connect to the Accelerate API. This may be due to a network or DNS issue. Please check your connection and the Accelerate connection string. For details, visit https://www.prisma.io/docs/accelerate/troubleshoot.
    at Yr.handleRequestError (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:20:7527)
    at Yr.handleAndLogRequestError (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:20:6851)
    at Yr.request (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:20:6564)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async l (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:29:9535)
2025-01-19T00:15:41.037Z [ERROR]: SYNC [CUSTOMER]: Error  PrismaClientKnownRequestError: 
Invalid `prisma.syncConfigs.findUnique()` invocation:


Cannot fetch data from service:
Unable to connect to the Accelerate API. This may be due to a network or DNS issue. Please check your connection and the Accelerate connection string. For details, visit https://www.prisma.io/docs/accelerate/troubleshoot.
    at Yr.handleRequestError (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:20:7527)
    at Yr.handleAndLogRequestError (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:20:6851)
    at Yr.request (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:20:6564)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async l (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:29:9535)
Invalid `prisma.syncConfigs.findUnique()` invocation:


This 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: Health Check of Query Engine timed out."}} (The request id was: 9042a80e3e3ed6da)
    at Yr.handleRequestError (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:20:7527)
    at Yr.handleAndLogRequestError (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:20:6851)
    at Yr.request (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:20:6564)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async l (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:29:9535)
Invalid `prisma.syncConfigs.findUnique()` invocation:


This 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: Health Check of Query Engine timed out."}} (The request id was: 9042a80e3e3ed6da)
    at Yr.handleRequestError (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:20:7527)
    at Yr.handleAndLogRequestError (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:20:6851)
    at Yr.request (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:20:6564)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async l (/usr/src/app/node_modules/.prisma/client/runtime/edge.js:29:9535)
Nurul
Nurul•2mo ago
Thank you for sharing the request id! I am taking a look I think this was an intermittent DNS allocation error from our underlying cloud provider Cloudflare. This happened while trying to allocate a new Query Engine for your environment. Please let me know in case you run into this issue again. I'll escalate it
Mitolius
MitoliusOP•2mo ago
Error: 
Invalid `prisma.usersProfiles.findFirst()` invocation:


Can't reach database server at `01jg46vq3dpsmq7r9wv0peq7h6.cdg1.db.prisma-data.net:5432`

Please make sure your database server is running at `01jg46vq3dpsmq7r9wv0peq7h6.cdg1.db.prisma-data.net:5432`.
 
Error: 
Invalid `prisma.usersProfiles.findFirst()` invocation:


Can't reach database server at `01jg46vq3dpsmq7r9wv0peq7h6.cdg1.db.prisma-data.net:5432`

Please make sure your database server is running at `01jg46vq3dpsmq7r9wv0peq7h6.cdg1.db.prisma-data.net:5432`.
maybe not related to my problem but it seems you have a problem on your side:, it happened around 14:40 and it's back to the normal, db seems unreachable for like 2 minutes
Nurul
Nurul•2mo ago
Prisma Postgres is undergoing maintenance due to which it is unavailable: https://www.prisma-status.com/
Prisma Data Platform Status
Welcome to Prisma Data Platform's home for real-time and historical data on system performance.
Nurul
Nurul•2mo ago
This is a one time maintenance as we are working towards making Prisma Postgres production ready It should be back up shortly

Did you find this page helpful?