Title. Visiting Brave.com I get the following error, after updating to latest Brave beta build (Version 1.60.86 Chromium: 118.0.5993.54): brave.com is blocked brave.com refused to connect.
@Notloc it’s seeming like it might be a DNS issue or something. Have you changed anything at brave://settings/security such as Use secure DNS?
Other thing would be to suggest you go to brave://net-internals and click on DNS area. Select Clear host cache and exit Brave. Then when you return, see if it resolves or continues.
Just a FYI, this tells us that it’s likely not an extension or cookies causing issues. Which would bring us to the idea of settings you have changed or a 3rd party thing, such as a firewall or antivirus.
This confirms what I stated right above. The new profile would go by default settings. It does potentially say that it’s less likely to be something like a firewall, but you have something with DNS or connection.
@chraebsli definitely was looking at a good place. Only thing I’ll mention is that on Brave, any changes you make to brave://flags will persist across all profiles. The same is true for any custom content filters you create under brave://adblock. I strongly believe those things should be restricted to each individual profile, but it’s not set up that way for now. So it makes flags an unlikely suspect.
I’m kind of at a limit for now. I will tag @Mattches and @steeven but with it being Friday night and near the end of the day, I’m not sure that either will see this or be able to help prior to Monday at the earliest.
I might tag in @fanboynz as he tends to pop in and out a bit more often.
Beyond that, would have to look to people not employed by Brave who might have some ideas, such as @JimB1 or @justsomeone1 .
None of the Tor sites above worked, and going to (brave://settings/privacy) as @chraebsli suggested, I saw under Tor windows “Private window with Tor” was turned on. Turning this off no longer redirects those sites to the Tor version. This was the fix. Thank you!!!
Never mind, spoke too soon. This didn’t dix it.
It was the “Automatically redirect .onion sites” setting. It’s actually fixed now. Must have turned itself on when the update happened.