Hi everyone! I've been trying to set up supabase with prisma and I was able to work with it for a while, now I'm getting

Error: P1001 Can't reach database server at...

even when trying from Beekeeper Studio, I had turned off connection pooling and turned it back on in an attempt to fix a 's3' already exists issue, which I don't find it to be very clear on the Prisma/Supabase docs (this was happening on a regular user create query), anyways, now I'm not able to reach the server 😭 Also I know passwords are not supposed to have any special cahrs, mine doesn't have any

Hello @Jenaro Calvino! This thread has been automatically created from your message in #843999948717555735 a few seconds ago. We have already mentioned the @User so that they can see your message and help you as soon as possible! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ``...`` menu) and select "Leave Thread" to unsubscribe from future updates. Want to change the title? Use the ``/title`` command! We have solved your problem? Click the button below to archive it.

You list several different error conditions and tools. My first suggestion would be to restart your server under general settings (you don't even say if you are hosted, but assuming that). I think Beekeeper is just a database tool and if you can't get that to log in thru the postgres user port you should solve that first.

Jenaro Calvino (2022-05-05)

My issue right now is that I can't reach the server, I had not seen the restart button, which I clicked now, Beekeeper studio should be able to connect given the connection string just like prisma would do

Thread was archived by @Jenaro Calvino. Anyone can send a message to unarchive it.

@Jenaro Calvino your next question should be why did you need to restart the server... If it happens again, try and look at the postgres logs under database as soon as possible and see if you see anything, or note what you did before the server "locked" up.

There are no errors on the postgres logs other than these

prepared statement "s0" already exists

Which I understand have something to do with the connection pooling, not sure how to fix though, I've tried the different connection pooling methods and completely turning it off, I'm using prisma inside of remix (hosted on a netlify serverless function)

I can offer no advice on prisma/pooling as I don't use it, and you seem to have searched for the extent of p1001 errors listed here.