Log the expected location for ssl cert

[NAllred91]

Problem

I'm trying to use prisma with Netlify functions, but I've been unable to get prisma to find my database ssl cert, no matter where I put it.

I get the following error, even with the cert file right next to my schema.prisma file.

Error opening a TLS connection: cert file not found (No such file or directory (os error 2))

Suggested solution

I'd suggest this error let you know where its actually looking. I've confirmed the file does exist in my serverless function, but without knowing where exactly prisma is looking I haven't been able to update the path in my database url to point to the right place.

[janpio]

Can you help us get a reproduction of this, maybe a simple repo that we can easily deploy to Netlify and that shows this error? Then we can investigate what is going on. Thanks.

[NAllred91]

Unfortunately, I'm unable to reproduce this original bug. Netlify dev now breaks with different errors.

[NAllred91]

The original error has been replaced by

PrismaClientInitializationError2 [PrismaClientInitializationError]: 
Invalid `prisma.user.upsert()` invocation:


  Can't reach database server at `*****-0.b.db.ondigitalocean.com`:`25060`

Please make sure your database server is running at `*****-0.b.db.ondigitalocean.com`:`25060`.

These issue are eventually resolved by deleting node_modules and reinstalling. The issues only occur after adding a new migration, and can take a few tries deleting node_modules and reinstalling before database connections work again.

Would you happen to have an example where netlify-dev is working properly?

[janpio]

What exactly do you mean by "netlify-dev"?

[NAllred91]

It's the development environment used when building Netlify functions.

https://www.netlify.com/products/dev/#how-it-works

It allows you to run your serverless functions locally. I did find the prisma documentation about deploying to netlify, but I didn't see anything specifically about working with prisma in this environment locally.

I'm sure its something small I'm missing somewhere! But without that something the development experience is rocky.

[janpio]

Ok, just needed the clarification that this is when using netlify dev, the CLI command 👍 With that we can try to debug and reproduce.

[NAllred91]

Thanks! I've just gotten around to actually deploying my project on Netlify and see similar issues. Although I'm unable to resolve the deploy issues since I can't manually remove and reinstall node_modules.

Following this documentation (https://www.prisma.io/docs/guides/deployment/deployment-guides/deploying-to-netlify) doesn't seem to indicate that I've missed anything.

I've noticed that setting binaryTargets = ["native"] is important for Netlify, but I don't believe that is related to the error "Can't reach database server"?

[NAllred91]

So I eventually got Prisma to work on Netlify. As far as I can tell, the following changes have resolved my problems in the dev environment and on Netlify production environments.

Overall, it seems that the issue was that in some cases Prisma could not connect to the database because it could not find my SSL cert. Unfortunately, the only error it gave was Can't reach database server, so this was difficult to track down.

I needed to make two changes to correct this in my environment.

In schema.prisma, I needed to make sure that it would output in the top-level node_modules. Before this, it would output in the node_modules in the .netlify directory.

generator client {
  provider = "prisma-client-js"
  binaryTargets = ["native"]
  output = "../node_modules/.prisma/client"
}

Then, as part of my build command, I run the following script after I run prisma generate. This moves my entire prisma folder (including the cert that sits next to schema.prisma) into the client directory. Then, I modify the client code to point to this directory.

const fs = require('fs-extra');

fs.copySync('./prisma', './node_modules/.prisma/client/prisma');

let prismaClient = fs.readFileSync('./node_modules/.prisma/client/index.js', {
    encoding: 'utf8',
});

prismaClient = prismaClient.replace(
    '"relativePath": "../../../prisma",',
    '"relativePath": "./prisma",'
);

fs.writeFileSync('./node_modules/.prisma/client/index.js', prismaClient);

This isn't a long term fix, but it at least lets me put builds on Netlify this week. Hopefully this is helpful to you as well!