225 points
Community rank #221
mikee17
ExpertJust Getting Started
MemberLikes (0)
Hello,
We just 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 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:
Its still working and has not shown any messages yet, can see 'Waiting for http://{our-site}/wp-admin/network/upgrade.php' on the status bar. (I'll post update if I get any results)
FF:
Not tried yet as IE is still working on as I write this.
Kindly advice, could it be an upgrade issue or could the delay be because we have several sites and is it worth waiting for IE to show results?
225 pointsCommunity rank #221ExpertJust Getting Started
Member
(joined February 2009)
Likes (0)
Hello,
We have no progress on this yet...
All user login and admin login works fine and we can go to the backend of all sites.
Its just that we cant go to Networks Admin and so cant manage anything network related... : (
Hmm, other than a Suhosin issue, a plugin conflict or clearing your browsers cache, I can't think of anything else that would cause it to redirect like that. Hopefully, someone else will come along to shed some light on the matter.
225 pointsCommunity rank #221ExpertJust Getting Started
Member
(joined February 2009)
Likes (0)
Thank you joshmac, we hope so too.
Noticed that 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
225 pointsCommunity rank #221ExpertJust Getting Started
Member
(joined February 2009)
Likes (0)
Update:
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 and had our site work on a single-db on our test site. 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.
225 pointsCommunity rank #221ExpertJust Getting Started
Member
(joined February 2009)
Likes (0)
WOW! We are able to go to the 'Networks Admin' area now.
Only change made is that we updated the Domain Mapping plugin from premium to its latest version 3.0.4
The previous error(...internal redirects due to probable configuration...) is still been recorded in the error_log.
2.
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.
PS: The 2nd one above is the error we mentioned in previous post here. Also, now we have upgraded from 3.1 to 3.1.2
11696 pointsCommunity rank #2Supreme DeityTrue DEVianLifetime member
Member
(joined April 2009)
Likes (0)
Hiya mikee17,
Thanks for reporting back. Those errors are both outside of my knowledge - I'm going to ask a couple of the devs to come by and see what they make of this.
Do you have mod_security enabled/configured? Any rules relating to this in your .htaccess? If so, please post those details here as well.
11696 pointsCommunity rank #2Supreme DeityTrue DEVianLifetime member
Member
(joined April 2009)
Likes (0)
Hiya mikee17,
Seeing the rules, you've got a couple there that you shouldn't need anymore. Specifically, the two RewriteRules pertaining to blogs (I see this one is commented out) and the avatar line as well.
The thing above that makes me nervous is the "WEB_ATTACK/XSS" critical severity. Aaron, Barry, any ideas?
225 pointsCommunity rank #221ExpertJust Getting Started
Member
(joined February 2009)
Likes (0)
Hey masonjames,
No feedback from Aaron, Barry yet! Hope they will walk through this way as well...
Another ModSecurity error we get is:
ModSecurity: Access denied with code 505 (phase 2). Match of "rx ^HTTP/(0\\\\.9|1\\\\.[01])$" against "REQUEST_PROTOCOL" required. [file "/etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf"] [line "83"] [id "960034"] [msg "HTTP protocol version is not allowed by policy"] [severity "CRITICAL"] [tag "POLICY/PROTOCOL_NOT_ALLOWED"] [hostname "oursubdomain.ourwordpress.com"] [uri "/2011/02/02/how-can-i-prevent-panic-attacks"] [unique_id "Tcjtb38AAAEAAGv2EggAAAAR"]
--
While we still have:
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.
Also, ADDED the following along with the other to <IfModule mod_security.c> ... </IfModule>:
---s---
<Files admin-ajax.php>
SecFilterInheritance Off
</Files>
---e---
The above TWO updates seems to have solved our issues reported here, shall get back again with updates if any...
225 pointsCommunity rank #221ExpertJust Getting Started
Member
(joined February 2009)
Likes (0)
We removed %{ENV:REDIRECT_STATUS and put back the orginal .htaccess file.
We are researching the cause of the following 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."
8421 pointsCommunity rank #4Supreme DeityWPMU DEV StaffLifetime member
Lead Developer
(joined May 2009)
Likes (0)
The modsecurity errors are just notices that modsecurity has blocked a possible attack based on /etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf configuration. No big deal, totally normal.
I even get the redirect errors in my logs, they're very common. It's real hard to trace what causes those. I don't know why they don't show the generating script.
225 pointsCommunity rank #221ExpertJust Getting Started
Member
(joined February 2009)
Likes (0)
So those ModSecurity errors are not to worry about?
Are you getting the same kind of redirect errors in your logs too? We are now at the assumption that it could be related to some missing files(i.e 'File does not exist' errors)... thoughts?
225 pointsCommunity rank #221ExpertJust Getting Started
Member
(joined February 2009)
Likes (0)
Ok, we get those 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.
Responses (22)
Member (joined February 2009) Likes (0)
Hello,
We have no progress on this yet...
All user login and admin login works fine and we can go to the backend of all sites.
Its just that we cant go to Networks Admin and so cant manage anything network related... : (
Could this be a Multi-DB related issue ?
Anyone kindly advice a solution.
Thanks & Regards
Member (joined February 2009) Likes (0)
Hello,
Did not find a solution yet for the issue we have mentioned here, by any chance would it be related to our host rendering that nested admin folder ?
Thanks & Regards
Member (joined April 2009) Likes (0)
@mikee17, I usually see this issue when multidb is not setup correctly. Were you using multidb before upgrading to WP-3.1.x?
Member (joined February 2009) Likes (0)
Yes, multi-db was working fine with WPMU-2.9.2 and looks like it still is as our sites are working fine.
Member (joined April 2009) Likes (0)
Hmm, other than a Suhosin issue, a plugin conflict or clearing your browsers cache, I can't think of anything else that would cause it to redirect like that. Hopefully, someone else will come along to shed some light on the matter.
Member (joined February 2009) Likes (0)
Thank you joshmac, we hope so too.
Noticed that 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
Member (joined February 2009) Likes (0)
Update:
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 and had our site work on a single-db on our test site. 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.
Member (joined February 2009) Likes (0)
WOW! We are able to go to the 'Networks Admin' area now.
Only change made is that we updated the Domain Mapping plugin from premium to its latest version 3.0.4
The previous error(...internal redirects due to probable configuration...) is still been recorded in the error_log.
Member (joined April 2009) Likes (0)
Hiya,
Sorry for the slower response on this one at the front. Going from 2.9.2 to 3.1 is a scary thing :-/
I've not attempted that myself even! Glad to hear you're able to get into the admin again :)
If you're still getting an error message, can you copy it exactly here so we can take a look?
Let us know how you're progressing and we'll assist any way we can.
Member (joined February 2009) Likes (0)
Hi masonjames,
We have TWO errors(logged to our error_log file) that worry us and they are as follows:
1.
ModSecurity: Warning. Pattern match "(?:\\b(?:(?:type\\b\\W*?\\b(?:text\\b\\W*?\\b(?:j(?:ava)?|ecma|vb)|application\\b\\W*?\\bx-(?:java|vb))script|c(?:opyparentfolder|reatetextrange)|get(?:special|parent)folder|iframe\\b.{0,100}?\\bsrc)\\b|on(?:(?:mo(?:use(?:o(?:ver|ut)|down|move|up)|ve)|key(?:press|d ..." at ARGS:content. [file "/etc/httpd/modsecurity.d/modsecurity_crs_40_generic_attacks.conf"] [line "102"] [id "950004"] [msg "Cross-site Scripting (XSS) Attack"] [data "src=\\x22http:"] [severity "CRITICAL"] [tag "WEB_ATTACK/XSS"] [hostname "oursubdomain.ourwordpress.com"] [uri "/wp-admin/admin-ajax.php"] [unique_id "TcP4q38AAAEAAEY8KOcAAAAw"]
2.
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.
PS: The 2nd one above is the error we mentioned in previous post here. Also, now we have upgraded from 3.1 to 3.1.2
Member (joined April 2009) Likes (0)
Hiya mikee17,
Thanks for reporting back. Those errors are both outside of my knowledge - I'm going to ask a couple of the devs to come by and see what they make of this.
Do you have mod_security enabled/configured? Any rules relating to this in your .htaccess? If so, please post those details here as well.
Again, I'll ask a few devs to chime in.
Thanks!
Member (joined February 2009) Likes (0)
Hey masonjames,
Thanks again!
I have attached the screenshot of our .htaccess file that has the 'IfModule mod_security.c' stuff.
Thanks & Regards
Member (joined April 2009) Likes (0)
Hiya mikee17,
Seeing the rules, you've got a couple there that you shouldn't need anymore. Specifically, the two RewriteRules pertaining to blogs (I see this one is commented out) and the avatar line as well.
The thing above that makes me nervous is the "WEB_ATTACK/XSS" critical severity. Aaron, Barry, any ideas?
Thanks!
Member (joined February 2009) Likes (0)
Hey masonjames,
No feedback from Aaron, Barry yet! Hope they will walk through this way as well...
Another ModSecurity error we get is:
ModSecurity: Access denied with code 505 (phase 2). Match of "rx ^HTTP/(0\\\\.9|1\\\\.[01])$" against "REQUEST_PROTOCOL" required. [file "/etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf"] [line "83"] [id "960034"] [msg "HTTP protocol version is not allowed by policy"] [severity "CRITICAL"] [tag "POLICY/PROTOCOL_NOT_ALLOWED"] [hostname "oursubdomain.ourwordpress.com"] [uri "/2011/02/02/how-can-i-prevent-panic-attacks"] [unique_id "Tcjtb38AAAEAAGv2EggAAAAR"]
--
While we still have:
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.
: (
Thanks & Regards
Member (joined February 2009) Likes (0)
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---
Also, ADDED the following along with the other to <IfModule mod_security.c> ... </IfModule>:
---s---
<Files admin-ajax.php>
SecFilterInheritance Off
</Files>
---e---
The above TWO updates seems to have solved our issues reported here, shall get back again with updates if any...
Thanks & Regards
Member (joined February 2009) Likes (0)
We removed %{ENV:REDIRECT_STATUS and put back the orginal .htaccess file.
We are researching the cause of the following 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."
Lead Developer (joined May 2009) Likes (0)
The modsecurity errors are just notices that modsecurity has blocked a possible attack based on /etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf configuration. No big deal, totally normal.
I even get the redirect errors in my logs, they're very common. It's real hard to trace what causes those. I don't know why they don't show the generating script.
Member (joined February 2009) Likes (0)
So those ModSecurity errors are not to worry about?
Are you getting the same kind of redirect errors in your logs too? We are now at the assumption that it could be related to some missing files(i.e 'File does not exist' errors)... thoughts?
Lead Developer (joined May 2009) Likes (0)
correct.
I do get those errors fairly commonly.
Member (joined February 2009) Likes (0)
Could this be a nested folders issue as mentioned by 'Andrea_r' at http://wordpress.org/support/topic/network-update-under-wp-31?replies=17 (i.e. I've been finding in some threads, certain hosts don't like rendering that nested admin folder.) ?
Lead Developer (joined May 2009) Likes (0)
Nah
Member (joined February 2009) Likes (0)
Ok, we get those 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.
Do you see any issue?
Become a member