Happy New Year!
I’m trying to connect a new v0 project (“Pocket Dimension Web”) to a Supabase database, but I’m stuck due to what appears to be a phantom database counting toward my 2-database limit.
Background:
I previously had 2 v0 projects connected to Supabase
I deleted one of those projects (which had been idle for 90+ days) from v0
I also deleted the corresponding database in Supabase itself
Problem:
Despite deleting both the v0 project and the Supabase database, the system still sees me at my 2-database limit. This prevents me from:
Creating a new Supabase project through v0
Installing the Supabase integration on my new project to connect to an external database
Troubleshooting Steps Already Taken:
Deleted the integration through the Vercel Marketplace (Settings → Delete section)
Waited several hours for the system to update
Installed the Vercel integration in my personal Supabase account and pointed it to “Pocket Dimension Web”
Current Status:
The project can see the database and schemas, BUT:
I have to manually copy and execute SQL scripts in the Supabase SQL Editor
I can’t see the data in v0 preview due to the lack of proper connection
I’m essentially flying blind without the full integration working
Question:
How can I fully remove the orphaned Supabase integration so it stops counting toward my limit, or alternatively, how can I properly complete the connection to my external Supabase database so v0 can preview the data?
Did you know there’s another category dedicated to v0 topics? A human should be here soon to help, but the answer may already be available even faster in one of these other posts.
Our docs are a great place to start.
We also have a walkthrough to help guide your workflow.
And these recordings can give you a look at v0 features and strategies in action shown by our Community:
Happy New Years and thanks for getting back to me. So what you’re seeing in my account is actually a new project I started up after opening the ticket. I think I figured out my issue;
I created my v0/vercel account with my Dev email (attached to this account). I also, previous to having a v0 account, had a Supabase account with that same Dev email that I was using for other projects. It looks like the external account that was active and my v0 projects and v0 supabase account, count towards my 2 free Projects in total. I never noticed this previously because one project was always paused. But during the time of this issue I had 2 active projects, one in v0 and one in supabase directly. And spinning up the 3rd project here in v0 and attempting to attach it to my existing supabase db caused me to be aware of that limit and the connection .
So I bit the bullet and paid for a pro account to get past the limitation, but I reached another problem that I’m able to work around.
Initially I wanted to create a new project in v0 and attach it to my external supabase account project db. Unfortunately, within v0, when trying to install the supabase integration, I have to create a DB first. Which is where I hit my initial snag with this support ticket. So since I’d rather not create another db at the moment, I provided the keys to the external project db I wanted to connect to and its currently working…..
But I want to stress that before I upgraded my supabase account, I was unable to even install the integration within v0 because it requires spinning up a new project db to install that integration smoothly. And to be clear, I was able to provide keys when I opened the ticket, but the app I was building would not show me persisting data from the db in preview. I’d have to deploy the app somewhere to test. Right now everything is working fine enough.
I’m not going to spin up a new db just to be able to run SQL injections within this browser tab, I can copy/paste. But it would be nice to be able to install that integrations without needing to spin up a whole db for it.
You can close this ticket if need be. I’ll mark this as my solution. And thank you again!
Did you try this little drop down to select an existing DB? The install button goes straight to the New DB flow but the arrow is meant to let you link to an existing one
Outside of that, you always have the power to add environment variables manually. The integration is really just a shortcut for that
Hey, yes I did check there. The dropdop only shows the other db’s in my Vercell/v0 account, not the external Supabase Account.
I have 3 DB’s in total after deleting 1 project in v0 and one in supabase. 2 are currently Internal to Vercel, and 1 external directly in Supabase. It only shows the other v0 project db -
I did add the environment variables manually before, but the data wasn’t being displayed in the app preview until I upgraded my Supabase account. But there might hav been a different reason there.
Its working 100% now. I did need 3 db’s but I thought the v0 and Supabase accounts were counted separately. I’m the one who linked my dev email to both so whether its a Supabase thing or a Vercel thing (sounds like Supabase via Vercel) I understand that it’s a thing. I would have needed to pay for it soon enough anywho.
.
