Netgear Orbi RBK50 - Web certificate expired yesterday (Aug 2, 2019)

schumaku
Guru - Experienced User
Nov 11, 2019
Wire1852 wrote:
FURRYe38 wrote:
https://kb.netgear.com/000061393/RBR50-RBS50-Firmware-Version-2-5-0-40-Hot-Fix

Are you insane?
It's your choice what is more important - a valid certificate or a random older firmware you prefer for whatever reason. Unlikely Netgear will release older firmware(s) with the new factory certificate.
- Wire1852
  Apprentice
  Nov 11, 2019
  schumaku wrote:
  
  It's your choice what is more important - a valid certificate or a random older firmware you prefer for whatever reason. Unlikely Netgear will release older firmware(s) with the new factory certificate.
  
  ----------------------
  But they will release the valid security certificate in future releases that are actually stable. Assuming Netgear get it's act together.
FURRYe38
Guru - Experienced User
Nov 11, 2019
Users need to factory reset there systems after loading v38 or v40. There is a known problem with v38 with device naming. This doesn't effect overall operation. I saw no issues with over all operation with v38 after a manual FW load and factory rest I'll be doing the same again to check v40. Users will have to wait for NG to fix the device naming problem or revert back and wait till the fix comes from NG. Up to users to use it or not. Complaining doesn't solve anything.
Wire1852 wrote:
FURRYe38 wrote:
https://kb.netgear.com/000061393/RBR50-RBS50-Firmware-Version-2-5-0-40-Hot-Fix

Are you insane? You're pointing people to a hot fix that is on top of 2.5.0.38 that people have been experiencing issues with for the last 2 weeks. Netgear indicate the hot fix only fixes the security certificate issue. All the other issues in 2.5.0.38 are still in this hot fix.
- Retired_Member
  Nov 11, 2019
  FURRYe38 wrote:
  Users need to factory reset there systems after loading v38 or v40.
  
  factory reset is for lost passwords
  - tomschmidt
    Virtuoso
    Nov 27, 2019
    NG recently released hot fix v2.3.5.34 to attempt to update the expired https certificate. However, they replaced it with a self-signed certificate instead of one issued by a certificate authority (CA). This still causes browsers to not trust the https URL for the router.
    
    Here is the certifcate error shown on Firefox 70.0.1 for the v2.3.5.34 firmware:
    
    orbilogin.net uses an invalid security certificate.
    
    The certificate is not trusted because it is self-signed.
    
    Error code: MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT
    
    I do not have v2.5.0.40 hot fix installed due to the major bug in device naming that it introduced. So I do not know if it likewise has a self-signed certificate instead of a valid CA issued certificate. If someone is running v2.5.0.40, can you check the certificate and report back? And open a ticket with NG if it likewise is self-signed.

Forum Discussion

Netgear Orbi RBK50 - Web certificate expired yesterday (Aug 2, 2019)