My site is offline, reporting redirection errors, what to do?

When you access your WordPress site you may encounter a message that "the page is not redirecting correctly". This is the error known as "too many redirects". In this article, we show you how to correct it!

Understanding the error message


This error appears with different messages in each of the browsers. It may come with a warning of "too many redirects" or "this web page has a redirection loop", but the information is the same: there is some configuration on your site that is generating infinite redirections, preventing the user from accessing it.

In general, it is caused by incorrect or incompatible settings between plugins, which are added to the main files of the site, such as HTACCESS or WP-CONFIG. Despite our complicated, it is a simple error of correction!

Fixing the error: restoring the HTACCESS file


The .HTACCESS file is a server file, and is one of those responsible for informing browsers of the main site settings. For example, redirection rules and cache settings can be defined in this file. Because of this, some plug-ins can edit this file (and cause a mess). Therefore, what you need to do is restore the default .htaccess file.

To do this, you must first have the SFTP access credentials of your website. If you don't have those credentials yet, here we show you how to get them!

With SFTO access in hand, we will first save the current .htaccess file.

The file is in the site's root folder, so when you access the FTP, it will be inside the 'website' folder. Click on the folder and locate the file. Then add an '.old' to the .htaccess file name:

Then click on the folder "...", right click and 'Create a new file':

Give the name .htaccess and click on ‘ok’:

Right click on this new htaccess and click 'view / edit':

A notepad file will be opened and you will copy the standard WordPress htaccess file.

If your WordPress is unchanged, with only one instance, this is the default HTACCESS:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

If your WordPress is multi-site, HTACCESS is this:

# 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]
</IfModule>
# END WordPress

Click 'Save' and 'yes' on this screen:

In the box on the left, check if the transfer was successful:

And try loading the site again.

In most cases, this solves the problem! If the error still remains, please contact our support so that we can help you!