network admin getting redirect loop

I think it’s … well, I’m not sure.

This keeps coming up, but not for everyone, and my best GUESS is that it’s a combination of server setup, DNS, and WordPress.

See, my DNS is set that https://www.domain.com and domain.com are separate entries, but both point to the same name server. Ditto the vhosts in my httpd.conf file. In WP, I installed everything to be domain.com (cause I subscribe to the ‘shorter is better’ school of thought). And I know that once I moved to 3.0, I no longer needed my .htaccess tweak of

RewriteCond %{HTTP_HOST} ^www\.domain\.tld$ [NC]
RewriteRule ^(.*)$ https://domain.tld/$1 [R=301,L]

So I presume that WordPress parses this better, not just because of MultiSite (I get the same results on a non-MultiSite WP install), but because of a change in the 3.0 base.

My gut feeling is that when all those pieces AREN’T aligned correctly, and somewhere in the mix, be it DNS or vhost, that your server things that one or the other should take precedence , WP has a bit of a hissy fit.

Sadly that doesn’t answer it for me I don’t think, as it makes zero difference whether the www is present or not in the wp-config. I still have the exact same redirect loop experience.

I’ll check the server setup tomorrow though to ensure everything is consistent.

Same problem here … I get the ‘redirect loop’ error and none of the above suggestions have helped so far …

Ok, it seems I have found the solution! At least for my problem.

In the table wp_blogs the domains for my networked WP sites were ‘mydomain.com’ in each case. I changed all of them into ‘www.mydomain.com’ and now the network part of the admin interface is accessible again!

And the WP sites seem to still work normally too ??

Does anyone know though why this suddenly became a problem after the upgrade from 3.1.0 > 3.1.1 ?

No joy for me, adding the www in that table just gives me a redirect loop for the entire site rather than just the network admin section.

rob:

Hmm … what value do you have in your wp-config.php file then at this line:

define(‘DOMAIN_CURRENT_SITE’, ‘???’);

I had ‘www.mydomain.com’ there but only ‘mydomain.com’ in the wp_blogs table, maybe that way the problem in my case? Since everything worked again once I’ve added a ‘www.’ there.

Also, I’m not working with subdomains but with subfolders. Maybe that’s why the domain change didn’t mess my whole interface up like in your case? Are you using subdomains?

it’s ‘ukintranet.eu.companyname.net’ since I’m running WP as an internal site rather than a website.

If I add www. here, then there is no difference. If I add it in the wp_blogs table then it loops the whole site.

and yes, I am using subdomains, so that may be the key difference.

robpannell, in your case you don’t need the www, obviously ??

I’m using subdomains as well, but you’re using … nested subdomains (that is you get site2.ukintranet.eu.company.net, right?)

That said, this:
define('DOMAIN_CURRENT_SITE', 'ukintranet.eu.company.net' );

and:
$base = '/subdir/';

Are a recipe for things being bizarre. WordPress doesn’t like running a network out of a subfolder, and especially not subdomains!

hmm, thanks. It looks like I’m gonna have to do a couple of fresh standalones & transfer everything across. ouch.

I’ve got this same issue. I can access the site (although comments won’t load), get to the login page. However, if I try to login, it just loops straight back to the login box again.

I’m running WordPress 3.1 Network on IIS7, SQL Server 2008 w/ sub-domains.

I have enabled network, and added the following to:

web.config:

<rewrite>
			  <rules>
				  <rule name="WordPress Rule 1" stopProcessing="true">
					  <match url="^index\.php$" ignoreCase="false" />
					  <action type="None" />
				  </rule>
				  <rule name="WordPress Rule 2" stopProcessing="true">
					  <match url="^files/(.+)" ignoreCase="false" />
					  <action type="Rewrite" url="wp-includes/ms-files.php?file={R:0}" appendQueryString="false" />
				  </rule>
				  <rule name="WordPress Rule 3" stopProcessing="true">
					  <match url="^" ignoreCase="false" />
					  <conditions logicalGrouping="MatchAny">
						  <add input="{REQUEST_FILENAME}" matchType="IsFile" ignoreCase="false" />
						  <add input="{REQUEST_FILENAME}" matchType="IsDirectory" ignoreCase="false" />
					  </conditions>
					  <action type="None" />
				  </rule>
				  <rule name="WordPress Rule 4" stopProcessing="true">
					  <match url="." ignoreCase="false" />
					  <action type="Rewrite" url="index.php" />
				  </rule>
			  </rules>
		  </rewrite>

wp-config:

define( 'MULTISITE', true );
define( 'SUBDOMAIN_INSTALL', true );
$base = '/';
define( 'DOMAIN_CURRENT_SITE', 'svr-web' );
define( 'PATH_CURRENT_SITE', '/' );
define( 'SITE_ID_CURRENT_SITE', 1 );
define( 'BLOG_ID_CURRENT_SITE', 1 );

Any ideas?

I’m having the same problem as robpannell – but only after I changed the site from non-www to www. The site is up, the admin works but the network admin goes into the infinite loop. If I remove the DOMAIN_CURRENT_SITE, then the network admin works but then none of the site links work(but the site is visible). I have two databases I’m flipping between to figure this out -one with all the links set to non-www and one with all www. I’m guessing there’s a mismatch somewhere between non-www and www but don’t get where when it only affects network admin?

homeruntaz – this post is both 2 months old AND flagged as resolved, so you’re better off making a new topic in these situations.

Go through your DB and look for any missmatches with your domain.

Found the solution!!!! I changed the url in the blogs table(wp_blogs if you didn’t modify it) -it’s the only row in the table and once I added the www to it- the site, admin and network admin works!

Actually in the end, I commented out lines 18 & 19 of wp-admin/network/admin.php

That did the trick for me.

robpannell – I cannot, in good conscience, suggest ANYONE edit the core files. Ever.