NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Unable to connect via WiFi - invalid certificate
This is a continuation of this post: https://community.netgear.com/t5/Orbi/Unable-to-connect-via-WIFI-b-ut-LAN-Invalid-security-certificate/m-p/2088811 * This happens on all websites and multiple w...
- I'm sure this is related to HSTS.
Most sites now force https and the built-in Orbi certificate is not valid, therefore the browser throws a warning.
Why does this only happen over wireless and why does this also block the MAC address?
Is there a way to update the cert via a serial (telnet) connection to the router?
the cert is built into the firmware, so could only one of the satellites and an invalid cert?
Could it be that one of the satellites
jkevincook wrote:
Netgear support won't help me since my support contract has conveniently expired.
Can someone from Netgear respond to this and suggest a fix?
Netgear support staff do not participate in the community forum. (with the exception of forum moderators who are tasked with maintaining the mechanics of the forum. The moderators occasionally respond to specific issues, but the intention is for the customers to talk amongst themselves.
jkevincook wrote:
Is there a way to update the cert via a serial (telnet) connection to the router?
the cert is built into the firmware, so could only one of the satellites and an invalid cert?
No. There is no way to replace the SSL certificate embedded in the firmware.
No chance that one satellite will have an invalid cert.
Some thoughts:
- Although the problem may appear to be identical to a conversation from 18 months ago, it might be useful to describe the situation in a bit more detail. My RBR50 with the same firmware definitely causes modern web browsers to complain about the self-signed SSL certificate. However, choosing the option "go there anyway" stops the browser from complaining.
- If I read that conversation correctly, it appears that doing a Factory Reset on the router cured the problem.
(Maybe I misread. Even so, when a problem resists every other attempt to fix it, a Factory Reset is almost always suggested.) - It is a puzzle to me that the complaint is that (in the referenced conversation) the complaint is that Google.com cannot be trusted, but the invalid cert is clearly the self-signed Netgear cert on the router. Could clearing browser cache perhaps be a solution?