NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Accessing orbilogin.local shows an error "certificate is using a broken key size" in Safari MacOS
The attached screen shot shows the error when trying to access the admin interface at orbilogin.local on my network using Safari in MacOS Sequoia. It seems to be related to another Netgear domain...
I think there may actually be two different issues here.
First, orbilogin.local doesn’t appear to be a generally supported access method on current Orbi models. I tested it on an Orbi 970 from both macOS and Windows, and it doesn’t resolve at all (ping orbilogin.local fails, and Bonjour/mDNS doesn’t advertise that name). However, orbilogin.com, routerlogin.net, and the router’s LAN IP all work normally. So you could use https://192.168.1.1, https://orbilogin.net, or https://orbilogin.com to access the router, albeit going through the certificate warning first.
Interestingly, Netgear’s documentation almost always references orbilogin.com and routerlogin.net. I searched netgear.com via Google, the only Netgear.com reference I could find on the whole site that mentions orbilogin.local is for the Orbi 770 series, not the 870 or any other router. That makes me wonder whether .local is only implemented on the 770 - or that even that reference could be an error. Since ceebee6cc has an 870 system, and mine is a 970, I really don't think orbilogin.local is supported at all in those routers' firmware.
The certificate warning is probably a separate issue. As others have implied, current versions of Safari are much stricter about older self-signed certificates than they used to be. I also receive a certificate warning when accessing my Orbi over HTTPS by IP, orbilogin.net or by orbilogin.com, but after accepting the warning the admin page loads normally.
Does https://orbilogin.com, https://routerlogin.net, or https://192.168.1.1 work for you? If they do, I’d be inclined to ignore orbilogin.local unless Netgear specifically says the 870 should support it. I don't think it does.
First, orbilogin.local doesn’t appear to be a generally supported access method on current Orbi models. I tested it on an Orbi 970 from both macOS and Windows, and it doesn’t resolve at all (ping orbilogin.local fails, and Bonjour/mDNS doesn’t advertise that name).
As I said in my earlier post, I was able to connect using orbilogin.local to my own Orbi 870.
Ping resolves it to a link-local ipv6 address
Pinging orbilogin.local [fe80::5607:7dff:fe20:2aed%17] with 32 bytes of data:
Reply from fe80::5607:7dff:fe20:2aed%17: time=4ms
Reply from fe80::5607:7dff:fe20:2aed%17: time=1ms
Reply from fe80::5607:7dff:fe20:2aed%17: time=2ms
Reply from fe80::5607:7dff:fe20:2aed%17: time=2ms
Powershell also shows the ipv4 address of my router
Resolve-DNSName -Name orbilogin.local
Name Type TTL Section IPAddress
---- ---- --- ------- ---------
orbilogin.local AAAA 4500 Answer fe80::5607:7dff:fe20:2aed
orbilogin.local A 4500 Answer 10.0.0.1
orbilogin.local AAAA 4500 Answer fe80::5607:7dff:fe20:2aed
orbilogin.local A 4500 Answer 10.0.0.1
mDNS is not advertising the name - at least neither of the mDNS viewers I tried found it. (One running on a windows PC, the other running on my iPhone). So this has to be coming from the Orbi's DNS resolver (the PC resolver is set to 10.0.0.1 by DHCP).
Oddly, when I look at the certificate for https://10.0.0.1, , the common name of the self-signed cert is routerlogin.net (which is also what ceebee6cc is also seeing).
FWIW, both ipv6 and UPnP are disabled in the router.
Yes, I’m seeing the same here with both IPv6 and UPnP likewise off.
iPad $ ping orbilogin.local
PING orbilogin.local (10.168.168.1): 56 data bytes
64 bytes from 10.168.168.1: icmp_seq=0 ttl=64 time=8.648 ms
64 bytes from 10.168.168.1: icmp_seq=1 ttl=64 time=10.220 ms
64 bytes from 10.168.168.1: icmp_seq=2 ttl=64 time=10.520 ms
64 bytes from 10.168.168.1: icmp_seq=3 ttl=64 time=10.872 ms
iPad $ host orbilogin.local
orbilogin.local has address 10.168.168.1
orbilogin.local has IPv6 address fe80::5607:7dff:fe34:92f2