Homeassistant takes over my router admin page

Configuration
1

I’m using duckdns for my homeassistant so I can access it remotely.
So what I’ve done is that I have portforwarded 8123 in and out and 444 in and 8123 out like always. However I’ve noticed recently I can’t access my router website and have to factory reset it.
My Linksys velop router is on local IP 192.168.1.1 and as soon as I portforward the 443-8123 port the router website gets replaced by homeassistant. So when I try to browse 192.168.1.1 I get to homeassistant.

I have to factory reset the router…

2

External 443(from internet into router) is directed to HA

AND

Internal https://192.168.1.1 is routed to HA?

Clear browser cache and check results.

3

This is my portforwarding. And yeah it’s not a cache issue, same issue on any device I try on.

image
image1770×284 29.9 KB

4

Hello, I am having the same issue. (How) did you resolve this?

I tried changing the port forwarding rule from 4443 to 443 - and that resolves the issue of being able to access the router admin page from 192.168.1.1, but it breaks other things…

thanks!

5

Get a new router :slight_smile:
Seems like bad design. Maybe there is setting to stop prevent this

Internal and external 443 get routed but port forward rule it seems

What happens if you go to routerip:8123. Does that show HA?

6

Sorry for late response. Issue was using DuckDNS and how I had to open those specific ports.
I moved to CloudFlared addon and since then I’ve had no issues, and even a issue where my homeassistant would go down randomly dissaparead!

Dont use DuckDNS, I’ve only had issues with it

7

I guess you mean that HA was not reachable since the system will not fail due to a non-working DuckDNS

8

In my case it was DuckDNS acting up, being slow/unresponsive. Reaching the HA locally worked fine. A quick search will give you many threads here on this forum with people having same issue.