Yannick Gloster

I hadn't though of testing that @janpio, I just did and I got the same error: ``` [GET] /api/tournaments 17:56:15:24 2022-01-28T17:56:15.974Z 4b670608-cb13-48cf-aca0-26f63e32b1f7 ERROR PrismaClientInitializationError: Can't reach database server at `IDONOTEXIST`:`3306`...

Ah yes, I did do it with the IP, I changed the cert path and I'm still getting the same error. As far as I can tell, the content is...

I was able to find the route cause of the issue. Prisma was not reading the composed env when deployed through vercel. Once I fixed the path directly into the...

I set the composed environment variables following what was written in the docs: https://www.prisma.io/docs/concepts/components/prisma-schema#accessing-environment-variables-from-the-schema And they were uploaded to vercel using their UI that was documented here: https://vercel.com/docs/concepts/projects/environment-variables

> So you had `mysql://user:pass@lserverip:3306/registration?sslcert=${SSL_CERT_PATH}&connect_timeout=300 > CRT_PEM=longbase64string` in the field for `DATABASE_URL`? I don't think that is supposed to work at Vercel indeed. Yep that would be correct. It would...

Thank you very much for all your help.