NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Can't access router configuration page also DHCP is giving out IP's slow
This is all I can get even though I am trying to access with the local ip Hmmm… can't reach this page It looks like the webpage at (local IP) might be having issues, or it may have moved permane...
oxyIT wrote:This is all I can get even though I am trying to access with the local ip
Hmmm… can't reach this page
It looks like the webpage at (local IP) might be having issues, or it may have moved permanently to a new web address.
ERR_SSL_KEY_USAGE_INCOMPATIBLE.
Known issue. See:There is a workaround in that thread, or you can use Firefox. Ultimately, it's up to Netgear to fix this.
The post does not describe the URL that it being opened.
It would not let me post with the URL in my original post but I can try local 192.168.1.1 but also routerlogin.net does not work either.
Thanks for the information. Yes, this forum software does not accept HTTP unless it is specifically entered using this symbol on the menu bar:
The Orbi Domain Name Service (DNS) module intercepts several search requests (orbilogin.com, orgilogin.net, etc.) and returns the IP address of the router itself. This is often 192.168.1.1, but when the Orbi router is connected to another router that has created a LAN subnet of 192.168.1.x, the Orbi creates a LAN of 10.0.0.x
What device is being used to access the Orbi web administration? (PC? Mac? tablet? smart phone?)
The correct IP address to use is the "gateway IP" that has been returned by the DHCP process.
On a Windows PC, the config /all command reveals what this IP address is.
p.s. I forgot the "obvious". If the IP address assigned to the device trying to open the Orbi web interface is xx.xx.xx.##, then the IP address of the router is going to be xx.xx.xx.1
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1Should Note I'm connected via Ethernet to the Router.
I had already checked that, I am connecting with a pc and was able to get logged into via Firefox, I'm going to assume there is something in Edge preventing me from even getting to the login page, usually on the page I have to deal with the HTTPS and allowing it to connect since no web browser will accept the Netgear self signed certificate. Just strange that after allowing it, then I get that error and it will refuse to load the webpage.
I also may have discovered what is causing my DHCP issues. Since I was able to log in through Firefox.
Should also note: fresh install windows 11 (and full updated) so edge was the quick option at the moment to check for dhcp issues at the time since I was originally only having issues on the PC but it then spread to other devices.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
