Forum Replies Created

Viewing 15 replies - 1 through 15 (of 16 total)
  • Thread Starter mikee17

    (@mikee17)

    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?

    Thread Starter mikee17

    (@mikee17)

    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.

    Thread Starter mikee17

    (@mikee17)

    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.

    Thread Starter mikee17

    (@mikee17)

    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.”

    Thread Starter mikee17

    (@mikee17)

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

    Thread Starter mikee17

    (@mikee17)

    Its Apache on a Linux box.

    Thread Starter mikee17

    (@mikee17)

    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

    Thread Starter mikee17

    (@mikee17)

    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.

    Thread Starter mikee17

    (@mikee17)

    Since its already done, what is the solution?

    Thread Starter mikee17

    (@mikee17)

    Directly from WPMU-2.9.2 to WP-3.1

    Thread Starter mikee17

    (@mikee17)

    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.

    Thread Starter mikee17

    (@mikee17)

    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.

    Thread Starter mikee17

    (@mikee17)

    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…”

    Thread Starter mikee17

    (@mikee17)

    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

    Thread Starter mikee17

    (@mikee17)

    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.”

Viewing 15 replies - 1 through 15 (of 16 total)