Prisma•5mo ago

Serving HTTPS from Prisma Client

I'm currently trying to spin up an AWS EC2 Instance with my Prisma Client Code base. I have it connected to an AWS RDS Instance and was able to connect and migrate to that. But my EC2 instance for the API has an SSL Cert and I have an A Record and CNAME set up for an HTTPS endpoint, but when I curl against the endpoint I receive:

 Connected to URL (IP) port 4000
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/pki/tls/certs/ca-bundle.crt
*  CApath: none
* OpenSSL/3.0.8: error:0A00010B:SSL routines::wrong version number
* Closing connection
curl: (35) OpenSSL/3.0.8: error:0A00010B:SSL routines::wrong version number

 Connected to URL (IP) port 4000
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/pki/tls/certs/ca-bundle.crt
*  CApath: none
* OpenSSL/3.0.8: error:0A00010B:SSL routines::wrong version number
* Closing connection
curl: (35) OpenSSL/3.0.8: error:0A00010B:SSL routines::wrong version number

How do I direct my Prisma client to use my SSL Cert/Key? Is it the same as my Web instancce where I need to pass them as ENV Values on initialization? Or is there code configuration I can do? I haven't been able to see anything about enabling SSL on the Client, just stuff talking about using it on the DB, which I already have handled.

1 Reply

darksyndaciteOP•5mo ago

I figured out the issue, I was looking up stuff for Prisma ORM/Client when I'm using Apollo Server lol

Gaming

Programming

Serving HTTPS from Prisma Client