Chrome error: ERR_TOO_MANY_REDIRECTS

**Update

This known bug has been addressed, and the ticket has been closed in October 2015 (by the Google bug team).

Issue: Chrome error: ERR_TOO_MANY_REDIRECTS
Status: Some sites are seeing this error in the Chrome browser. There is currently an closed ticket on Google.com to address this error.
Who is impacted? This is only affecting some websites. To test your site, visit it with the latest version of the Chrome Browser.
Estimated time until resolution: Google is aware of this issue, and working on a resolution. They have not provided a specific ETA for the fix.

Are you ready for a hosting company that actually puts their customers first? InMotion is a leading provider of Web Hosting products back by world-class, 24/7 support.

Thoughts on “Chrome error: ERR_TOO_MANY_REDIRECTS

    • Hi there, sorry to see your upset. I can understand when things don’t work they way they should, it can be frustrating. It appears from the Google post that the issue has been resolved. If you are running the latest version of Chrome and are still receiving this error, you will need to review the configuration of your website, the DNS and your .htaccess file to ensure that they are all directing website traffic properly.

    • Hello Seppi,

      Apologies for the error. Unfortunately, this issue is something that Google must address. If you suspect it is a hosting issue, then you will need to speak with your hosting company. Your site is not hosted with InMotion so I cannot investigate the site through our servers.

      If you have any further questions or comments, please let us know.

      Regards,
      Arnel C.

    • @Arn, again … even though browsers’ bugs belong to those that created the issue(s), directing your customers away from the offending browser often sends them to another Web site instead ( i.e. their bug, yes, but it will be your company that suffers the sting of it’s bite ~;-)

      Until the required conditions no longer exist on your server(s)? This issue is gonna keep coming up, since Google’s built-in browsers will never go away. Not mixing legacy insecure content in w/ https requests solves the problem. Don’t wanna rewrite all your internal URLs? Still easily fixed:

      “Content-Security-Policy: upgrade-insecure-requests”

      Injecting one simple line solves this problem for InMotion, which (again) ain’t gonna go away ’til the conditions required to duplicate this error no longer exist upon your servers.

    • In regard to InMotion suggesting another browser, you’d asked the better question: “What kind of answer is that? Is there not a workaround you guys can give to your customers?”
      I, as a customer, was guilty of suggesting Firefox as well (due to my frustration with the results, since google closed this unresolved bug).
      You’re right … the appropriate response, and this goes for us all, isn’t to suggest upgrades or alternatives. Your question reminded me to find a solution that would allow the content to be fully accessible with the offending browser, which is really the only right answer.

    • Issue wasn’t resolved by google, and does present in some later versions of chrome. However, another user reminded me of our obligation to make every effort to assure our content remains fully accessible. Otherwise? Google’s bug bites you.

  • Quote “If you are getting this error in the Chrome browser, the best solution is to use a different browser (such as FireFox, Safari, IE, etc.) until Google releases an update to correct the error.”

    What kind of answer is that? Is there not a workaround you guys can give to your customers?

    • Hello Elliot,

      The issue was resolved in version 44 of the Chrome browser. If you are using a version higher than 44 and still getting this error please provide the url so we may investigate to make sure the problem is not something else.

      Best Regards,
      TJ Edens

    • @Arn:
      Issue continues, despite now using 52.0.xxxx.xx; suggested Google revisit.

      @ALL USERS:
      This appears to be an issue w/ CHROME, rather than hosting.
      Tell Google, and use Firefox ~;-)

  • i am also facing the same problem guys ?

    how can i solve this problem

    this error is sowing when i delete my .htaccess file from the server an i can i solve this now please help

     

    • Hello Milan,

      Sorry for the problem you’re seeing. I would recommend checking out this post for a possible answer. I hope this helps to answer your question, please let us know if you require any further assistance.

      Regards,
      Arnel C.

    • Hello Patricia,

      Sorry for the problem with the re-directs. Per the ticket with Google Chrome version 44.0.2403.107 of Chrome does address this issue.

      I hope this helps to answer your question, please let us know if you require any further assistance.

      Regards,
      Arnel C.

Leave a Reply