brazen goblet
Hey guys,
since supabase changed their pooler and probably also moving away from IPv4, I keep running into a problem of not being able to connect anymore, neither through the pooler nor directly.
Should I create a new user for triggerdotdev, or how do you successfully connect?
I either keep getting a SSL error, or even PrismaClientInitializationError: Can't reach database server at aws-0-eu-central-1.pooler.supabase.com:5432`
subtle nymph
Hi @brazen goblet! I am not sure what you setup is, but maybe using port 6543 and ?pgbouncer=true&connection_limit=1 reccommended for serverless enviroments can help?
eg. postgres://postgres.YOUR_INSTANCE:[email protected]:6543/postgres?pgbouncer=true&connection_limit=1
You will still want to use standard 5432 for prisma migrations , deployments and such
brazen goblet
You will still want to use standard `5432` for prisma migrations , deployments a...
Thank you. I got further, now the error is: FATAL: Tenant or user not found Any idea what this could be? Should I create a new user for trigger.dev?