SELF_SIGNED_CERT_IN_CHAIN error on DigitalOcean App Platform deploy

[thick field]

[2023-03-14 18:39:26] Error: self-signed certificate in certificate chain
[2023-03-14 18:39:26]     at TLSSocket.onConnectSecure (node:_tls_wrap:1540:34)
[2023-03-14 18:39:26]     at TLSSocket.emit (node:events:513:28)
[2023-03-14 18:39:26]     at TLSSocket._finishInit (node:_tls_wrap:959:8)
[2023-03-14 18:39:26]     at ssl.onhandshakedone (node:_tls_wrap:743:12) {
[2023-03-14 18:39:26]   code: 'SELF_SIGNED_CERT_IN_CHAIN'
[2023-03-14 18:39:26] }

I cannot seem to figure out if its this a medusa issue or a digital ocean issue. Digital Ocean manages certs so in my mind I think I want to just be able to run the backend without consideration for TLS. I don't understand how to interpret the issue really at all but its blocking deploys.

[limpid comet]

Hey @thick field, not sure if you have got your issue resolved. I encountered the same issue earlier today. My problem was that I copied the Postgres URL provided on the Digital Ocean and it has ?sslmode=required at the end. I just removed it and I was able to deploy again. Hope this helps your case also!

[thick field]

yea! thanks so much for reaching out. I also found I had done the same thing and resolved in the same way.

sorry i should have updated my Q

[limpid comet]

Lovely. Glad you have it resolved also!

[astral talon]

After removing ?sslmode=required from the connection string I still get an error:

Is anyone else facing this problem?

I managed to resolve the issue - in case anyone else runs into this then it's possible to add &sslrootcert=/path/to/ca-certificate.crt to the connection string. You can download ca-certificate.crt from the managed database page in DigitalOcean.

[lime oxide]

Just got this error having trouble finding where to change the connection string. Whenever I find it it's read only.