Can no longer access router GUI

[Lee MacMillan]

I was changing the LAN DNS director settings so my (Windows 11) desktop and laptop would go through Quad9 DNS servers. I had Quad9 selected in the WAN page but the ipconfig still showed my ISP (Comcast) as one of the servers. I did the desktop and it went it applied the change. When I did the laptop, it hung up on the applying changes page so I closed that tab. Now I can't access my router even after rebooting it. I get the "this site can't be reached" page. The router and internet connections are working fine otherwise. 192.168.1.1 doesn't work either. I guess I should have left well enough alone. Suggestions on next steps?

​

 

[dave14305]

Is the default gateway in ipconfig really 192.168.1.1? Use whatever that gateway IP is with these different options:

http://192.168.1.1/
https://192.168.1.1:8443/

 

[Lee MacMillan]

IPconfig shows:
Default Gateway . . . . . . . . . : fe80::3e7c:3fff:fee2:ccf0%14
192.168.50.1
I tried the 192.168.50.1 with http and https and both timed out.

 

[dave14305]

IPconfig shows:
Default Gateway . . . . . . . . . : fe80::3e7c:3fff:fee2:ccf0%14
192.168.50.1
I tried the 192.168.50.1 with http and https and both timed out.

Did you specifically try https://192.168.50.1:8443/ ? Do you have ssh enabled?

 

[Lee MacMillan]

Did you specifically try https://192.168.50.1:8443/ ? Do you have ssh enabled?

I got in with this link. I got a couple Chrome warnings about privacy before I got to the login screen. I was able to access the GUI from my laptop normally but I don't know why. I deleted the DNS director change for my desktop that I had made previously. The entry for my laptop which caused this mess not there, not surprising since it hung when I had tried to apply it.

I do not have ssh enabled. I didn't know what it was but I found it on the administration/system page and it is not enabled.

I logged out and still get the "this site can't be reached" message when I try to access via http://www.asusrouter.com/Main_Login.asp. Still not sure what I did or how to correct it.

I have a saved configuration from just a few days ago that I will restore and see if that fixes the issue.

 

[Lee MacMillan]

I figured it out and it was something I did. It's too embarrassing to explain. Thanks for your help!

 

[jerry6]

you need to use https unless you chabge the settins on the routter on the admin>system page