NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Firmware v2.5.1
New version available. Based on the description, doesn’t seem worth the disruption. New Version: V2.5.1.8 Release Notes: [Bug Fix] Fixes JP/AU/CA region can't firmware update issue. [Bug Fix] F...
The first issue I'm experiencing with firmware 2.5.1.8 is the inability to turn on remote management from the app. I can enable it from the web interface but the app does not allow me to enable it so I can access my Orbi remotely from the app. I did a full restore back to factory settings before applying the update.
I receive the following error:
"Some error occured while enabling/disabling remote management"
For those that have installed v2.5.1.8 firmware, have you checked to see if the https certificate is updated to be properly signed by a certificate authority? Does opening https://orbilogin.net/ open as a secure web site in your web browser? Can you check the certificate for when it will expire again?
tomschmidt wrote:For those that have installed v2.5.1.8 firmware, have you checked to see if the https certificate is updated to be properly signed by a certificate authority? Does opening https://orbilogin.net/ open as a secure web site in your web browser? Can you check the certificate for when it will expire again?
Chrome complained, so it still appears broken to me.
On the device renaming issue, it appears the icon choices between the browser UI and ios app are not all there. This will break updating one versus the other. As an example, I have a TP Link smartplug HS100 which the browser UI identified correctly but the ios app viewed as generic. I changed the browser side to a light (what's actually controlled by the smart plug), and the change then reflected back to the ios app.
The browser UI also has provisions for changing two fields for descriptors, whereas the ios app only displays and edits one of them. This is another issue that is causing problems in being able to properly identify devices.
So close...
Has anyone seen any release notes form 2.5.1.8?
gr8sho, In Chrome, can you click on the red "Not Secure" in the URL line at the top and then select "Certificate" to see the date range that the certificate is valid? I am curious if it is the expired certificate still as seen with v2.3.5.30 and v2.5.0.38, or if it is the self-signed certificate (thus still not trusted) as seen in the v2.3.5.34 and v2.5.0.40 releases, or if it is yet another certificate... You can also click the "Details" tab and copy and paste its contents to your reply.
gr8sho wrote:
tomschmidt wrote:For those that have installed v2.5.1.8 firmware, have you checked to see if the https certificate is updated to be properly signed by a certificate authority? Does opening https://orbilogin.net/ open as a secure web site in your web browser? Can you check the certificate for when it will expire again?
Chrome complained, so it still appears broken to me.
tomschmidt wrote:gr8sho, In Chrome, can you click on the red "Not Secure" in the URL line at the top and then select "Certificate" to see the date range that the certificate is valid? I am curious if it is the expired certificate still as seen with v2.3.5.30 and v2.5.0.38, or if it is the self-signed certificate (thus still not trusted) as seen in the v2.3.5.34 and v2.5.0.40 releases, or if it is yet another certificate... You can also click the "Details" tab and copy and paste its contents to your reply.
gr8sho wrote:
tomschmidt wrote:For those that have installed v2.5.1.8 firmware, have you checked to see if the https certificate is updated to be properly signed by a certificate authority? Does opening https://orbilogin.net/ open as a secure web site in your web browser? Can you check the certificate for when it will expire again?
Chrome complained, so it still appears broken to me.
Still appears to be boken on Safari despite having instlled the fix
