Not signing in: "try signing in with a different account" error
javisolans opened this issue · 9 comments
Here you can see a preview of the error:
I also have this problem, very frustraiting, i have tried EVERYTHING without success
Tried everything still same issue.
Update your .env file with both the DATABASE_URL and DIRECT_DATABASE_URL variables settings. As shown in the following example, set DATABASE_URL to the pooled connection string for your Neon database and include pgbouncer=true, and set DIRECT_URL to the non-pooled connection string. https://neon.tech/docs/guides/prisma-migrate
DATABASE_URL=postgres://3xample:password@ep-white-mode-652705-pooler.us-east-2.aws.neon.tech/neondb?pgbouncer=true
DIRECT_DATABASE_URL=postgres://3xample:password@ep-white-mode-652705.us-east-2.aws.neon.tech/neondb
SHADOW_DATABASE_URL=postgres://3xample:password@ep-white-mode-652705.us-east-2.aws.neon.tech/shadow_db
i paid 15$ to a fiver guy to resolve this issue. Your welcome.
"The reason you are getting the error is [DIRECT_DATABASE_URL] because of this database you are adding two database url but its schema is schema add in one now the Google provider login is not getting the database schema.
You have given two different database URLs but Prisma schema is adding to one database. Because of this, it is not finding the database schema while logging in with the Google provider"
I am running into the same issue, but it seems its because the database is not able to establish a connection, Any idea how I can fix it?
add '?pgbouncer=true' can fix it. P3P-tech already provide me the answer.
Even with the above suggestions, I'm still having problem with the same error. I think that Neon's Postgree service doesn't work very well and that's why we can't maintain connectivity between the application and the bank. Does anyone have a suggestion for a similar service to evaluate if it solves the problem?
Guys don't forget to run npm run build so that the schema migration is executed.
Hey all. I've just simplified the repo to remove auth and payments so you can clone and deploy very easily, only with a Replicate environment variable. Try it out and if you still have any problems, please open a new issue and I will take a look!