There was a problem loading the comments.

Fix WordPress “Too many redirects” / ERR_TOO_MANY_REDIRECTS

Support Portal  »  Knowledgebase  »  Viewing Article

  Print

The error “Too many redirects” (for example ERR_TOO_MANY_REDIRECTS) means your browser is stuck in a redirect loop — the site keeps redirecting back and forth.

On WordPress, the most common reasons are:

  • WordPress URLs set to the wrong scheme (http vs https) or wrong host (www vs non‑www)
  • Multiple redirect rules at once (WordPress + .htaccess + Plesk + Cloudflare)
  • Cloudflare “Flexible SSL” while the origin server forces HTTPS

1) Clear cookies and test correctly

  • Open the site in an incognito/private window.
  • If it works in incognito, the issue may be caused by cookies. Clear cookies for the domain and test again.

2) Check WordPress Site URL settings

In WordPress admin:

  1. Go to SettingsGeneral.
  2. Check:
    • WordPress Address (URL)
    • Site Address (URL)
  3. Both should match your real site address and protocol (usually https://).

If you cannot access wp-admin

You can set the URLs in wp-config.php (temporary fix):

define('WP_HOME', 'https://example.com');
define('WP_SITEURL', 'https://example.com');

Or you can update them in the database (advanced): in wp_options table change siteurl and home.

3) Remove duplicate redirects (keep only one “source of truth”)

Redirect loops often happen because the same redirect is configured in multiple places.

  • Plesk redirects: check Hosting Settings and any configured “Permanent SEO-safe 301 redirect” / domain forwarding.
  • .htaccess: if you recently edited it, temporarily rename .htaccess to test.
  • WordPress plugins: disable redirect/caching/security plugins temporarily.

4) If you use Cloudflare: fix SSL/TLS mode

If your WordPress site has a valid SSL certificate on GARMTECH (for example Let’s Encrypt in Plesk), use Cloudflare SSL/TLS encryption mode Full or Full (Strict).

  • Avoid Flexible if your origin server redirects HTTP→HTTPS — this is a classic redirect loop scenario.
  • After changes, purge Cloudflare cache and test again.

5) Common WordPress-specific fixes

  • Regenerate WordPress rewrite rules: SettingsPermalinksSave Changes.
  • Clear LSCache: LiteSpeed CacheToolboxPurge All.
  • Check for forced HTTPS settings in plugins or in wp-config.php.

After the fix

Once the site opens correctly, re-enable plugins one by one (if you disabled them) to make sure the loop does not return.


Share via
Did you find this article useful?  

Related Articles


Comments

Add Comment

Replying to  

Tags

© GARMTECH