{"id":2433,"date":"2021-07-08T12:41:42","date_gmt":"2021-07-08T09:41:42","guid":{"rendered":"https:\/\/www.scalahosting.com\/kb\/?p=2433"},"modified":"2022-09-01T11:44:46","modified_gmt":"2022-09-01T08:44:46","slug":"why-does-my-redirection-show-an-error","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/kb\/why-does-my-redirection-show-an-error\/","title":{"rendered":"Why does my redirection show an error?"},"content":{"rendered":"\n

URL redirections<\/span> ensure you don\u2019t lose traffic or potential sales<\/b> due to a moved or deleted page.<\/span><\/p>\n\n\n\n

It lets you forward your web visitors to a location<\/span> after moving or deleting a page<\/b> by automatically taking them to the new location while trying to reach the old one.<\/span><\/p>\n\n\n\n

In addition, you could<\/span> use it to force <\/b>all visitors<\/b> to connect securely to your website via HTTPS,<\/b> save your organic ranking or fix www and non-www duplicate concerns. <\/span><\/p>\n\n\n\n

Redirection loops, incompatible WordPress plugins, browser cookies, and others could cause a redirection error, like <\/span>ERR_TOO_MANY_REDIRECTS<\/b>.<\/span><\/p>\n\n\n\n

Let\u2019s examine what the error means, the causes, and how to fix it.<\/span><\/p>\n\n\n\n

Understanding Error \u201cToo Many Redirects\u201d<\/b><\/h2>\n\n\n\n

Too Many <\/span>Redirects<\/b><\/a> is probably the most widely seen redirection error.<\/span><\/p>\n\n\n\n

It occurs when the browser<\/span> fails to establish a connection between the old location and the destination page in a redirect.<\/b><\/p>\n\n\n\n

The error indicates that <\/span>the website gets redirected too often<\/b>, creating a long direction chain or redirecting in an infinite loop\u2014getting redirected to a new location that redirects back to the old URL. <\/span><\/p>\n\n\n\n

Now, let’s examine <\/span>what causes the redirection error and how to resolve them.<\/b><\/p>\n\n\n\n

Causes of Redirection Error and How to Fix Them<\/b><\/h2>\n\n\n\n

Here are some of the <\/span>common causes of the redirection and the quick fixes.<\/b><\/p>\n\n\n\n

Cache and Cookies<\/b><\/h3>\n\n\n\n

Cache and browser cookies are <\/span>often the first suspects when a website experiences a redirection error.<\/b> So consider <\/span>clearing your browser cookies<\/b><\/a> and cache, and luckily, you could get this done in a few minutes.<\/span><\/p>\n\n\n\n

If your <\/span>WordPress website uses any site caching plugin<\/b>, log in to your backend and clear the site cache.<\/span><\/p>\n\n\n\n

If this step is unable to resolve the error, then proceed with step two.<\/span><\/p>\n\n\n\n

URL Settings<\/b><\/h3>\n\n\n\n

Failing to configure your URL settings correctly <\/span>can cause a redirect loop.<\/b><\/p>\n\n\n\n

It\u2019s essential your <\/span>WordPress URL and Site URL<\/b> match by using the same URL for the two. <\/span><\/p>\n\n\n\n

For instance, if your WordPress URL is <\/span>https:\/\/www.domain.com<\/b>, then the Site URL should have the URL as well\u2014setting the Site URL to<\/span> https:\/\/domain.com<\/b> will cause a redirect loop.<\/span><\/p>\n\n\n\n

You could<\/span> troubleshoot your URL settings <\/b>onto your WordPress backend, locate <\/span>Settings<\/b> and open the General tab.<\/span><\/p>\n\n\n\n

But if you are <\/span>unable to log in to your backend,<\/b> follow these steps to resolve it <\/span>via SPanel<\/b><\/a>\u2014<\/b>Scala Hosting all-in-one control panel.<\/span><\/p>\n\n\n\n

Step 1: Log into SPanel’s User Interface.
<\/b><\/h4>\n\n\n\n

The default login URL is https:\/\/yourdomain.com\/spanel\/<\/strong><\/em> (don’t forget to replace yourdomain.com <\/em>with your actual domain).<\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

Step 2: Open File Manager<\/b><\/h4>\n\n\n\n

Go to the control panel\u2019s <\/span>FILES<\/b> section and click <\/span>File manager <\/b>to open the home directory.<\/span><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

Locate the webroot directory of the domain with the redirection error<\/span>. <\/b>Please scroll to the <\/span>public_html<\/b> folder if it\u2019s the root domain.<\/span><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

Step 3: Open the Configuration File<\/b><\/h4>\n\n\n\n

In your webroot directory, locate the <\/span>wp-config.php<\/b> file, right-click the file to reveal a menu, then select <\/span>Edit<\/b>.<\/span><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

Scroll through the file and<\/span> ensure the addresses of <\/b>WP_HOME<\/b> and <\/b>WP_SITEURL<\/b> match.<\/b><\/p>\n\n\n\n

But if you don\u2019t find the <\/span>WP_HOME<\/span> and <\/span>WP_SITEURL<\/span> lines on your configuration file, then follow this step to change the address via your database using the phpMyAdmin tool.<\/span><\/p>\n\n\n\n

Step 1: Log in to phpMyAdmin<\/b><\/h4>\n\n\n\n

Please log in to your control panel, scroll to the <\/span>DATABASES<\/b> section and click <\/span>phpMyAdmin<\/b> to access your database. <\/span><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

phpMyAdmin is an intuitive web interface that allows users to <\/span>manage their MySQL databases.<\/b><\/p>\n\n\n\n

Step 2: Access Your Database<\/b><\/h4>\n\n\n\n

On the phpMyAdmin dashboard, <\/span>locate your website\u2019s database and click to open it.<\/b><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

You could verify the database linked to your website on your <\/span>wp_config.php<\/b> file. The database name is on the <\/span>DB_NAME<\/b> line under <\/span>MySQL settings.<\/b><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

Step 3: Open Your Database WP_Options Table<\/b><\/h4>\n\n\n\n

When you <\/span>open your database<\/b>, please scroll through the tables to find the <\/span>wp_options<\/b> table and double click to open it.<\/span><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

Redefine the addresses if the option-values of the <\/span>siteurl<\/b> and <\/span>home<\/b> don\u2019t match.<\/span><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

If there\u2019s no URL mismatch or the step doesn\u2019t resolve the error, <\/span>then proceed to troubleshoot your .htaccess file.<\/b><\/p>\n\n\n\n

The .htaccess File<\/b><\/h3>\n\n\n\n

The <\/span>.htaccess file<\/b><\/a> is a <\/span>server configuration file that lets users configure their server settings, including web redirects. <\/b>As a server configuration file, any error on the file or corrupted .htaccess file could affect your website.<\/span><\/p>\n\n\n\n

You could <\/span>find if the file is responsible for the error<\/b> by disabling it and then visiting the website to check if it\u2019s working fine. <\/span><\/p>\n\n\n\n

Follow these steps to get it done.<\/span><\/p>\n\n\n\n

Step 1: Locate Your .htaccess File<\/b><\/h4>\n\n\n\n

Log in to your control panel and click <\/span>File manager<\/b> to access your home directory. Next, please open your domain\u2019s web root directory and locate the <\/span>.htaccess<\/b> file.<\/span><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

Step 2: Disable the .htaccess File<\/b><\/h4>\n\n\n\n

You can <\/span>disable your .htaccess file<\/b> by renaming it to <\/span>.htaccess.old<\/b>. To do this, right-click the file and select Rename.<\/span><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

Now, visit the website to check if it\u2019s working fine. <\/span><\/p>\n\n\n\n

If it doesn\u2019t, <\/span>then the .htaccess file is not the problem<\/b>; reactivate it by renaming the file to its original name. But if disabling the file resolves the issue, then it means <\/span>the file was corrupt.<\/b><\/p>\n\n\n\n

Kindly delete it and generate a new file.<\/span><\/p>\n\n\n\n

Step 3: Deleting and Generating a New .htaccess File<\/b><\/h3>\n\n\n\n

To delete the file, right-click it and select <\/span>Delete<\/b> to remove it permanently from the file manager.<\/span><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

And to generate a new fresh one, sign in to your WordPress backend, click <\/span>Settings<\/b> > <\/span>Permalinks<\/b> > <\/span>Save Changes<\/b> leaving the text boxes blank.<\/span><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

If you wish to create the file <\/span>manually via the file manager<\/b>, open your web root folder, click the <\/span>New File\/Folders<\/b> icon and select <\/span>New File.<\/b> <\/span><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

Name the new file <\/span>.htaccess<\/b> and save it. <\/span><\/p>\n\n\n\n

WordPress Plugins<\/b><\/h3>\n\n\n\n

If the other steps fail to resolve the error,<\/span> then an incompatible plugin might be the cause, and here\u2019s how to troubleshoot your <\/b>plugins<\/b><\/a>.<\/b><\/p>\n\n\n\n

Open your domain\u2019s root directory and locate the <\/span>wp-content<\/b> folder.<\/span><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

Open the folder, right-click the <\/span>Plugins<\/b> folder and rename to<\/span> deactivate all your plugins.<\/b><\/p>\n\n\n

\n
\"Why<\/figure>\n<\/div>\n\n\n

Visit your website to check if it\u2019s working fine now. If yes,<\/span> rename the folder to reactivate all the plugins. <\/b><\/p>\n\n\n\n

Then follow these steps to identify the plugin causing the error:<\/b><\/p>\n\n\n\n