Nutlope / roomGPT

Upload a photo of your room to generate your dream room with AI.
https://www.roomgpt.io/
MIT License
9.78k stars 1.29k forks source link

Not signing in: "try signing in with a different account" error #70

Closed javisolans closed 1 year ago

javisolans commented 1 year ago

Here you can see a preview of the error:

image

rgsaura commented 1 year ago

I also have this problem, very frustraiting, i have tried EVERYTHING without success

Estehsan commented 1 year ago

Tried everything still same issue.

R3P-tech commented 1 year ago

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

rgsaura commented 1 year ago

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" image

goyalpramod commented 1 year ago

image 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?

mmtechhk commented 1 year ago

add '?pgbouncer=true' can fix it. P3P-tech already provide me the answer.

Kellokes commented 1 year ago

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?

caevv commented 1 year ago

Guys don't forget to run npm run build so that the schema migration is executed.

Nutlope commented 1 year ago

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!