NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi App Bug with Firmware 2.7.1.60
I updated to Orbi firmware 2.7.1.60 last night and now when I go to view the devices connected to the Orbi via the Orbi app I get the following error. This happens on both my iPad and iPhone so it seems to be something related directly to the new firmware. Has anyone else experienced this? I tried googling this error and absolutely nothing comes up for it. So it seems tobe fairly new and unique. Plus there is a typo in the error message which is strange.
The error is:
Sorry, the action was failed. Please try again. (code: CDIL-API-FAIL).
Orbi App Error
Solved for me at least!
I downloaded to newest iphone app this morning and I can now access the Device Manager and see all devices with no error occurring! So finally fixed I think. I tried it both on my iphone and ipad and it works fine :-D I hope it's fixed for everyone now!
56 Replies
It would appear Netgear somehow addressed the situation. I did nothing to fix the problem of devices not being listed in the Orbi app, so I assume Netgear addressed it through an automatic firmware update. we'll see for how long.
I have an Orbi Mesh Network system I purchased from Costco back in August.
The network, and the app worked flawlessly until late October.
In late October, when both IoS and the Orbi App was updated, I lost all use of the App. A system reset, with re-naming the network and starting from scratch got things working again.
The app worked well for a couple of weeks. Now, it works for about 24-36 hours and the App quits working and says it can't find the network. (same issue as before).
However, if I unplug and re-plug in my main Orbi router, it does seem to also reset the app. So, at least it's a work-around, but it is pretty annoying. Any thoughts?
App is version 2.7.4.1.
IoS - 14.2
Thanks.
See my previous posting dated 12-15-20, message 38/54. If you are having problems with the iPhone Orbi app working after upgrading to Firmware 2.7.1.60 to the base router RBR50, I would recommend manually changing the firmware back to the previous version. There is a new beta version that corrects the problem, but until it is available, using the previous firmware 2.6.1.40 works. Contact Christian (post of 12-21-20) for more information.