• I created a multisite on WordPress today using subdirectories because evidently 1&1 can’t handle multisites using subdomains – go figure, but I’m stuck with 1&1.

    The original WordPress site works fine as it did before. So I created a new site and now I’m caught in a redirect loop with the WP-Login screen. You can put the URL into a browser and it’ll show you a text version of the initial WordPress blog page without any formatting – so something’s wrong there too. But it’s the looping that’s killing me.

    I have spent almost 9 hours trying every .htaccess and wp-config work around I can find on the internet and none of them work.

    I’ve tried adding this code to wp-config:

    define(‘ADMIN_COOKIE_PATH’, ‘/’);
    define(‘COOKIE_DOMAIN’, ”);
    define(‘COOKIEPATH’, ”);
    define(‘SITECOOKIEPATH’, ”);

    I’ve tried this in my wp-config:

    if(isset($_SERVER[‘HTTP_X_FORWARDED_FOR’])) {
    $list = explode(‘,’,$_SERVER[‘HTTP_X_FORWARDED_FOR’]);
    $_SERVER[‘REMOTE_ADDR’] = $list[0];
    }
    $_SERVER[ ‘SERVER_ADDR’ ] = DOMAIN_CURRENT_SITE;
    $_SERVER[ ‘REMOTE_ADDR’ ] = DOMAIN_CURRENT_SITE;
    $_SERVER[ ‘HTTP_HOST’ ] = DOMAIN_CURRENT_SITE;

    and this:

    define( ‘WP_ALLOW_MULTISITE’, true );
    define(‘MULTISITE’, true);
    define(‘SUBDOMAIN_INSTALL’, false); //or true, depends on your chosen way
    define(‘DOMAIN_CURRENT_SITE’, ‘localhost’);
    define(‘PATH_CURRENT_SITE’, ‘/wp/’);
    define(‘SITE_ID_CURRENT_SITE’, 1);
    define(‘BLOG_ID_CURRENT_SITE’, 1);

    There have been more, but I’ve lost track. And I’ve tweaked and edited the .htaccess file in a dozen ways. I’ve also tried adding these:

    define(‘WP_HOME’,’http://example.com’);
    define(‘WP_SITEURL’,’http://example.com’);

    I’ve deactivated all my plugins which made no difference as well. I’ve cleared cookies, caches, histories, you name it I’ve cleared it. I also changed the permalink settings to plain and checked for capital letters in URLs. I just cannot get it to work. I don’t know if it’s the .htaccess and wp-config files or some setting at 1&1. Anything anyone can suggest would be greatly appreciated.

    The .htaccess file is the standard one generated by the WordPress Network Setup in the dashboard:

    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]

    And my wp-config file is also straight from the Network Setup:

    define(‘MULTISITE’, true);
    define(‘SUBDOMAIN_INSTALL’, false);
    define(‘DOMAIN_CURRENT_SITE’, ‘southpacificwwiimuseum.com’);
    define(‘PATH_CURRENT_SITE’, ‘/’);
    define(‘SITE_ID_CURRENT_SITE’, 1);
    define(‘BLOG_ID_CURRENT_SITE’, 1);

Viewing 2 replies - 1 through 2 (of 2 total)
  • This may not be any help but I am suffering with the exact same problem and think I have tracked it down to a Cookie: “_wp_session”.
    If I delete this cookie then everything springs back into life… until the next time it happens …and so I delete the cookie and all is well again… until… you get the picture I’m sure!
    I have also spent many hours over the last three days trying to figure this out and made all the changes mentioned above but still no luck.
    If anyone can shed any light on this, I/we would be eternally grateful!

    So, following a fairly lengthy “Chat” session, it turned out there had been some sort of “update” that changed the mod_security settings on my VPS. Unfortunately, despite asking three times what the changes were and what was done to correct them, the “Chat Operator” declined to provide an answer.
    However, the site is now back up and running as it should be (so far anyway…)
    I don’t know if this also your problem but I hope it helps.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Another Looped WP-Login Screen’ is closed to new replies.