Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERR_TOO_MANY_REDIRECTS #28065

Open
Rusenche opened this issue Jan 26, 2023 · 6 comments
Open

ERR_TOO_MANY_REDIRECTS #28065

Rusenche opened this issue Jan 26, 2023 · 6 comments

Comments

@Rusenche
Copy link

Hello

I have a problem with the latest stable version 109.0.5414.119.

I am attaching a photo for you to see:

https://postimg.cc/wy6pKxSD

https://i.postimg.cc/Y9FqWhRD/Brave-error.png

I found the problem on this site: https://2baksa.ws/

I tested the latest latest portable version Brave v.1.47.186.

The site I specified is impossible to open because of an error:

"This page isn't working

2baksa.ws redirected you too many times.
Try clearing your cookies.
ERR_TOO_MANY_REDIRECTS"

Important clarification: I did all experiments with portable versions and without any ported settings, but only with a new profile and everything is new - with new settings.

Probably a Chromium issue, I have no other explanation.

If any of the build masters could file a problem report with Chromium or wherever.

The only possibility with 109.0.5414.119 to open https://2baksa.ws/ is only with a proxy, but agree that this is extremely inconvenient...

I'm sure there will be other sites that won't load and the error from the picture will appear.

Anyone with advice or to test my observations?!

@RazTK
Copy link

RazTK commented Jan 27, 2023

Another website that appears to suffer from the same issue: http://123tvnow.com

Most recent stable Brave version that works (at least with http://2baksa.ws): 1.46.153

LibreWolf browser, and I'm assuming Firefox itself and its other derivatives work just fine,

This happens also on Android with the latest Chrome and Kiwi Browser.

Using the latest stable version of any Chromium-based browser, there is no issue when using a VPN (perhaps also with just a proxy as the OP mentioned). There is also no issue browsing to the websites in a Hyper-V virtual machine with a NAT'd network adapter. As soon the adapter is in bridged mode (as in, the virtual machine gets the same IP configuration as the hosting physical machine), OR still in NAT mode but using the same DNS address as the physical machine, the issue reappears.

Hopefully this information helps a bit.

EDIT:

image

@Rusenche
Copy link
Author

Librewolf v.109.0-1 loads http://2baksa.ws and http://123tvnow.com. But so what, Librewolf isn't Chromium cored.

Everything works fine only up to version 108.0.5359.125. From this version up, any site that is http - is impossible to open. Such "progress" = regression!

Looks like google has removed http support and that's why such sites can't load?!

@rebron
Copy link
Collaborator

rebron commented Jan 27, 2023

cc: @ryanbr

@Rusenche
Copy link
Author

cc: @ryanbr

?!

What does your comment mean?! And what does "cc" mean?!

@RazTK
Copy link

RazTK commented Jan 28, 2023

Some more observations: Both domains use Cloudflare and both have an HTTPS DNS record; although both websites attempt to redirect you to HTTP when accessing them via HTTPS.

Also found this interesting article: https://blog.apnic.net/2022/08/10/the-https-record-passes-a-key-milestone/

image

So I setup a DNS server in a VM, added the relevant A records for 2baksa.ws, and I could access the website just fine. As soon as I added an HTTPS record, I got into the same redirection loop as reported in this thread. Removed it, problem gone. I am not sure though why there is no issue when using a proxy or a VPN or in a VM with the network adapter in NAT mode (and with the default DNS address that you get from the hypervisor).

I'm assuming we will face the same issue with every HTTP-only website that (for some reason) has an HTTPS DNS record for its domain.

As I said before, this issue began sometime after v1.46.153. v1.47.171 (the stable version after it) is already problematic.

@Rusenche
Copy link
Author

Okay.
From what I understand - any future new version after the Chromium core version (v.108.0.5359.125) will be problematic for users who open some sites on the internet - which sites will not load because of google developers in Chromium.

  1. Actually what is the solution if there is one?!
  2. It turns out that we should not use a newer version of the Chromium kernel (v.108.0.5359.125) to fully use the sites on the Internet.

It is obvious that the situation is worse than expected because even in Chromium there is no necessary flag to change to solve this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants