How fix ERR_TOO_MANY_REDIRECTS?

Enable automatic HTTPS redirection IS OFF!

.htaccess
RemoveHandler .html .htm
AddType application/x-httpd-php .php .htm .html .phtml
or empty = different!

fix your code. unrelated to hestia

This is divinely related to HestiaCP.
Infinite HTTPS redirect it’s a bug EXACTLY with HestiaCP.
So fix your software (hestiaCP).

How reproduce:
1.) clean ubuntu 20.04 instance
2.) install hestiaCP via script from your front page
3.) create a user in hestiaCP and login to that user
4.) you must have Cloudflare domain created with no options in Cloudflare changed, only A DNS record point to VPS instance where hestiaCP installed.
4.) create domain example com (for example) as you have in Cloudflare
5.) Now go to Hestia → create domain → enter your example com
6.) now click edit example.com
7.) Checkbox: enable SSL for this domain. Checkbox: Use Lets Encrypt, Checkbox: automatic HTTPS redirection
8.) Save.
9.) Try to open your website. You will see tons of critical problems with an infinite redirect.

.htaccess as far as I’ve seen - empty.
The problem somewhere else. Due to the nature of the problem, I think this is related to the Nginx proxy that was incorrectly configured.

Please analyze, and fix that.
Note: exampleCom changed, due to limitations on this forum.

Infact of what you explain above, do you run any software for this specific webdomain or “only” the default template? For Cloudflare, did you used their protection service or just as dns provider? It’s easy to say it’s on hestia side, but there is no pending issue for infinite redirects. It could be more an issue together with cloudflare, the best practises can you read in our docs: SSL Certificates and Let's Encrypt — Hestia Control Panel documentation

So probaly if you go the suggested way, it should work out of the box. Another thing: Please don’t reopen “old” threads, it’s better to create a new one, because this is clearly not related to the issue above.

  1. Cloudflare is by default “https:// traffic to http://”
  2. Hestia recivies internally an http:// and redicrect the user to https://
    and so on…

Nothing we can do about it is just how Cloudflare decides to its work

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.