[Nighthawk R6700v3] cannot access

192.168.1.1 is the default router IP ? I mapped it to something else 192.168.0.180. If I go there after setting up wifi 2.4Ghz and 5Ghz + reboot, I am usually redirected to a page to configure the admin password with security questions and then I can access it and configure the wifi guest. Now I am just redirected to https://www.routerlogin.net/genie_index.htm which gives me a 404 (the error I have in my initial message).

 

I must have been doing the same steps 10-15 times in the last 3 years because this router doesn't save the configuration. I never had this problem before.

I have my normal router (network provider) and then I have the nighthawk that I use as an access point where I have all the wifi (2.4Ghz, 5Ghz, guest wifi that I use for IoT devices). I am normally wired to my network provider router unless I have to setup the nighthawk when  I just change the network cable from the main router to the nighthawk.

 

I tried to use firefox, chrome, edge. I just can't reach the admin page to setup the admin password with any of them after the first setup (wifi) + forced reboot.

 

It looks to me that the redirection is wrong. What's the main page that should be accessed on the nighthawk because 192.168.0.180 redirects me to 192.168.0.180/start.htm then https://www.routerlogin.net/genie_index.htm where I get the 404

I also have the same question. I'm experiencing a very similar issue with my router where the initial setup appears to work, but after the reboot I can no longer access the management interface properly. Instead of reaching the configuration page, I get redirected and end up with errors that prevent me from completing the setup process. It becomes especially frustrating after multiple factory resets because everything seems to lead back to the same problem.

What makes it even more confusing is that basic network functionality may appear to work, but important settings remain inaccessible because the web interface cannot be reached. I've tried different browsers, devices, and connection methods, but the behavior remains the same. If anyone has found a reliable solution or knows whether this is related to firmware, browser redirects, or a known bug, I would really appreciate hearing about it.