Forum Discussion

Kandyman's avatar
Kandyman
Aspirant
Jun 13, 2022

RBR50 - Cannot connect to admin console (web site) after upgrade to v2.7.4.24

I have a mesh system with an RBR50 and two RBS50. These are v2 devices. I started the upgrade to v2.7.4.24 using the web admin console. At some point I got disconnected (probably when the router was rebooting), and I have since not been able to reconnect to the admin console. The web site/pages do not load. The browser just spins and eventually times out. Everything appears to be working though. I just can't access the admin console via its IP address. The router is configured in bridge mode so using the app is not an option.

 

Here is what I have done:

  1. I have tried Edge, Chrome Firefox. Heck, I've even tried curl just to see if I can get a connection. Nothing is returned/loaded. 
  2. I have used PowerShell to test ports 80 and 443 on the router IP, and they are both open.
  3. I have tried to factory reset the router 3 times, hoping I could go back to a blank slate. The old config just keeps getting loaded.

I am not sure what to do next.  Any suggestions?

9 Replies

  • vpollinzi's avatar
    vpollinzi
    Aspirant
    Jan 21, 2024

    Thanks for your feedback! I suppose the developer/programmer that added the option didn't understand the ramifications of maintaining certificates. Disabling RSA key usage in chrome doesn't buy me any more security than what I have with http protocol, (chrome --force-fieldtrials=RSAKeyUsageForLocalAnchors/DisabledLaunch).
     

    An encrypted connection to management console would have been nice though. Guess I'll have to rely on strong password. Thanks again.

     

    • schumaku's avatar
      schumaku
      Guru - Experienced User
      Jan 21, 2024
      vpollinzi wrote:

      I suppose the developer/programmer that added the option didn't understand the ramifications of maintaining certificates. Disabling RSA key usage in chrome doesn't buy me any more security than what I have with http protocol, (chrome --force-fieldtrials=RSAKeyUsageForLocalAnchors/DisabledLaunch).

      That's not the case. For once one of the browser makers again run ahead for something the industry - and even more consumer devices and infrastructures - can't cope with (like fully featured DNS infrastructures, to allow complete https deployment. This does not abandon any https security. Many more vendors are affected by this wonderful rush forward. The browser will just not look for the keyUsage bits like digitalSignature -and- keyEncipherment which does typically not exist on any self-signed and many CA signed certificates. It won't abandon the basic encryption. The browser simply error-out and won't continue in case the keyEncipherment bit is not set.