hi! Does anyone know how to fix this error? I'm using Prisma Data Proxy and it fails to connect 😞

Hi @potatoxchip. Could you provide some extra information on your setup? Feel free to use DM if it is sensitive.

generator client {
  provider = "prisma-client-js"
  previewFeatures = ["dataProxy"]
}

datasource db {
  provider = "mysql"
  url      = env("DATABASE_URL")
}

model views {
  id     Int    @id @default(autoincrement())
  ipHash String @db.VarChar(64)
  postId Int

  @@unique([ipHash, postId], map: "views_ipHash_postId_UNIQUE")
}

model posts {
  id          Int       @id @default(autoincrement())
  slug        String    @unique(map: "posts_slug_UNIQUE") @db.VarChar(50)
  description String    @db.VarChar(100)
  title       String    @db.VarChar(50)
  isPublished Boolean?  @default(false)
  createdAt   DateTime? @default(now()) @db.Timestamp(0)
  updatedAt   DateTime? @default(now()) @db.Timestamp(0)
}

this is my

prisma/prisma.schema

file

Cool, just checking a few things

this is the entire console log if it helps

So what I can see is that the engine failed to connect to your database.

I even tried to deploy it to vercel and there also it failed to connect

Yes. Note that the database connection is initiated from the Data Proxy.

Is this a problem from my end tho? I can't seem to narrow it down 😞

The engine logs indicate an issue connecting to your database, so that might be worth double checking.

aight i will try once with

<https://github.com/prisma/deployment-example-vercel/tree/data-proxy>

Data Proxy supports the same connectors as regular Prisma.

im using mysql from planetscale and my connection string has ?ssl_cert as well

Ah, right. I remember there being some weirdness with PlanetScale at some point. Let me check what the deal is there.

oh! aight you can ping me anytime! 👍

Right. I was able to diagnose this against a planetscale DB, and the issue was on indeed on our end. This should be patched across all Data Proxy regions shortly. Thanks for reporting, and lemme know if you are stuck

Thanks for the confirmation!! Well i am stuck with this, but it is not a big issue. I will fallback to using postgres in the meanwhile and then migrate to mysql when this is resolved

Assuming we were observing the same issue with PlanetScale, this should be resolved for you ( at least in us-east , as eu-central is currently updating ) .

aight. i am using us-east, let me check it once

Ah, I see what the issue with your setup is. You are explicitly passing

?sslcert

which tries to name a path. That isn’t going to work - however, omitting that param should unblock you, as that will cause the engine to fall back to our managed CA certs.

ok let me change that in cloud.prisma.io

Hmm. I updated my project with a fresh connection string and that is working correctly. I did that by updating the Connection string under Database in Environment Settings in cloud.prisma.io for my project.

i just made a new planetscale db and still cloud.prisma.io wont connect. If you want, i can share you the connection string

Ah, awesome. Happy days