Le
TTCTheo's Typesafe Cult
•Created by Le on 7/24/2024 in #questions
NextAuth problem in production on Vercel
I changed my smtp server to just gmail now, and the email provider works
I will mark your first answer as a solution because it's the closest thing to the solution. Thanks for the assistance
23 replies
TTCTheo's Typesafe Cult
•Created by Le on 7/24/2024 in #questions
NextAuth problem in production on Vercel
Alright the google provider works fine now, I recreated the project, I created another database, and created another google project. I carefully added each environment variable except nextauth_url, then I cleared my site data, and it worked.
Before this I did try updating prisma, it didn't seem to be the issue. I'm afraid the issue might have been with the env after all, as I initially just pasted the .env into vercel, but this time I copy-pasted each key and each value separately.
The current issue is just the email provider, I get a 504 "This Serverless Function took too long"
23 replies
TTCTheo's Typesafe Cult
•Created by Le on 7/24/2024 in #questions
NextAuth problem in production on Vercel
no worries, much appreciated
23 replies
TTCTheo's Typesafe Cult
•Created by Le on 7/24/2024 in #questions
NextAuth problem in production on Vercel
⨯ PrismaClientUnknownRequestError:
Invalid prisma.user.findUnique() invocation:
Error occurred during query execution:
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(PostgresError { code: "42P05", message: "prepared statement "s3" already exists", severity: "ERROR", detail: None, column: None, hint: None }), transient: false })
at _n.handleRequestError (/var/task/node_modules/.pnpm/@prisma+client@5.17.0_prisma@5.17.0/node_modules/@prisma/client/runtime/library.js:121:7939)
at _n.handleAndLogRequestError (/var/task/node_modules/.pnpm/@prisma+client@5.17.0_prisma@5.17.0/node_modules/@prisma/client/runtime/library.js:121:7057)
at _n.request (/var/task/node_modules/.pnpm/@prisma+client@5.17.0_prisma@5.17.0/node_modules/@prisma/client/runtime/library.js:121:6741)
at async l (/var/task/node_modules/.pnpm/@prisma+client@5.17.0_prisma@5.17.0/node_modules/@prisma/client/runtime/library.js:130:9355) {
name: 'GetUserByEmailError',
code: undefined
}
23 replies
TTCTheo's Typesafe Cult
•Created by Le on 7/24/2024 in #questions
NextAuth problem in production on Vercel
sure thing, I will share both. Give me a sec
23 replies
TTCTheo's Typesafe Cult
•Created by Le on 7/24/2024 in #questions
NextAuth problem in production on Vercel
it gives me a 504 error
23 replies
TTCTheo's Typesafe Cult
•Created by Le on 7/24/2024 in #questions
NextAuth problem in production on Vercel
but the email provider still doesn't work
23 replies
TTCTheo's Typesafe Cult
•Created by Le on 7/24/2024 in #questions
NextAuth problem in production on Vercel
in the drizzle project, the production version google provider works
23 replies
TTCTheo's Typesafe Cult
•Created by Le on 7/24/2024 in #questions
NextAuth problem in production on Vercel
yeah
23 replies
TTCTheo's Typesafe Cult
•Created by Le on 7/24/2024 in #questions
NextAuth problem in production on Vercel
yo thanks for the response
I had the google provider secrets in my env, so I think it was something else.
I looked at my logs on vercel and saw some prisma erros but I didn't really know how to resolve them. I suspected it had something to do with the direct_url database_url thing, so I scaffolded another project with drizzle to test it out
23 replies