How to fix too many redirects on your website

The ERR_TOO_MANY_REDIRECTS error means your browser is stuck in a redirect loop — the server keeps sending it back and forth between URLs without ever loading the page. This guide explains the most common causes and how to fix each one.

What causes a redirect loop

A redirect loop happens when two or more rules conflict. The browser is told to go to URL A, which redirects to URL B, which redirects back to URL A, and so on. After about 20 attempts, the browser gives up and shows the error.

On WordPress sites hosted with Web60, the three most common causes are:

1. The WordPress Address and Site Address do not match or are set incorrectly.
2. An SSL or redirect plugin is conflicting with server-level HTTPS.
3. Incorrect rewrite rules in the .htaccess file.

Fix 1: Check your WordPress URL settings

WordPress stores two URL values: WordPress Address (siteurl) and Site Address (home). Both must be set to your full domain with https:// — for example, https://yourdomain.ie.

If you can access the WordPress Dashboard, go to Settings, then General, and check both fields.

If you cannot access the Dashboard because of the redirect loop, use the WP-CLI tool in your Web60 portal:

wp option get siteurl
wp option get home

If either value is wrong (for example, using http:// instead of https://, or a different domain), update them:

wp option update siteurl 'https://yourdomain.ie'
wp option update home 'https://yourdomain.ie'

Replace yourdomain.ie with your actual domain name.

Fix 2: Deactivate SSL and redirect plugins

Web60 handles SSL certificates and HTTPS redirection at the server level. You do not need any plugin to force HTTPS. Plugins like Really Simple SSL, WP Force SSL, or Easy HTTPS Redirection add their own redirect rules that conflict with the server configuration, creating a loop.

Deactivate any SSL or redirect plugins using WP-CLI:

wp plugin deactivate --all --skip-plugins --skip-themes

Reload your site. If it works, reactivate plugins one at a time to identify which one caused the conflict. Leave any SSL or redirect plugins deactivated — they are not needed on Web60.

Fix 3: Check .htaccess rules

If you or a plugin have added custom redirect rules to the .htaccess file, they may conflict with the server configuration. Open File Manager in your Web60 portal and look at the .htaccess file in your site root. Remove any rules that force HTTPS redirects or rewrite URLs. The standard WordPress rewrite rules should look like this:

# 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 there are extra rules outside the WordPress block that mention HTTPS or redirect, remove them.

Clear your cache

After making any of the fixes above, clear your site cache from the Web60 portal. Also clear your browser cache, or test in a private browsing window, because browsers cache redirect responses.

FAQ

Q: Why does this happen after installing an SSL plugin?

A: Web60 handles SSL and HTTPS redirection at the server level automatically. When you install a plugin like Really Simple SSL or WP Force SSL, it adds its own redirect rules on top of the server ones. The server redirects to HTTPS, then the plugin redirects again, creating an infinite loop. Removing the plugin fixes the problem.

Q: Will clearing my browser cache fix this?

A: Sometimes. Browsers cache redirect responses, so even after you fix the underlying cause, your browser may continue to follow the old cached redirect. Clear your browser cache or try opening the site in a private/incognito window to test.

Q: How do I check my WordPress URL settings without access to the Dashboard?

A: Use the WP-CLI tool in your Web60 portal. Run wp option get siteurl and wp option get home to see the current values. If they are wrong, use wp option update siteurl 'https://yourdomain.ie' and wp option update home 'https://yourdomain.ie' to correct them.