Prisma’s PostgreSQL connector only supports a specific set of SSL parameters. Historically, `sslrootcert` was *not* supported and would be ignored or cause issues, while parameters like `sslmode`, `sslcert`, `sslidentity`, and `sslpassword` are the documented ones. [[PostgreSQL SSL](); [Custom SSL issue]()] The error `unrecognized configuration parameter "sslrootcert"` suggests that the underlying driver (or Prisma’s layer around it) does not understand `sslrootcert` in the connection string in your current setup. Earlier GitHub issues explicitly mention that `sslrootcert` was not supported and tracked as a feature request. [[Custom SSL issue](); [Cockroach sslrootcert]()] From the available docs, the supported way to configure SSL for PostgreSQL with Prisma is to use: - `sslmode=(disable|prefer|require)` - `sslcert=` - `sslidentity=` - `sslpassword=` - `sslaccept=(strict|accept_invalid_certs)` [[PostgreSQL SSL]()] Given the knowledge sources: - They do not clearly state that `sslrootcert` is fully supported in Prisma Studio today. - They *do* show that `sslrootcert` support has been requested and partially discussed, but not clearly documented as available. So, to get Prisma Studio working based on the documented options, you’ll likely need to: 1. Remove `sslrootcert=./ca.pem` from the connection string. 2. Use the documented SSL parameters (`sslcert`, `sslidentity`, `sslpassword`, `sslaccept`) instead, placing certificate files relative to your `./prisma` folder. [[Data sources](); [PostgreSQL SSL](

Prisma studio

Similar Threads

Similar Threads

Similar Threads