Viewing 6 replies - 1 through 6 (of 6 total)
  • Several of our servers encountered this issue as well as disconnects from Akismet. Turned out to be a DNS issue. Are you using OpenDNS?

    If your /etc/resolv.conf contains:
    nameserver 208.67.222.222
    nameserver 208.67.220.220

    try changing to Google’s public DNS servers:
    nameserver 8.8.8.8
    nameserver 8.8.4.4

    I had the same issue today, but changing the nameservers didn’t help. The command line curl started to work (which wasn’t working before) but the wordpress plugin updates still gave the same error message. Has anyone found another solution to this?

    Thread Starter pmcjones

    (@pmcjones)

    The admin at my ISP just emailed me, “No we do not use OpenDNS or Google. I just refreshed our DNS cache in case that is related (though nslookups against our DNS as well as Google and OpenDNS all returned the same results).”

    I tried again, and this time the WordPress 3.9 one-click update succeeded (as did the Akismet 3.0 update, which had been giving the same error message).

    Update to the above, managed to get it working. I run a VPS so everytime the server rebooted it pulled the resolv file from the host with teh openDNS details in there. Once you have made your changes to /etc/resolv.conf to use googles public DNS servers (as below) you need to chattr the file so it cant be overwritten on a reboot and then reboot the server.

    nameserver 8.8.8.8
    nameserver 8.8.4.4

    See this link on how to keep the resolv file the same on an OpenVZ VPS

    https://wiki.vpsget.com/index.php/OpenVZ_:_/etc/resolv.conf_doesn%27t_keep_its_content_after_the_reboot

    How about OpenSSL? All Hosts use OpenSSL and all Hosts should have installed the patch for the recent security vulnerability found in OpenSSL. Logically I would think either your Host messed something up with the OpenSSL patch installation or the SSL certificate you are using needs to be deleted and and a new SSL Certificate needs to be issued to you. If you do not have an SSL Certificate then this could be a Shared SSL Certificate problem on your Host Server.

    I’ve fixed this issue by simply repairing and optimizing the tables of my database. Let me know if it worked for you.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Download failed.: SSL peer certificate or SSH remote key was not OK’ is closed to new replies.