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

/Rickard

---

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?

Hi James_MA,

Try using Firefox to update Firmware (Online update) and a factory reset is required after installing the patch firmware. Let me know if this fixes your issue.

NOTE: You can save a backup config file and restore it once the factory reset is done.

Kind regards,

ReneD Can confirm this fixed this issue for me in Edge and Chrome!!!! For statistics purposes, here are the browser versions I tested it with successfully (all are up to date as of this post, just checked).

Edge: v122.0.2365.66

Chrome: v122.0.6261.95

Firefox: v123.0

Tested with both Windows 11 23H2 and an old laptop (that can't run Win 11) running Windows 10 whatever is the most up to date version.

All 3 browsers now act as they did previously, which is good you connect, you get that same warning about trust etc., click advance and proceed anyway (depends on your browser the exact sequence but I assume by now everyone in this thread knows about this), and boom in you go to the GUI!

I will list a general suggested method to upgrade, as my specific set up is most likely way more complex than other people. If you're curious, my personal set up is this:

• ISP connects to commercial hardware firewall. This firewall also acts as the router.
• I have a Netgear MS510TXM switch that connects via the 10Gbps SFP+ port to the above firewall's 10Gbps SFP+ port. This is the central switch for everything on my network and numerous other ethernet cables connect here (PC, gaming devices, NAS, media server, other switches, etc)
• The Orbi SXK80, in AP mode, has its WAN port (the leftmost one, i.e. the one you'd just connect right to your ISP if you ran it in router mode) connected to the above switch.
• All 3 of my SXS80 satellites connect directly to the above SXK80 router via ethernet backhaul.

Take note of my specific product: these instructions only apply to my experience with my SXK80 and my three SXS80 satellites (2 that came bundled, 1 I bought later on). Also, be aware that I took an ultra paranoid approach to this given the firmware was described as being beta.

General suggestions:

1. BACKUP YOUR CURRENT SETTINGS: This will probably differ for each model, but for the SXK80, click on Advanced->Administration->Backup Settings and click the "BACK UP" button at the top where it says "Save a copy of current settings". Make sure this is on hand somewhere not requiring net access. Just put it on your desktop.
2. If you are rushing through this, you need to make sure you did step 1, unless you like to start everything from scratch and do things the hard way.
3. As per instructions, INSTALL THE FIRMWARE ON EACH SATELLITE FIRST. I did each one at a time. Yes, that took a while, but I was paranoid and wanted to ensure nothing went wrong.
4. Once you've updated all your satellites, now you can update the router.
5. Yes, you do have to do a factory reset. As a test, I tried connecting w/out doing so and obviously it didn't work. Before you factory reset, please keep reading.
6. I unplugged every satellite, so that at this point only the router was powered on.
7. Now I did the factory reset. Follow the instructions for your model. If you don't know how, it's in the user manual. For my model it was towards the bottom at the appendix area. Just search for "factory".
8. For my model, after the front LED blinked white (indicates booting up) for a while, it turned solid white for a while (indicates factory reset in progress).
9. I directly connected my ethernet cable from my laptop to the router (not sure if this is required or you can just use wifi, but I wanted to be extra careful)
10. I am not sure once it's solid white how long you need to wait but I got bored after a few minutes and decided to try connecting to the router. My model's factory default IP address is 192.168.1.1 so I opened Firefox (again, being paranoid, decided to keep using same browser as before, possibly not necessary) and connected directly to it. I then got the standard fresh out the box "let's set up your Orbi!" walkthrough.
11. Follow the set-up instructions and you'll quickly be given a choice to start from scratch, or here's why you should have read step 1, restore your router configuration from a backup file. I selected this option and uploaded the config from step 1.
12. I waited until the router was all done, verified I could connect with Firefox, then verified I could connect using Edge and Chrome (which previously wouldn't): it worked.
13. Again, probably being overly paranoid, but I plugged back in each satellite one-by-one. By that I mean I waited until the front LED on each satellite remained on for the 3m the manual says it will do, and then it eventually turned off, indicating successful connection to the router.
14. Profit. Issue resolved in Edge and Chrome with no regedit or other workarounds needed.

ReneD If you're curious, I have my router set to syslog everything to my NAS and got a bunch of warnings/errors the first time I powered on the first satellite (15 to be exact), after which point it seemed to reboot itself, gave me 3 more errors, and then fixed itself with no other errors at all. For the subsequent 2 other satellites, I simply got the same 3 errors instead of the initial 15. Once again, this didn't cause any problems: the satellites correctly fixed themself. If you want, I can send you the messages the syslog server sent me (just tell me the appropriate way to send them to you).

Once again, thanks!

ReneD Can confirm this worked. I posted a very detailed reply about what I did but for some reason said post got rejected and seems to be awaiting moderator approval after I edited it because an angry face emoji somehow accidentally appeared, I think due to how I ended my parenthesis.

Thanks for the information re Beta but is a Factory Default seriously required?   We have 2 kits each with 1 Router and 6 Satellites and that's a lots of time and effort to repare and set them up again  😞

Great the latest firmware automatically updated and the web page is now accessible again. Great job everyone!