Self-Signed Certificate Error on Orbi RBR50v2

This is not the first time an issue similar to this has been posted.  FURRYe38 is correct that the self-signed certificate issue only affects sonnections to the Orbi router secure web interface, the https interface, not the http interface used for administration.

My hypothesis is that a connection attempt to an internet resource has been blocked and the browser redirected to the Orbi secure .interface to display an error message and the browser takes over and complains about the certificate.  For example, this recent post talks about getting a certificate error and after ignoring the error getting a message from the Orbi system:

https://community.netgear.com/t5/Orbi/Unable-to-connect-via-WIFI-b-ut-LAN-Invalid-security-certificate/m-p/2088811#M119703 

Notice the Firefox (browser) message that google.com requires a secure connection, but the certificate sown is for "routerlogin.net" (not google.com).  Pressing on to ignore the certificate warning brings up a message from routerlogin.net. (Device Blocked) So my hypothesis is that the certificate problem only shows up because some other problem has triggered a connection to the secure web interface.

That post goes on to explore possible ways that devices could be blocked (or "paused" in terms of the Orbi "app").

I, myself, have had situations where I used the Orbi app for something innocuous and later found that the Orbi Access Control had been activated (I do not use access control - that's a different story.) and a device blocked.  I believe my exact words were "What the F**K just happened?"  This was before the recent change in web browsers which now enforces the HSTS protocol (see Wikipedia).  All I got was no connection and it took me quite some time to track down the Access Control issue.

I see a couple of ways to proceed:

• Determine that the Orbi is not actually blocking any devices.  Perhaps ensure that Access Control is not enabled, reboot the Orbi, and verify that Access Control remains "un"abled.  Then see if the problem persists.
• If the problem persists, then something is wrong with the firmware.  Either Factory Reset and configure the 2.7.2.104 firmware, or do a manual firmware upload to the previous firmware that came before 2.7.2.104 and configure it.

Every Orbi setup is  unique.  If there are bugs in the code, then the precise sequence of changes can have an effect on the configuration.  Just because some Orbi's function well on 2.7.2.104 does not mean that all do.  And, just because 2.7.2.104 is "broken" on some Orbi's does not mean that it is broken on all of them. (not broken "yet", and maybe never broken because the precise sequence of events may never happen.)

p.s. If I were able to replicate this problem on my Orbi, I would go into debug mode and collect the LAN/WAN packets involving this device.  Does it get an IP via DHCP?  Does it do a DNS search on the URL? Does it send an HTTP connect request?  Does it get answers?  Do any packets actually go to the web URL? At what point does it get an https response from the Orbi? etc. etc.

Perhaps someone has a better explanation?