This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I tried to login to my network via the APP and it kept asking for my password like I had it wrong or something. I then went to a desktop and tried to log in and found that it has a dialog box wanting me to enable circle. I do not need circle as it is just my wife and I. I click out the x in the upper left of dialogue box and to close it (like I have in the past). It then gives me a 400 bad request.
I’ve ran into issues in the past where I don’t see why you would have to split as what I had to do was turn off my 5 GHz until my 2.4 cameras connected and then once it was configured I turned on the 5 GHz and everything worked fine. So another words I didn’t have to split it I just had to turn off the 5 GHz once connected to the 2.4 everything is fine
I tried to login to my network via the APP and it kept asking for my password like I had it wrong or something. I then went to a desktop and tried to log in and found that it has a dialog box wanting me to enable circle. I do not need circle as it is just my wife and I. I click out the x in the upper left of dialogue box and to close it (like I have in the past). It then gives me a 400 bad request.
It never asks for a username or password. I pops us as if I am logged in. Behind the dialoge box I can see the left menu with the Basic tab selected. However I am unalbe to click on anything other than the X, "Learn More", or "Enable" all part of the dialoge box.
Everything in the background has is fadded and unable to interact.
Oh, I also tried with the APP on my phone and it just keeps asking for my password and never logs in.
Well, fooey. It's time to clear the browser cache or change to a different browser. I let my browser "save" my Orbi password (because I open the web interface at least 20 times a day) but it still asks me to press <Enter> before letting me in. However, there IS a "time out" because I can close the window and get back in without entering the password only for something like five minutes.
You don't by any chance have more than "window" open on the browser? For example, when I click on "Connection Status", that opens a new web window that stays even if I close the connection to the Orbi. Not another "tab". But, it's definitely there.
Update went well, it took a bit to settle down and my devices connected back up. The only issue I have is not being able to update the device names via the UI or the Orbi app. The first few I made worked, but then they stopped updating.
Wow, is there any way to roll this back off??? As stated here, my IPTV is now no longer working reliably. And, all of my named devices are randomly messed up. For example, it says one of my cell phone is on a "wired" connection. My Vonage box (wired) is wireless, etc. This is a really bad release.
I just downloaded V2.3.5.30 manually and put my RBR50 and RBS50 both back to that. All my labels are back, and I think IPTV is better. Hopefullyt hey figure it out, I'm not touching V2.3.5.30 again.
FW is JUNK.... DO NOT UPGRADE if you have separate SSID names. It will override it.
Of all the BASIC settings separate names for each SSID is often required. This FW defeats that purpose. I have IoT 2.4 ONLY devices that refuse to connect and stay connected to a common named SSID.
I just downloaded V2.3.5.30 manually and put my RBR50 and RBS50 both back to that. All my labels are back, and I think IPTV is better. Hopefullyt hey figure it out, I'm not touching V2.3.5.30 again.
Thank you, and well done.
I can do this rollback as well, but I'm worn out and need to take a break from this stuff, and also re-evaluating the situation as trust has been lost.
My IPTV had been acting spotty anyway, so unless IGMP is made to work correctly, including through the satellite, I'm just not going to touch it.
I just downloaded V2.3.5.30 manually and put my RBR50 and RBS50 both back to that. All my labels are back, and I think IPTV is better. Hopefullyt hey figure it out, I'm not touching V2.3.5.30 again.
How do you rollback on the RBR50 ? I rolled backed on the RBS50 but I see no way to do that with the RBR50. I just see a uplload and upgrade the RBS50.
Did you at least try a factory reset on the RBR after upgrading to v38 to see if this resolved your problem? I don't have IPTV here so I can test for this. I do have DISH Hopper system and having two Joeys connected via ethernet to the Hopper is working here for me. Though I think DISH protocols differ from IPTV protocols.
Wow, is there any way to roll this back off??? As stated here, my IPTV is now no longer working reliably. And, all of my named devices are randomly messed up. For example, it says one of my cell phone is on a "wired" connection. My Vonage box (wired) is wireless, etc. This is a really bad release.
Update went well, it took a bit to settle down and my devices connected back up. The only issue I have is not being able to update the device names via the UI or the Orbi app. The first few I made worked, but then they stopped updating.
Wired or wireless? Mines currently wired though I did test my RBS which is in the basement here and it connected wirelessly to my RBR two stories up. Seems to take about 4-5 minutes to complete the task after hitting the sync button on the RBR in the UI then button on the RBS.
Has a factory reset and setup from scratch been performed since last FW update on both RBR and RBS?
Wired or wireless? Mines currently wired though I did test my RBS which is in the basement here and it connected wirelessly to my RBR two stories up. Seems to take about 4-5 minutes to complete the task after hitting the sync button on the RBR in the UI then button on the RBS.
Has a factory reset and setup from scratch been performed since last FW update?
Whats the distance between the RBR and RBS?
Try syncing the RBS in the same room as the RBR to check this. Give up to 5 minutes for the RBS to complete the sync. Look at the top LED of the RBS while it's syncing. BLUE should be seen then it should go out. Check the RBSs web page to see if the SSID is the same as the RBRs. It should be.
