Resolving the Too Many Redirects Error in VergeCloud

Resolving the Too Many Redirects Error in VergeCloud

What is Too Many Redirects Error

The "Too Many Redirects" error occurs when a browser repeatedly attempts to load your website but is caught in a redirection loop, unable to determine the correct destination. After 16 attempts, the browser displays this error, indicating that it cannot proceed further.

Why This Error Happens

This error typically occurs when there is a misconfiguration in your website's redirection settings, leading to conflicting or continuous redirects between URLs. For example, the browser may be redirected between "www" and non-"www" versions of the site without resolution.

Scenarios That Cause the Error and Soultions

1. HTTPS Settings

Issues with HTTPS configuration can result in redirection loops. Consider the following scenarios when setting up HTTPS on VergeCloud:

  1. Your web server only responds to HTTP requests: Disable the Secure connection of HTTPS with Origin Server setting. VergeCloud will then communicate with your server over HTTP (port 80).
  2. Your web server only responds to HTTPS requests: Enable the Secure connection of HTTPS with Origin Server setting, so VergeCloud communicates with your server over HTTPS (port 443).
  3. Your web server responds to both HTTP and HTTPS requests: Set the Secure connection of HTTPS with Origin Server to Automatic Mode. This ensures:
    • If a user sends a request over HTTP, VergeCloud forwards the request to your server in HTTP.
    • If a user sends a request over HTTPS, VergeCloud forwards the request to your server in HTTPS.

2. Transfer Domain to www Setting

When the Transfer domain to www setting is enabled in your CDN configuration, and your web server is configured to serve the website without "www," this mismatch can result in redirections between "www" and non-"www" versions of the site, creating a loop.

How to Prevent the Error

  • Review your HTTPS settings in the VergeCloud dashboard and ensure they align with your web server’s protocol settings.
  • Verify the "Transfer domain to www" setting and ensure it matches your web server’s configuration to avoid conflicting redirections.
  • Test your website after making changes to confirm that no redirection loops occur.

Considerations

  • Always test HTTPS configuration changes to avoid unintended redirection loops.
  • When using the "Transfer domain to www" setting, ensure consistency between VergeCloud’s configuration and your web server’s response.
  • If enabling HTTPS for the first time, verify your origin server settings and confirm compatibility with VergeCloud’s CDN.

    • Related Articles

    • Troubleshooting ERR_SPDY_PROTOCOL_ERROR in Chrome

      What is ERR_SPDY_PROTOCOL_ERROR? The ERR_SPDY_PROTOCOL_ERROR occurs in Chrome when there is an issue with the SPDY or HTTP/2 protocol. This error can appear while trying to load a website, even for well-known domains. It typically stems from browser ...

    • Troubleshooting DNS_PROBE_FINISHED_NXDOMAIN Error on VergeCloud

      Understanding DNS_PROBE_FINISHED_NXDOMAIN Error The DNS_PROBE_FINISHED_NXDOMAIN error occurs when a DNS lookup is performed for a domain name, but no corresponding IP address is found. NXDOMAIN stands for "Non-Existent Domain," indicating that the ...

    • Troubleshooting SSL Errors on VergeCloud CDN.

      Troubleshooting SSL Errors on VergeCloud If users encounter SSL errors while visiting your website and you are utilizing VergeCloud’s content delivery network (CDN), the issue may stem from several potential causes. This guide outlines common factors ...

    • Troubleshooting ISP Accessibility Issues with VergeCloud CDN.

      Resolving ISP Access Issues with VergeCloud If your website is inaccessible to users from specific Internet Service Providers (ISPs) while using VergeCloud's CDN, this guide provides solutions to common causes, such as firewall and rate-limiting ...

    • Troubleshooting Traffic Routing Through VergeCloud CDN

      After updating your NS records to utilize VergeCloud CDN, you might notice that the traffic isn’t yet routed through VergeCloud. This issue can arise due to two main reasons: Reason 1: Delay in Propagation of Changes Although you have updated your NS ...