Accessing orbilogin.local shows an error "certificate is using a broken key size" in Safari MacOS

routerlogin.net is mostly supported on Nighthawk router systems. Orbi uses orbilogin.com or router IPv4  IP address. Which I mostly use is the IP address on my 870 series all the time. 

Ya, you'll get cert warnings on most newer browsers. One you accept the warning, you won't see it. Been like this for years. Browser security tag back and forth. 

https://kb.netgear.com/000061003/I-get-a-security-warning-in-my-browser-when-I-try-to-log-in-to-my-NETGEAR-or-Orbi-router-what-do-I-do

Thanks for such a full reply.

The suggestion to use orbilogin.net is on the base of the 871 router. However that, along with all the other’s mentioned in your reply fail from here at least and simply resolve to a generic Netgear support page suggesting I instead use the app (see attached)

This support page, although not 870 specific, seems to suggest using orbilogin.local or 10.168.168.1 both of which are accessible from my internal network here.

https://kb.netgear.com/31142/Why-can-t-I-access-orbilogin-com-or-orbilogin-local

donawalt wrote:

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.