Good news: It’s not a WordPress issue.
Bad news: It’s an infrastructure problem, so I get to hurry up and wait 😉
Doug – if it is, is that a problem?
Dan:
Yes. cURL tries to verify the integrity of SSL certs and will error out unless told to ignore verification.
See, e.g. https://wordpress.org/support/topic/server-self-connect-error-nss-client-cert-not-found?replies=6
Basically, you need to run the equivalent of curl -k:
-k, –insecure
(SSL) This option explicitly allows curl to perform “insecure” SSL connections and transfers. All SSL connections are attempted to be made secure by using the CA certificate bundle installed by default. This makes all connections considered “insecure” fail unless -k, –insecure is used.
See this online resource for further details: http://curl.haxx.se/docs/sslcerts.html
I added that to a MU-plugin and now one box returns:
RSS Error: WP HTTP Error: NSS: client certificate not found (nickname not specified)
and the other returns:
RSS Error: WP HTTP Error: Peer certificate cannot be authenticated with known CA certificates
Disregard the above. I’m now getting the same error on both servers
RSS Error: WP HTTP Error: Peer certificate cannot be authenticated with known CA certificates
In a MU-plugin, I’ve added the following:
add_filter(‘https_local_ssl_verify’, ‘__return_true’);
add_filter(‘https_ssl_verify’, ‘__return_true’);
and I still get the error…Ideas?
I changed the filter to __return_false, and now I’m getting:
RSS Error: WP HTTP Error: NSS: client certificate not found (nickname not specified)
