postgres db probs on vercel lately?
Has anyone else experienced problems with vercel not finding the server localhost:port of their postgres db? I havent touched this since the vanilla setup of t3 with postgres. Curently only using this as auth with discord. It just decided to stop working and the server is no longer a thing?
prisma:error
Invalid
Can't reach database server at
Please make sure your database server is running at
[next-auth][error][adapter_error_getUserByAccount]
https://next-auth.js.org/errors#adapter_error_getuserbyaccount
Invalid
Can't reach database server at
Please make sure your database server is running at
message: '\n' +
'Invalid
'\n' +
'\n' +
"Can't reach database server at
'\n' +
'Please make sure your database server is running at
stack: 'PrismaClientInitializationError: \n' +
'Invalid
'\n' +
'\n' +
"Can't reach database server at
'\n' +
prisma:error
Invalid
prisma.account.findUnique()Can't reach database server at
localhost5432Please make sure your database server is running at
localhost5432[next-auth][error][adapter_error_getUserByAccount]
https://next-auth.js.org/errors#adapter_error_getuserbyaccount
Invalid
prisma.account.findUnique()Can't reach database server at
localhost5432Please make sure your database server is running at
localhost5432message: '\n' +
'Invalid
prisma.account.findUnique()'\n' +
'\n' +
"Can't reach database server at
localhost5432'\n' +
'Please make sure your database server is running at
localhost5432stack: 'PrismaClientInitializationError: \n' +
'Invalid
prisma.account.findUnique()'\n' +
'\n' +
"Can't reach database server at
localhost5432'\n' +
This is a list of errors output from NextAuth.js.
