kingrazor001

I figured it out. Through judicious use of grep I found that a few min.js and min.css files within the uploads folder still mentioned the old url, so I manually updated those files. No more errors.

• This reply was modified 6 years, 5 months ago by kingrazor001.

I fixed it. Needed to install the intermediate certificate from GoDaddy.

No. No issues with the network. All hosts on the network can communicate with each other without issue, and can communicate both ways with outside networks. The network is as healthy as it can be. The only error I see anywhere is within wordpress, and as far as I can tell, everything works other than this curl error.

I get the same certificate issuer is not recognized message.

api.numedics.com

I don’t see any issues when I navigate to the site, the browser recognizes the cert and the full cert path.

It connects, but I get an “Unable to locally verify the issuer’s authority.” message. I’m using a Go Daddy certificate.

I have wordpress installed on a CentOS server in my company’s server room. Everything seems to be working, just can’t figure out how to get rid of this error.

I’ve added this line to my wp-config.php file: define('ALTERNATE_WP_CRON', true);

I’ve also added my wp site’s hostname to the hosts file on the server.

Now I’m getting a different error, which hopefully means I’m making some progress:

 The loopback request to your site failed, this may prevent WP_Cron from working, along with theme and plugin editors.
Error encountered: (0) cURL error 60: Peer's Certificate issuer is not recognized.

I’m the one hosting it.