Redirect loop to wp-admin or wp-login.php

If you are using Cloudflare, you can try adding this to the TOP of the wp-config.php file:

define('WP_SITEURL', 'https://www.example.com');
define('WP_HOME', 'https://www.example.com');
define('FORCE_SSL_ADMIN', true);
define('FORCE_SSL_LOGIN', true);
if(isset($_SERVER['HTTP_CF_VISITOR']) && strpos($_SERVER['HTTP_CF_VISITOR'], 'https')){
  $_SERVER['HTTPS']='on';
}

      

        
        
        
      

    

It is important that you add it to the beginning of your wp-config.php file, otherwise you will receive the error "Sorry, you cannot access this page."

Courtesy of: https://www.meltajon.com/dev/wordpress-wp-admin-redirect-loop-with-cloudflare-ssl.

with nginx config I originally only had this line and had the same redirect problem:

location / {
    try_files   $uri /index.php$is_args$args;
}

      

        
        
        
      

    

after adding this everything was fine:

location /wp-admin/ {
    index index.php;
    try_files $uri $uri/ /index.php$args;
}

      

        
        
        
      

    

I was getting DoS pages when trying to publish to my WP site. I found advice that changing the permissions in the function.php file to 600 might fix the problem and also add a script snippet to that file. This is the WP help page. I was able to get to the post in different ways. There is still a DoS when I try to open the editor.

I just needed to clear my redirects. Since I couldn't access Admin, I added this to the top of my functions.php file:

flush_rewrite_rules(); exit;

Saved and updated my place. Then remove the code from your functions.php file and update it again. This did it for me.

I also think it might be a good measure to keep your permalinks.

PS. I think the main problem was coming from topic-my-login as it was being redirected to / login.

To delete lines

define('DOMAIN_CURRENT_SITE', 'www.sitename.de');

define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);

      

        
        
        
      

    

of wp-config.php

must do the job.

These lines are not needed for multi

In the sites-enabled folder, you will need to edit the configuration for your site and add multisite redirect rules. For Ubuntu 14.04, you should be able to find the path under / etc / nginx / sites -available

Add the following block to your server block and you can avoid an endless redirection loop.

#Rewrite multisite '.../wp-.*' and '.../*.php'.
if (!-e $request_filename) {
    rewrite /wp-admin$ $scheme://$host$uri/ permanent;
    rewrite ^/[_0-9a-zA-Z-]+(/wp-.*) $1 last;
    rewrite ^/[_0-9a-zA-Z-]+(/.*\.php)$ $1 last;
}

      

        
        
        
      

    

I had a similar problem, in my case it was due to a db restore script that was generated with WP Migrate DB. The script had merge tags like "## DEV URL ##" which I needed to fix before running the script in mysql and pointing wp-config.php to the correct database.

In my case, it was an Apache issue DirectoryIndex

. Access wp-admin

was from wp-admin/index.php

, but not from, wp-admin

and was shown ERR_TOO_MANY_REDIRECTS

.

It looks like Apache DirectoryIndex

may not be installed "correctly". Try dumping this at the top of the file .htaccess

:

DirectoryIndex index.php

      

        
        
        
      

    

See the full answer here. Can't access admin panel using wp-admin without /index.php after it

My problem was that the hard drive was full. Trying to login to wordpress control panel redirected me to wp-login.php. I was able to log in again as soon as I deleted some files.

If you have nginx then check your index configuration as well. As for me, I had a problem: I installed the following:

server {
    server_name _;
    root /var/www/html;
    index /index.php;
}

      

        
        
        
      

    

So, as you can see, I have set index.php with a trailing slash, which means that all rewrite requests will be sent to index.php in the documentro. This is not correct for WP because the wp-admin directory has its own index.php

The above answers came pretty close to me. In our particular case, someone at some point added some rules to the htaccess file at the root of the site and in the admin folder to block traffic from everywhere except for some white IP addresses (when trying to access wp-admin).

Example:

<Files wp-login.php>
   order deny,allow
   Deny from all

   # Allow from this IP address
  allow from 123.45.67.89
</Files>

      

        
        
        
      

    

Whitelisting our IP address in both files fixed the issue.