NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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 ...
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.
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.
Hmmm. No error on my Windows 11 machine with Chrome:
I used http://orbilogin.net and http://192.168.1.1
Hi!
I'm getting the same error message when trying to login to my Orbi RBR50 with chromeos 120.
Anyone having a solution for this situation?
Regards
/RickardWhen a web browser complains "not safe" about the Orbi SSL certificate, I search for that tiny link near the bottom of the screen called "Advanced Options" (or something vague like that) and get to a choice of "go there anyway". Once the browser has been instructed to ignore the SSL certificate, it usually quits complaining about it.
I don't get that far...
After clicking "Advanced Options" I just get an empty page with the text below:
- The work around deleted the local state in the Chrome/Google folder did not correct my issue. Edge still worms. Any other ideas?
Have you tried deleting the beta version of Chrome and reinstalling the regular version?
One workaround without deleting the "Local State" file or using GPO to disable "RSAKeyUsageForLocalAnchorsEnabled" is to start Chrome with the field trial disabled:
chrome --force-fieldtrials=RSAKeyUsageForLocalAnchors/DisabledLaunch
The proper solution is to create a new certificate for the server with the key usage flag "Digital Signature" enabled.The background is explained for example here in the release notes:
https://support.google.com/chrome/a/answer/10314655?sjid=16333568074522698164-EU#chromBre116&zippy=%2CchromeA lot of work for Netgear engineering updating certificates, including the self signed ones, and distribute updated firmware all over.
Please distribute to all Netgear PMs and Engineers! Sorry for ruining the Xmas and New Year Holidays!
Will Netgear ever fix that sill certificate error?
Zworkon schrieb: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.
(...)Thanks for nothing! This "tip" is really bad. All locally stored logins are deleted, but it doesn't help at all. You could also have warned us that everything would be lost if someone deleted this file.
What really worked (Windows):
start "regedit" - insert:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]
"RSAKeyUsageForLocalAnchorsEnabled"=dword:00000000
Restart Chrome - voila!
greets,
mFor some reasons old bold, (and I admit not always wise) men are sometimes posting some comments worth reading before jumping the boat. That's why I said "One workaround without deleting the "Local State" file or using GPO to disable "RSAKeyUsageForLocalAnchorsEnabled" is to start Chrome with the field trial disabled..."
Yes, I'm doing my experiments on a virtual Linux environment, so calling chrome with some calling params was easier at that point.
The more complete information on the control of this wonderful new policy Chrome staretd to enforce - and available for all supported Chrome platforms - is here: https://chromeenterprise.google/policies/#RSAKeyUsageForLocalAnchorsEnabled
So navigating to HKEY_LOCAL_MACHINE\SOFTWARE\Policies in regedit and there is no Google folder/path, ergo no chrome folder/path and under Microsoft no Edge folder/path. Manually adding them and the registry values to them also does not resolve the issue for me. Windows 11 23h2 here.
I tried the registry flag you mentioned for Edge (not Chrome), and while it works (I'll tell you how after this caveat), you'll notice that when you go into your Edge settings, some options will no longer be available to you. There will be a message at the top of the screen saying that your browser is managed by your organization, or something close to that. I'm not sure if this is a permanent fix either, given that as I mentioned above, Google has indicated that for the Chrome solution (and Edge is based on Chromium like Chrome), it's a temporary fix for now to allow admins to fix their certs. They didn't specify how long this would remain tenable. Now that the caveat is out of the way, should you wish to actually enable that registry setting for Edge specifically, here is how you'd do it:
- Open regedit
- go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft
- Most likely, you will not see an Edge sub folder. That's because if you do, it means that your "organization" (aka you if it's your personal home machine) now will be in charge of setting certain browser settings (I elaborated a bit on that caveat above, I also don't know about all the possible other side effects managing it in this way has)
- If you do NOT see the Edge subfolder, right-click on the Microsoft folder (it's actually called a key but whatever, the icon looks like a folder), and select New->Key (I'd suggest doing this with Edge closed). Proceed to step 5.
- If you DO see the Edge subfolder (or you now see it because you made it in step 4), left click on the Edge subfolder. In the window on the right, right-click on any empty space, and select: New->DWORD (32-bit) Value and name it RSAKeyUsageForLocalAnchorsEnabled
- It should already preselect the name so that you can change it. If not, you can simply right-click on the name of the value you just created and choose "rename"
- The value by default should already be 0. If it isn't, simply double left-click the name, and change the value in the pop-up that appears to 0.
- THIS WILL NOT WORK UNTIL YOU REBOOT THE COMPUTER.
As for doing this for Chrome, it's the same basic idea. Source regarding the actual key for Edge: https://stackoverflow.com/questions/77519169/err-ssl-key-usage-incompatible-error-google-chrome-this-site-cant-be-reached-mi you have to skip past the actual answer (it doesn't apply to us in this case) and it should be right under it. As of this writing it has 6 upvotes and begins with the text "The equivalent Edge registry setting...."
And for Edge users, the same tip:
In Regedit, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge and manually add a new DWORD (32 bit) called RSAKeyUsageForLocalAnchorsEnabled and set it value 0.
Then reboot and et voila, Edge will work as well.
I tried firefox, that worked. I installed the beta firmware on the satellite, then the router. I factory reset both of them.
I'm setting up the router and I can't get it to pair with the satellite. I've tried wireless and wired modes. What's going wrong
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
