#marketplace

yasoob Hi eric, thanks for letting us know. Could you please try again? The Prisma team has just pushed out a fix.

eric Hi yasoob, thanks for the follow-up, and sorry for the late reply. I just tested it again and the issue is resolved now. I do want to share some feedback, though. Because of this error, we had to remove the Prisma Postgres integration from our service and migrate to a different database provider. An issue like this takes the whole service down, not just one feature. It took a long time to get a response, and in the meantime there was nothing we could do on our end. No status update, no workaround, no escalation path. For integrations that sit on the critical path, like database auth/SSO, a fas

Pawelmroczek6 6823 pmrapiddeliverydopracowana-2.vercel.app

system Hi there! I'm just a bot here to share some info that might help you before a human arrives. If your account is eligible, you can use our new self-service recovery flow: Go to vercel.com/login Choose to sign in using the email + one-time password (OTP) option. Select Use another sign-in method Verify your identity using the GitHub, GitLab, or Bitbucket account previously linked to your Vercel account Follow the remaining prompts to complete the recovery process If you've ever set up a passkey, possibly on another device, you can use that to get back into your account and update 2FA settings yo

Eduardo Pavez Hi @amyegan, Any thoughts on this? Thanks!

Amy Egan Hey @epavez, sorry I missed your earlier post! For the database filter, I believe those are typically related to Vercel Marketplace integration options. I'd be happy to get you connected with the team if you want to explore adding Backblaze B2 to the marketplace. Just lmk if you're interested in that 😃 As for the full-stack deployment, it looks like you already configured Services in a vercel.json file to deploy everything in a single Vercel project. That's the right approach for all-in-one deployment. Let me ask the templates team if they have any other info or recommendations

Amy Egan If you're using the Supabase integration, you can delete it from the Vercel dashboard in integration settings. If you're using a separate Supabase account, you can manage that in your account or organization settings at supabase.com

Ryu Hi JorgY\_, Given your diagnostic output, I’d focus on the Supabase connection type rather than the PHP env vars. The suspicious part is: Database: Supabase Postgres Direct connection Port: 5432 pdo_pgsql_loaded: true sslmode=require Works locally, fails on Vercel Supabase direct database connections use IPv6 unless you have the IPv4 add-on enabled. Vercel serverless functions are commonly the case where the direct db.<project-ref>.supabase.co:5432 connection fails, even though the same credentials work locally. I’d switch the deployed PHP API to the Supabase Shared Pooler / Supavisor connecti

Pauline P. Narvas Hey! I'll check with our Marketplace team. 🙂 In the meantime, which other community posts have you seen which are similar?

Ryu Hi Vsme, I’d treat this as a potentially risky env/branch-mapping issue and disable any automatic migration-on-start behavior until you confirm which database the v0 chat is actually using. A safe way to debug it is to log only the environment and Neon host/branch, not the full connection string or password: console.log({ vercelEnv: process.env.VERCEL_ENV, publicVercelEnv: process.env.NEXT_PUBLIC_VERCEL_ENV, databaseHost: process.env.DATABASE_URL ? new URL(process.env.DATABASE_URL).host : "missing", }) If the v0 chat/preview shows production or points at the same Neon host/branch as production