The MU forums have moved to WordPress.org

MaxRedirects error since upgrade to WPMU 1.2.1 (3 posts)

  1. jshare
    Member
    Posted 15 years ago #

    From the moment I upgraded to WPMU 1.2.1, my error_log started filling up with these couplets:

    [Tue Apr 17 23:28:34 2007] [error] [client xx.xx.xx.xx] mod_rewrite: maximum number of internal redirects reached. Assuming configuration error. Use 'RewriteOptions MaxRedirects' to increase the limit if neccessary., referer: http://jobmob.co.il/
    [Tue Apr 17 23:28:34 2007] [error] [client xx.xx.xx.xx] 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://jobmob.co.il/

    AFAGK, 'LogLevel debug' can only be used via httpd.conf which I do not have access to, but what does Google know :)

    Interestingly enough - these errors are not generating any 500 errors in the Apache log.

    On upgrade, I removed the 'www redirect' from my .htaccess file, just like it disappeared from htaccess.dist.

    I could try changing the MaxRedirects value but that's the easy way out.

    Any suggestions? Anyone else see this with 1.2.1?

  2. drmike
    Member
    Posted 15 years ago #

    You're not trying to run WPmu on an addon domain or anything, are you? It's in its own account all by itself, right?

  3. jshare
    Member
    Posted 15 years ago #

    Not exactly. I'm also running my WPMU 1.2.1 dev environment using a separate domain in that hosting account, but I don't dev often so >90% of the time the dev install is doing nothing. It's password-protected too.

    I've been using this arrangement for the past 6 months starting with 1.0. It's not ideal but it's the best compromise for my current needs.

About this Topic