WordPress.org

1. Mikee17
   Member
   Posted 1 year ago #

   Hello,

   We sucessfully(all except the issue mentioned here as far as we see now) updated WPMU-2.9.2 to WP-3.1 MultiSite.

   We are using Multi-DB(http://premium.wpmudev.org/project/multi-db) plugin version 3.0.6.

   There are 200+ users and all of them together have almost 2000+ sites while upgrading and all seem to work fine too.
   All plugins work fine too now, had to update couple of them too before they did.

   But, while logged in as 'admin', it says "Thank you for Updating! Please visit the Update Network page to update all your sites." << We do that and get following messages on different browsers we tried.
   Get the same result when we try to access 'Network Admin' on top right of admin login.

   Safari:
   Too many redirects occurred trying to open “http://{our-site}.com/wp-admin/network/”. This might occur if you open a page that is redirected to open another page which then is redirected to open the original page.
   Chrome:
   This webpage has a redirect loop
   The webpage at http://{our-site}/wp-admin/network/ has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
   IE:
   It keeps on working and has not shown any messages yet, can see 'Waiting for http://{our-site}/wp-admin/network/upgrade.php' on the status bar.
   FF:
   Not tried yet.

   Kindly advice, could it be an upgrade issue or the multi-db plugin related issue or anything else?

   Thanks & Regards

2. Andrea_r
   team pirate
   Posted 1 year ago #

   It could be related to plugins, yes. Make sure all of those are updated as well.

   The "update network" action will also be run as soon as users login to the admin area of their blogs.

3. Mikee17
   Member
   Posted 1 year ago #

   Hi Andrea_r, thank you for the quick reply.

   We are running the latest version of Multi-DB plugin.

   We have several other plugins too, to test if there would be any issue and make sure we can go ahead with an upgrade from WPMU-2.9.2 to WP-3.1, we created another test-domain on the same server and got our original WPMU-2.9.2 in the main site working as it is on the test-domain too and then upgraded the test-domain first, it went smooth and later we also spend few days investigating if all our plugins are working and thus had to upgrade couple of them, then everything looked like it was fine with upgrade from WPMU-2.9.2 to WP-3.1 on our main domain.
   Thus we gained courage to repeat what we did on the test-domain and it went smooth too on our main domain except that we cant go to the networks area, kinda stumped here.

4. Andrea_r
   team pirate
   Posted 1 year ago #

   Some people have reported being unable to access wp-admin/network/. As far as I can determine, it's a server side issue, but I do not know what needs to be changed.

5. Mikee17
   Member
   Posted 1 year ago #

   Hi Andrea_r, should we contact the host regarding the same? I happened to read your post at http://wordpress.org/support/topic/network-update-under-wp-31 regarding similar issue, it says: "certain hosts don't like rendering that nested admin folder."

6. Andrea_r
   team pirate
   Posted 1 year ago #

   Yes, contact your host.

7. Mikee17
   Member
   Posted 1 year ago #

   Hi Andrea_r, what exactly should be ask our host to check/fix?

   We get the following on our error_log:
   Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: http://{our-site}/wp-admin/network/sites.php

8. Andrea_r
   team pirate
   Posted 1 year ago #

   Send them that message maybe?

9. Mikee17
   Member
   Posted 1 year ago #

   The host increased the limit to 100, but now we still get the error with "Request exceeded the limit of 100 internal redirects..." in place of "Request exceeded the limit of 10 internal redirects..."

10. Andrea_r
    team pirate
    Posted 1 year ago #

    Disable all your plugins, even the mu-plugins. try again.

11. Mikee17
    Member
    Posted 1 year ago #

    We did that already...deactivated all plugins in /wp-content/plugins/ PLUS deactivated the mu-plugins by renaming the /wp-content/mu-plugins/ folder PLUS had the default 'twentyten' WP theme PLUS deactivated the multi-db plugin mentioned in my first post and had our site work on a single-db. Still get the same error: :(
    Request exceeded the limit of 100 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.,
    ** We had our host raise LimitInternalRecursion to 100 from 10.

12. Mikee17
    Member
    Posted 1 year ago #

    WOW! We are able to go to the 'Networks Admin' area now.
    Only change made is that we updated the Domain Mapping plugin from http://premium.wpmudev.org/project/domain-mapping to its latest version.
    The previous error(...internal redirects due to probable configuration...) is still been recorded in the error_log.

13. Andrea_r
    team pirate
    Posted 1 year ago #

    Have you started combing though logs on the server? Cuz if they cranked it to a hundred and it still tops out, soemthing is most definitely wrong.

    Did you go right from 2.9.1 to 3.1? Or did you go to 3.0 in the middle?

14. Mikee17
    Member
    Posted 1 year ago #

    Directly from WPMU-2.9.2 to WP-3.1

15. Andrea_r
    team pirate
    Posted 1 year ago #

    That's the kicker there. You should have done it incrementally to 3.0 and then to 3.1.

16. Mikee17
    Member
    Posted 1 year ago #

    Since its already done, what is the solution?

17. Andrea_r
    team pirate
    Posted 1 year ago #

    Got a backup?

    Go back to the original version. Manually upgrade to 3.0.

    http://wpmututorials.com/how-to/upgrading-to-3-0/

    then upgrade to 3.1.

18. Mikee17
    Member
    Posted 1 year ago #

    Ok, but now it looks like we have everything working fine except that it logs the error (i.e ...internal redirects due to probable configuration. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace) when we go to the Network Admin area(which was NOT working either earlier) at backend of our WP installation.

19. Mikee17
    Member
    Posted 1 year ago #

    Hi,

    Here is an update we did to our .htaccess ('---s---' & '---e---' is used only here to improve readability)...

    The below code:
    

    ---s---
    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule . - [L]
    ---e---

    is REPLACED with:
    

    ---s---
    RewriteCond %{ENV:REDIRECT_STATUS} 200
    RewriteRule .* - [L]
    ---e---

    The above updates seems to have solved our issue reported here, shall get back again with updates if any...

    Thanks & Regards

20. Ipstenu
    Half-Elf Support Rogue & Mod
    Posted 1 year ago #

    That doesn't look like Apache.... What kind of server are you on?

21. Mikee17
    Member
    Posted 1 year ago #

    Its Apache on a Linux box.

22. Ipstenu
    Half-Elf Support Rogue & Mod
    Posted 1 year ago #

    *After rereading my books...* Oh. So it is.

    You shouldn't need %{ENV:REDIRECT_STATUS} but if you do, it's a server config wacky.

23. Mikee17
    Member
    Posted 1 year ago #

    @Ipstenu
    We removed %{ENV:REDIRECT_STATUS and put back the orginal .htaccess file.

24. Mikee17
    Member
    Posted 1 year ago #

    We are researching the cause of the follwoing error:
    "Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace."

25. Ipstenu
    Half-Elf Support Rogue & Mod
    Posted 1 year ago #

    No, what I mean is that you shouldn't need to use that INSTEAD of
    

    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule . - [L]

    That YOUR server is requiring you to use this is what's weird.
    

    RewriteCond %{ENV:REDIRECT_STATUS} 200
    RewriteRule .* - [L]

26. Mikee17
    Member
    Posted 1 year ago #

    RewriteCond %{ENV:REDIRECT_STATUS} 200
    RewriteRule .* - [L]

    We REMOVED the above code and is now using the orginal that is below:

    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule . - [L]

    I.e. we switched back our changes to .htaccess as that did not solve the issue completely.

27. Ipstenu
    Half-Elf Support Rogue & Mod
    Posted 1 year ago #

    Right and now it's failing again, correct? So for your setup, it only worked with the ENV:REDIRECT_STATUS line?

    Which is weird, and that's all I was getting at. THAT was weird.

28. Mikee17
    Member
    Posted 1 year ago #

    Yes, we get the bellow error when we go to the Network Admin area:

    Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.

    Could be a nested folders issue like Andrea_r said.

29. Mikee17
    Member
    Posted 1 year ago #

    We get the above messages mainly when we go to the 'Network Admin' area ... looks like an .htaccess file with following code at /wp-admin/network/ solves the issue.

    RewriteEngine On
    
    RewriteRule index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule (.*)$ /wp-admin/$1 [L]

    Do you see any issue?

Topic Closed

This topic has been closed to new replies.