prisma pulse + supabase?
Hi folks, I am experiencing an issue when trying to enable Pulse with my supabase-hosted postgresql db. I have configured the DB using the Prisma instructions from Supabase to create a bespoke Prisma user (see here - https://supabase.com/docs/guides/database/prisma) , and am using the direct connection string postgresql://prisma:<password>@<supabase-url>:5432/postgres - however I continue to run into an error when trying to enable Pulse. I have enabled accelerate without issue, so I know that the connection string is working, however there is no feedback on what exactly is going wrong with Pulse.
9 Replies
You're in no rush, so we'll let a dev step in. Enjoy your coffee, or drop into
#ask-ai if you get antsy for a second opinion!any updates on this?
i have the same issue
ok, good, it's not just me - makes me think it might be a bug 🙂
Hi @pixellord
Can you please share the error message you received when trying to enable Pulse with Supabase?
Hi @RaphaelEtim yes - see the attached image. Nothing pops in the browser console log that would be more helpful, unfortunately.
Thanks for sharing. I’ll try to reproduce this on my end
Hi @pixellord
I can reproduce this issue. You need to append
sslmode=disable to the end of your direct database connection string.
For example:
thanks so much @RaphaelEtim , that worked!
You’re welcome
and to document for others - you only need the
?sslmode=disable on the connection string when setting up Pulse - in your env files, you can use the pooler connection