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...
Thanks for replying. You should see Chrome complain if you try either of these links
or
It will of course not show a certificate error if you simply use http:// rather than https:// but I'd prefer to find out what the Netgear certificate is so badly broken.
(I can't use IPv6 either as it's also broken in the current firmware release)
Thanks for replying. You should see Chrome complain if you try either of these links
https://<your IPv4 address>
or
https://orbilogin.local
Both connect for me with no problems. I tried Chrome, Edge and Firefox (being careful to use https).
Of course I do need to click through the certificate warning - that is expected with a self-signed cert. But no errors related to the key size.
Note I am using a Windows PC.
FWIW, routerlogin.net's certificate looks fine to me.
- signature algorithm of SHA-256 with RSA Encryption
- RSA key length is 2048 bits
- fingerprints are SHA-256
These meet current security standards, and shouldn't create any issues with Safari or other modern browsers.
The 10 year validity period ( 21 Jan 2026 - 19 Jan 2036) might be the problem. Apple says they want 825 days or less. But this has been out there for some time, and I would have expected to see more complaints if this happened with every safari user.
Issued by: routerlogin.net
Expires: Sunday, 8 October 2124 at 08:55:21 British
Summer Time
I am seeing a different expiration date, so I am thinking that somehow you might not be getting the correct cert.
Have you tried
- clearing the Safari Cache and data?
- disabling any VPN that is enabled
- turning off iCloud Private Relay (if you use it)
donawalt : Are you seeing this issue with Safari (using https://)
Thanks for checking. It’s not going to cause me sleepless nights, so I’ll leave it as just “one of those things”. It doesn’t impact the actual security of the connection internally but appreciate you checking.