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
prisma.account.findUnique() invocation:
Can't reach database server at localhost:5432
Please make sure your database server is running at localhost:5432.
[next-auth][error][adapter_error_getUserByAccount]
https://next-auth.js.org/errors#adapter_error_getuserbyaccount
Invalid prisma.account.findUnique() invocation:
Can't reach database server at localhost:5432
Please make sure your database server is running at localhost:5432. {
message: '\n' +
'Invalid prisma.account.findUnique() invocation:\n' +
'\n' +
'\n' +
"Can't reach database server at localhost:5432\n" +
'\n' +
'Please make sure your database server is running at localhost:5432.',
stack: 'PrismaClientInitializationError: \n' +
'Invalid prisma.account.findUnique() invocation:\n' +
'\n' +
'\n' +
"Can't reach database server at localhost:5432\n" +
'\n' +Errors | NextAuth.js
This is a list of errors output from NextAuth.js.
2 Replies
Did localhost ever work for connecting to a postgres db on Vercel? I wouldn't expect it to you should have a database url to use
I really thought it did, but I could be tripping. I appreciate the reply as I could be a complete idiot on this.
I thought it worked.. I'm dying with a stomach flu and honestly am foggy on it all. Pretty sure I got the vercel server working with auth through discord as per the instructions, and it had to have a postgres up there to do that. I also saw the secret message, which was TRPC through the db, I assume. I didn't "set up" a vercel postgres db.
maybe I accidentally blew away my URL in my env somewhere...