Forums

Problem updating to 3.1 with network (8 posts)

  1. maltamario
    Member
    Posted 1 year ago #

    I'm going from 3.0.5 to 3.1
    I was able to update to 3.1 but not the blogs within the network, when a try to update the network I get this error

    Warning! Problem updating . Your server may not be able to connect to sites running on it. Error message: A valid URL was not provided.

    I have no errors in my php error log and nothing in my apache error log. Is this a known issue? I didn't tell me the blog in question either so I can't check to see if it's loading properly.

    I'm running FreeBSD 7.3-Release with Apache 2 / Nginx / PHP 5.3.5
    Thanks

  2. Andrea_r
    team pirate
    Posted 1 year ago #

    Are you actually in *network* admin when you hit that?

    And... logging in to the admin area of a sub site will fire the same processes.

  3. tmuka
    Member
    Posted 1 year ago #

    I have the same issue trying to "update network". I'm running a pair of servers behind a load balancer, i'm wondering if that's related to this problem.

  4. Andrea_r
    team pirate
    Posted 1 year ago #

    The first blog it hits in that listing is the second blog in your network. Cuz you;re alreayd on blog #1 and just upgraded it.

    If that helps.

    I have hit this error on one of my test sites, and it stopped at a mapped one where the domain itself was down.

  5. Jason
    Member
    Posted 1 year ago #

    I've got the same/similar issue. Upgraded to 3.1 (able to do it manually and automatically through the backend) but "update network" not working. In my case it just doesn't do anything.

    Running on a pair of servers also. Sub domain setup with nginx

    Domain appears to be resolving fine on each of the servers.

    Also - none of the themes (including twentyten) are appearing as enabled on any of the sub blogs either - not sure if it is related to not being able to upgrade the network though

  6. Andrea_r
    team pirate
    Posted 1 year ago #

    Eh, probably not (on the theme thing).

    We just got an nginx box (again) but I think we alreayd upgraded before the move, or I'd test that.

    If it helps, the same action is fired when someone visits the admin area of the sub sites. that does the same "update network" on that site.

  7. Jason
    Member
    Posted 1 year ago #

    Thanks Andrea - figured out it was my own fail with the themes - one of the nfs shares on one of the servers wasn't configured properly so it couldn't find the themes!

    Update network still having issues but it's not a big concern - yet

  8. tmuka
    Member
    Posted 1 year ago #

    The workaround i've found for this issue is to temporarily change my local workstation's hosts file and that one server's hosts file to point to only one of the server's internal IPs, like

    192.168.1.200 http://www.example.com

    this did the trick for me with the 3.1.1 upgrade. hope it helps you.

Topic Closed

This topic has been closed to new replies.

About this Topic