Redirect Errors Related to Multisite Wordpress/BuddyPress/bbPress SIte

We are getting the following errors:

[Thu Feb 25 06:52:02.044062 2016] [core:error] [pid 7352] [client] AH00124: 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.
[Thu Feb 25 06:57:09.026897 2016] [core:error] [pid 18802] [client] AH00124: 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.

We are hosted on wp-engine and the history of the site is about 2 months ago we "moved" the site to the default root of www, so, where prior we were not using. Also we implemented SSL. These redirect loops have been happening for a while, but not sure if back as far as this change.

The settings for www in wordpress are and my developer thought there might be a conflicting domain setting so he asked wp-engine and they suggested to remove the www as they said this was causing the errors and also suggested to comment out the line in the wp-config:

//define('DOMAIN_CURRENT_SITE', '');

After that the following change was made so www was removed.

define('PWP_DOMAIN_CONFIG', '' );

This actually stopped the errors interestingly enough, but we haven’t changed the site_url to from the www.

There is a redirect set in wpengine panel under domains from to which seems to be working fine now.

My concern is that wpengine suggested me to edit the domain under domains in wpengine to remove the www, but this was a huge change, one I even considered by posting the question on this site. To move it back is a really big deal and it seems like this has to be some other configuration issue.

So now the website has the default url set to and a redirect set in wpengine to make to and with the changes made the errors are actually gone.

The concern is the existing configuration seems like a bad practice, even though errors are gone. And the developer that moved this to www is highly experience, so it isn't as likely he misconfigured the settings, but of course possible.

So where I am now is I worked with my developer to document this and see if anyone can point out what we are missing. I have a feeling it is easy, but this isn't as much my area of expertise. My developer will be able to help me respond to any questions though if necessary.


  • Predrag Dubajic
    • Support

    Hey David,

    Hope you're doing well today :slight_smile:

    With WP network installation it is recommended to use non www address to avoid any issues with subsite domains.

    Can you tell me if you have any additional rules in your .htaccess file and have you tried using default .htaccess rules for your type of WP installation?
    You can find those rules below and see if the redirects are still happening after that:

    Best regards,

  • David
    • The Incredible Code Injector

    Hello Predrag,

    Thank you for your reply. I am writing on behalf of David. I am his developer. We only have certain rules for s2members downloads in htaccess and the other code is the default code. Wpengine support has helped us earlier by checking the htaccess code. But i will paste the code here again.

    # BEGIN s2Member GZIP exclusions
    <IfModule rewrite_module>
    	RewriteEngine On
    	RewriteBase /
    	RewriteCond %{QUERY_STRING} (^|\?|&)s2member_file_download\=.+ [OR]
    	RewriteCond %{QUERY_STRING} (^|\?|&)no-gzip\=1
    	RewriteRule .* - [E=no-gzip:1]
    # END s2Member GZIP exclusions
    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    # add a trailing slash to /wp-admin
    RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
    RewriteCond %{REQUEST_FILENAME} -f [OR]
    RewriteCond %{REQUEST_FILENAME} -d
    RewriteRule ^ - [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
    RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
    RewriteRule . index.php [L]
    # END WordPress

    As for sub domains. We are not planning to have any subdomains. With the change in

    define('PWP_DOMAIN_CONFIG', '' );

    and removing www seems to have solved the problem. We wanted to keep www. Will that be a issue ? or a concern ?


  • Predrag Dubajic
    • Support

    Hi David,

    Using www in multisite is generally a bad practice and can cause more issues than it's worth, and setting everything up to work with www can be complicated and is something that your host should actually help you with, if it can be done on that specific server setup.

    Best regards,

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.