2 months ago
I get the following error when hitting apn api via railway which requires access to Neon Db. Works perfectly fine on my local and I'm able to reach Neon from my local deployment.
PrismaClientInitializationError:
Invalid prisma.user.findFirst() invocation:
Can't reach database server at ep-morning-sunset-****-pooler.eastus2.azure.neon.tech:5432
Please make sure your database server is running at ep-morning-sunset-****-pooler.eastus2.azure.neon.tech:5432.
at Xn.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7759)
at Xn.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:6784)
at Xn.request (/app/node_modules/@prisma/client/runtime/library.js:121:6491)
at async l (/app/node_modules/@prisma/client/runtime/library.js:130:9812)
at async /app/dist/lib/prisma.service.js:17:32
at async Object.authenticate (/app/dist/middleware/auth.middleware.js:31:21) {
clientVersion: '6.11.0',
errorCode: undefined,
retryable: undefined
}
1 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
We recently had a networking issue that could have caused this. It looks like your service is running now, but if you're still seeing connection failures to Neon, try redeploying so it lands on a fresh host - that's been the reliable fix for affected services.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 2 months ago