WordPress update.php error

  • Resolved karljv

    (@karljv)


    8 years, 11 months ago

    Hi

    I am writing because a lot of people have been experiencing issues with wp-admin having long load times and giving an error on update.php on various lines.

    (WordPress could not establish a secure connection to www.ads-software.com. Please contact your server administrator.) in D:\ABC\XYZ\wp-includes\update.php on line 295

    There seems to be little information and almost no solutions to be found for this exact problem, so I am going to post my solution here.

    I found out that these update.php errors were caused by curl failing with an ssl connection timeout. The problem was that curl was resolving DNS records at a really slow speed and the connection just timed out. When using Linux server, then CURL uses the /etc/resolv.conf file to look up a DNS server to use. I opened the file and replaced the DNS server IP address with 8.8.8.8, which is Googles own DNS server and the problem resolved.

    WP-admin load times went from 6 seconds to an astounding 200ms which is more appropriate for the server configuration I am using.

    I hope this post helps some of you tackle the immense load time while developing on WordPress.

    Karl

Viewing 9 replies - 1 through 9 (of 9 total)
  • Moderator James Huff

    (@macmanx)

    Another source of this error could be an out-of-date copy of OpenSSL on the server.

    Thread Starter karljv

    (@karljv)

    Good input!

    I also first thought that an out-of-date OpenSSL was an educated guess on what was wrong.

    For information I was using a virtual machine on my OSX El Capitan, running Parallels Desktop 10. Linux Server 14.xx stable (I’m too lazy to check right now).

    Right before modifying my /etc/resolv.conf file, I updated everything related to apache2, with “sudo apt-get upgrade apache2”. This also updated my OpenSSL copy, but alas no success on fixing the problem.

    Moderator James Huff

    (@macmanx)

    Just to be sure, run: openssl version

    OpenSSL is installed by the OS, not Apache, so it’s still possible you could be running on an old version.

    The current version of OpenSSL is 1.0.2e.

    Thread Starter karljv

    (@karljv)

    apt-get upgrade apache2 also updates the dependancies so

    “sudo apt-get upgrade openssl”

    gave the response

    “sudo apt-get upgrade openssl
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    Calculating upgrade… Done
    openssl is already the newest version.
    “

    Im not a veteran linux server admin though, so take my advice with a grain fo salt ??

    Moderator James Huff

    (@macmanx)

    Just to be sure though, run openssl version

    If I had $5 every time a server package said the latest version was 0.9.8, I’d have … well … $15, but you get the idea. ??

    Thread Starter karljv

    (@karljv)

    I admit my mistake

    "karl@ubuntu:~$ openssl version
OpenSSL 1.0.1f 6 Jan 2014"

    But even as I was wrong on this account, it was not the problem for me, but it might be worth checking out for others.

    Moderator James Huff

    (@macmanx)

    1.0.1 should be fine, so it was definitely the other fix. Thanks for checking!

    Thread Starter karljv

    (@karljv)

    Hi again

    I will update on my input. Changin resolv.conf is partially a wrong solution, since the file gets overwritten on server restart. Thus please refer to this article to correctly resolve the issue -> https://askubuntu.com/questions/479506/override-dns-nameserver

    Moderator James Huff

    (@macmanx)

    Thanks for letting us know!

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘WordPress update.php error’ is closed to new replies.