Brave redirects port 80 to router

1

Hi all.

I’m having a problem.

I have a file server running on one of my machines (192.168.0.20). I have a DDNS so that I can access my network from the outside. My router redirects port 80 to that machine.

When I try to access my files server, from within the network, using the Local IP, it works. But, if I use the DNS address, it shows me my router admin login (that is not even on port 80). From outside the network I can connect only using the WAN IP, but not the DNS address (gives me “Connection_Refused”)

This only happens with Brave. On my computer (in the LAN - Windows 10 Pro 22H2, with Brave 1.87.191), or in my mobile (outside the LAN - Android 15, with Brave app 1.87.190). When I use Chrome or Firefox I can access the file server from within the network (with computer or mobile), or from outside (with mobile), using either my WAN IP or DNS address.

Any clues?

2

@HotDrive

Please edit your Original Post (“OP”) above, and fill in the blanks:

  • Brave Browser version numbers
  • Operating System version numbers

For each computing device that you are using to reach your “my network” - probably a Local Area Network (“LAN”) given your “one of my machines (192.168.0.20)”.

For your “using the IP” - possibly you mean: using the LAN IP address 192.168.0.20

And, for your “But, if I use the address,” - possibly you mean: But, if I use that LAN IP address 192.168.0.20,"

So you map out what you have and where.

1 Like
3

@HotDrive

So, what seems to be the situation:

DDNS (Dynamic DNS) is a service that keeps a DDNS hostname (what you refer to as a “DNS address”) updated to whatever your current, public WAN IP address is, so you can remotely reach your home network at the DDNS hostname (a stable name), even though your public WAN IP address may change.

The LAN file server works, when accessed by LAN IP (http://192.168.0.20), from inside the LAN - when using Brave Browser, Chrome, and Firefox - and that applies to Windows 10 PC and Android devices.

The LAN file server works, when accessed by DDNS hostname, from inside the LAN - when using Chrome and Firefox, BUT NOT when using Brave Browser - and that applies to Windows 10 PC and Android devices.

When using the WAN IP or DDNS hostname, for remote access by the Android device:

The LAN file server works, when the home network is reached at either a) the public WAN IP address, or b) the DDNS hostname - when using Chrome and Firefox, BUT NOT when using Brave Browser.

When and where Brave Browser fails, it shows either: a) the home network router admin login, when access attempt is within the LAN, or b) ERR_CONNECTION_REFUSED, when access attempt is remote via the WAN.

Possibly, the failing is because of the Brave Browser and home network router (its embedded “website”) relationship.

Tips regarding Brave Shields:

I have more success, with:

  • Brave Shields UP, but . . .
  • Either Allow All Cookies or Block 3rd Party Cookies, but NOT Blocking All Cookies
  • Allowing JavaScripts from specific sources, but NOT Allowing All JavaScripts
  • Trackers & Ads treatment: Aggressive (at first), and then incrementally relaxing that setting
  • Fingerprinting (aka footprinting) blocking: Strict (at first), and then incrementally relaxing that setting

I almost NEVER use:

  • All of Brave Shields UP
  • All of Brave Shields DOWN

Shields Basics

How do I configure global and site-specific Shields settings?

How do I use Shields while browsing?

Test: In a Brave Browser New Window, go to: brave://settings/security and Disable User secure DNS ← test is reported to have failed.

1 Like
4

So, your assumptions are almost all correct. The only thing missing is:

  • When I use Brave from inside the LAN (Windows PC)
    • Using Local IP → File server
    • Using DDNS hostname → Router admin login
  • When I use Brave from outside (Android device)
    • Using WAN IP → File server
    • Using DDNS hostname → ERR_CONNECTION_REFUSED

Also, “User secure DNS” is disabled.

Thanks for the help.

5

UPDATE:

On Brave Shields, I changed the setting “Update HTTP to HTTPS” (for my DDNS hostname), and now it’s disabled. I can now access my file server with Brave, using DDNS hostname, from inside the LAN.

I can also access my file server from outside, using WAN IP or DDNS hostname, but I had to disable “Update HTTP to HTTPS” and also delete HSTS settings (@ brave://net-internals/#hsts) for DDNS hostname.

All working now, apparently.

It seems Brave was redirecting port 80 to 443 and, since the file server machine doesn’t have service on port 443 (although port 443 is also directed to the same machine, via router), somehow it was going to the router admin page or being denied connection.

1 Like