NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Zworkon
Nov 22, 2023Aspirant
Chrome Certificate
After the latest updates with chrome, The certificate is not secure and I get this: This site can’t be reached The webpage at https://192.168.x.x/ might be temporarily down or it may have moved ...
- Nov 22, 2023
Here is the solution I found:
We found a fix. Delete the user's local state file located in C:\users\(username)\AppData\Local\Google\Chrome\User Data\Local State. After deleting it the issue went away. Let me know if that works for you.
EDIT: Confirmed this is also happening on MacOS. Need to go to Library/Application Support/Google/ and Delete the Local State file from their as well.Thanks Everyone.
James_MA
Feb 11, 2024Initiate
chrome --force-fieldtrials=RSAKeyUsageForLocalAnchors/DisabledLaunch does not work in my pc, and I can only connect with safari in my iphone.
There has no firmware update so far, may I know if there has any workaround?
schumaku
Feb 11, 2024Guru - Experienced User
James_MA wrote:
chrome --force-fieldtrials=RSAKeyUsageForLocalAnchors/DisabledLaunch does not work in my pc, and I can only connect with safari in my iphone. ... may I know if there has any workaround?
What OS, what browser, and what version please?
- CrimpOnFeb 11, 2024Guru - Experienced User
Perhaps I am not doing it correctly. Windows 11 Pro. trying to open https://orbilogin.net or https://192.168.1.1
Entering URL: https://192.168.1.1/--force-fieldtrials=RSAKeyUsageForLocalAnchors/DisabledLaunch
Results in this:
Opera:
Firefox: https web site opens after warning about self-signed certificate.
Edge:
- schumakuFeb 11, 2024Guru - Experienced User
Heya CrimpOn
Looks like you are mixing several different issues and models. The --force.... is a parameter to be passed to Chromw on start-up from the command line, not magicallly added to any URL.
Around the Christmas days, I've posted refering to what I understand are Netgear people able to read and understand the problem here. Almost three months later Netgear is -unable- to create and distribute self-sighed certificates with the new mandatory (by more and more modern browsers) inlcuding the new certificate attribute. If Netgear is unable to read, unable to listen, and obviously not even able to ASK in case they don't understand.
Fits perfect to the new nightmare they caused with distributing untested beat (or more QA-code, under the flag of an SSO idea) to some RAX50v2, and more RAX4xv2, ....
I'm serously disappointed: Even the CTO (I've sent emails, PMed on LinkedIn, ...these days) keeps silent and does not show any signs or a reaction.
Reagrds,
-Kurt
...no idea what for I'm wasting my time here. There is -nothing- coming back from Netgear, they are simply abusing the free knowledge.
- CrimpOnFeb 11, 2024Guru - Experienced User
schumaku wrote:
The --force.... is a parameter to be passed to Chromw on start-up from the command line, not magicallly added to any URL.
I remain happy to use http to access the Orbi web admin and tell browsers to ignore the "not secured" error. From what I can see, the current versions of:
- Chrome
- Edge
- Opera
Simply will not connect to my RBR50 https web admin, even after saying to accept the self-signed SSL certificate. Whereas Firefox continues to connect after complaining about the self-signed SSL certificate. Which could indicate it may be only a matter of time before Firefox also declines to connect.
Which would seem to indicate that enabling that option to require secure access would immediately lock the user out of the router (unless one of the more exotic, less used web browsers has not kept up with standards).
- schumakuFeb 11, 2024Guru - Experienced User
Not a refernence, however using the ubiqutous Chrome Version 121.0.6167.161 (Offizieller Build) (64-Bit) and Firefox 122.0.1 (64-bit) [admit to allow using legacy devices, I have changed the security.tls.version.min to 1] allow the access e.g. to a bunch of WAX6xx and WAC5xx using https flawless, after accepting the self-signed certificate as usual CrimpOn
- James_MAFeb 12, 2024Initiate
OS: Windows 11 Pro 23H2
Browser:
Chrome Version 121.0.6167.161 (Official Build) (64-bit)
Microsoft Edge Version 121.0.2277.112 (Official build) (64-bit)
Same error in both Chrome & Edge
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!