Why am I receiving a SSH remote key error

[kylestarr]

On June 22, 2019, I was able to successfully git push to my Dreampress staging environment. On September 29, 2019, I received the following error:

curl: (60) SSL peer certificate or SSH remote key was not OK
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could notestablish a secure connection to it. To learn more about this situation andhow to fix it, please visit the web page mentioned above.

It looks like there is a new process running that checks for curl:

Mon Sep 30 05:34:31 UTC 2019: Check if curl is functional.

Which in turn fails.

Did something change with Pipelines between June 22 and Sept 29 that would cause this? 

[kylestarr]

I'm able to get around this by adding --insecure to my git ftp push command, but I would love to solve this securely.

[Daniil Penkin]

Hello @kylestarr,

Is the TLS certificate up to date on the host you're trying to connect to? The default Docker image Pipelines is using hasn't changed, if you were asking about that. If you're using a custom image to run your pipeline, this is irrelevant though.

Hope this helps.

Cheers,
Daniil

[kylestarr]

Hi Danni,

It looks like the version of git-ftp has been updated, from 1.3.1 to 1.5.1. That’s probably the rub.