I am having weird issues with my network. Specifically I can no longer access my router landing page. I suspect I have a conflict somewhere because I do not know what I am doing with networking settings, at all.

 

My router should be 192.168.1.1 - this should also be accessible via a DDNS service at asuscomm.com but it doesn't seem to be. I have a router app on my phone that *can* access it, but it does not work in a browser from my pc.

 

My unraid server is set in my router settings to permanently be assigned 192.168.1.10. This *does* work but it always gives me a "site is not secure" error in browser even though letsencrypt should be working. If I let the router auto-assign an address then the letsencrypt link does work. It doesn't when I specify what I want it to be.

 

Docker is enabled and the network settings appear to be:

IPv4 custom network on interface br0: Subnet: 192.168.1.0/24 Gateway: 192.168.1.1 DHCP pool: not set

 

In "Network Settings" I have: 

IPv4 address: 192.168.1.10 /24

 

MAC Address: 80:61:5F:08:A8:8A

(This MAC Address is set to 192.168.1.10 in the router IP Bonding List)

 

IPv4 DNS server assignment: Static

 

IPv4 DNS server: 192.168.1.1

 

My router DNS Settings pull from 192.168.1.120 which is my pihole adblocker.

 

I can access my shares from my pc, pihole seems to be blocking things correctly (for the whole network), I can access Tower from the 192.168.1.10 address but not the letsencrypt link found in encryption management and I cannot access my router at 192.168.1.1, only from the app on my phone when on my local network (or VPN into my network via OpenVPN).

 

Is something in the above just conflicting? If more info is required please let me know. Thanks.

Something on the network (likely piehole) is also being assigned the ip address 192.168.1.1 or likely piehole is breaking the dns bind on the network that would allow it to communicate to the router...

The site is not secure" error is a normal standard error about access http / https non cert through the web page. Ignore them when connecting to local and lan machine at 192.168.1.x

Try to turn off piehole as pinhole can act as a router and be a broken with DNS.
You may also need to add a dns entry to asuscomm.com to 192.168.1.1 as pihole may not be able to see that device on the lan.

Your router is the type i absolutely hate. Dam phone API and werid broken apps to configure base home networking... on your phone try manually setting your dns to 192.168.1.1 and try the app again.

Otherwise, your out of luck and need to hold the router down to factory reset it to bring back to a configurable working state.

Since its a asus router, i would recommend the asus merlin custom firmware.
https://www.asuswrt-merlin.net/

?Can you access the router if the unraid system is off?

Edited October 23, 20241 yr by bmartino1

Been a minute since I had time to look at this. I appreciate the reply. Kids take up a lot of time. PiHole is currently assigned 192.168.1.120. That doesn't appear to be the issue.

On 10/22/2024 at 11:51 PM, bmartino1 said:

or likely piehole is breaking the dns bind on the network that would allow it to communicate to the router...

 

I don't know what that means but I DO think you are on the right track with PiHole being an issue. How would I verify this issue and correct?

Edited October 30, 20241 yr by Hydranmenace

turn off pihole and set phone dns manual to router ip 192.168.1.1 try app again...

if success then pihole is killing your local dns name resolution and you will need to add a dns record...

Pihole > Local DNS > Dns Records

add one for the asus api...

her is an example I use for unifi so if i call unifi it goes to 192.168.2.4

in your case, you need to add one for 
asuscomm.com to 192.168.1.1

you also may need to whitelist the apps calls as example:

 

Edited October 30, 20241 yr by bmartino1