Problem upgrading multisite to 4.5.2, Error message: couldn't connect to host

  • I am trying to upgrade my multi-site installation to 4.5.2 But when I click “upgrade network” I receive the following error:

    Warning! Problem updating https://1nw.suttonscouts.org.uk. Your server may not be able to connect to sites running on it. Error message: couldn’t connect to host

    Any suggestions for diagnosis please?

    Ian

Viewing 6 replies - 1 through 6 (of 6 total)

  • Are you with a hosted service provider? When upgrading WP, WP makes a call to itself for each site. Some servers are configured so that it does not allow a server to call itself.

    This happens more often in an Enterprise; and security configurations prevent servers making calls to itself. Happens in our environment. We added the site hostnames to the servers /etc/host to fix our problem.

    Thread Starter imellor

    (@imellor)

    Yes I am hosted. Is it a case of asking 127.0.0.1 to be added?

    Thread Starter imellor

    (@imellor)

    Also, I note the error is: couldn’t connect to host not “host unknown”

    > Yes I am hosted. Is it a case of asking 127.0.0.1 to be added?

    No. When you upgrade, the server will make a call like this:
    https://1nw.suttonscouts.org.uk/wp-admin/upgrade.php?step=upgrade_db

    It makes that call for every single WP site you have…of course with the site specific hostname. For some reasons your hosting provider configuration is blocking the WP server to make a call to itself. You might want to open up a support ticket.

    > Also, I note the error is: couldn’t connect to host not “host unknown”

    Yes, you can ignore my comment about our workaround. But to give more details why it works for us. We use the /etc/hosts for routing purposes, not for resolution. If we didnt specifically put the entry in /etc/hosts, the url call routes to our LB; and our LB doesnt like returning back to original server. The LB blocks the call, it connects but never completes – we get the same message as you.

    LB = load balancer

    Thread Starter imellor

    (@imellor)

    OK, I opened up a support ticket and they have checked my shared hosting config and said it is all OK. They did suggest adding the line define(‘ALTERNATE_WP_CRON’, true); which has removed the error from one of my CRON monitoring plugins.
    I also renamed all my plugins and MU_plugins to disable them, but I still receive the same error?

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Problem upgrading multisite to 4.5.2, Error message: couldn't connect to host’ is closed to new replies.