Macos Brave won't load 10.0.0.1

Nothing fancy on my end - an “out of the .dmg” browser config. No additional security besides what the OS does as-is. No added firewalls, VPNs, proxies, etc. I have tried disabling shields & using a private browsing window with no success at accessing my Xfinity Gateway cable modem’s software interface.

From Brave:

This site can’t be reached

http://10.0.0.1/ is unreachable.

ERR_ADDRESS_UNREACHABLE

I am also NOT able to get to it through Firefox.app:

Unable to connect

An error occurred during a connection to 10.0.0.1.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.

Though I can get to it through Safari.app

Any suggestions on how I can access 10.0.0.1 through the Brave browser?

I used to be able to access the modem at 10.0.0.1 just fine in Brave, but this week no dice (first noticed ~Monday 12/23/2024)

Brave.app Version 1.73.104 Chromium: 131.0.6778.204 (Official Build) (x86_64)
macOS Sequoia 15.2 (24C101)

Thanks.

I believe this post may be related:

(thank you, @fmarier !)

Of note: the “Upgrade connections to HTTPS” option is at brave://settings/shields (lots of sources citng it in Settings > Prvacy and security)

nope - even restarted Brave.app after Of setting “Upgrade connections to HTTPS” option at brave://settings/shields to Disabled (from Standard)

I have seen reference to “Upgrade navigations to HTTPS”(purportedly in Settings > Privacy and security > Security settings > Advanced Security Options) and “Always use HTTPS” (purportedly in Settings > Privacy and security > Security settings > Advanced Security Options), but I do not see them in my browser or when using text search in the settings :frowning:

So ood

deleting 10.0.0.1 from the HSTS did nothing :frowning:

You did refer to the following above, but to be clear:

Upgrade connections to HTTPS

In a Brave Browser New Window, go to:

brave://settings/shields

Disabled or set to “Standard” should allow HTTP.


You might use the Brave Browser Developer Tools window > Network tab / Console tab . . . in order to see some of what is happening.


Try:

  1. Clear caches, cookies, history and all that you are willing to clear, using the Advanced tab and “All time” for the Time range, at:

brave://settings/clearBrowserData

  1. Test each:
  • Brave Browser New Window
  • Brave Browser New Private Window
1 Like

@289wk thanks - I edited the earlier post - hopefully that made it clearer.

Nuking the cache didn’t solve the problem (in a new or new& private window, nor after restarting Brave in both)

interesting - using the Chrome browser app to access IP Addy 10.0.0.1 got me this response:

Allowing for it got me to the Xfinity login screen in through the Google Chrome browser.

Now, how to eeffect the same in Brave :thinking:

Lo and behold, without restarting the browser or trying in a new or new & pvt window, the Brave tab which had 10.0.0.1 loded upin the location bar and was displayiing an the “can’t reach” error msg simply loaded up the Xfinity login page.

Of note: this is also a thing in macOS::System Settings > Privacy & Security > Local Network:

Who knew?

I don’t know what state the macos settng was in when Brave wouldn’t access 10.0.0.1, nor what caused the kerfuffle to begin with last week, but it appears to have been resolved. I can now access 10.0.0.1 in Brave.

What t was about allowing Google Chrome (build similarities notwithsranding - a third party application :frowning:) access to local devices that fixed the issue, II do not know. Allowing this seems to have reset something in the OS :man_shrugging:

Possibly, the DNS cache was corrected. May interest:

https://phoenixnap.com/kb/how-to-flush-dns-cache
https://osxdaily.com/2017/03/08/clear-dns-cache-macos-sierra/

Terminal.app command:

$ netstat -an | egrep '(ESTABLISHED|LISTEN*)'

That’s very interesting. Thanks for sharing these screenshots @mixelpix . I was not aware of that new OS-level permission.

Also, from your screenshot, it looks like Safari is not subject to these new restrictions. Only third-party browsers.

1 Like

I had similar problems with not being able to access the local network on MacOS but only some ip addresses such as my server and access point were affected. I was able to access my router? NONE of the Brave browser settings I changed made a difference and I even deleted my history. My privacy settings in MacOS were set to allow Brave to access the local network. I shut down and was able to access the local network after powering on? Then noticed the same behavior later with losing local network access. I then re-toggled the switch for the MacOS Brave browser privacy and security setting noted in the screenshot above and regained access to the local network.

Is there an issue with MacOS permissions unexpectedly changing in regard to local network access for the Brave browser?

1 Like

they’re a competitor :person_shrugging:

glad that was able to help :slight_smile: