R610 stuck in Configure.Me mode

[ctay]

Hello.  My issue appears to resemble this previous post, but there wasn't a practical solution.

https://community.ruckuswireless.com/t5/Unleashed/R320-Unleashed-stuck-on-Configure-Me/m-p/52388#M47...

I have a "new to me" R610 with Unleashed 200.13.6.1.319.  Upon receipt I reset to default via button in rear.  Configure.Me-xxxxxx appeared but no device I tried was able to connect.  Using Ethernet, I was able to reach web GUI on 192.168.0.1 and was presented with initial setup.   For testing purposes, I simply made a new Wifi network called "TestWifi", finished the setup and rebooted.  Upon next startup TestWifi is not seen, but Configure.Me remains. 

No device was still able to use that SSID, so I again used Ethernet and browsed the GUI settings.  Everything appeared OK, but it did show zero working access points.  Tried setting to factory defaults again, but that had same issue.  Tried reflashing the same firmware and after reboot and setup, the same issue remains.  Access point appears stuck with Configure.Me and will not broadcast any other Wifi networks configured on device.  Any ideas?   

For reference I tried connecting to Configure.Me with two Win10 laptops, an older Win7 laptop, an iPhone with IOS 16.x and attempting to use the Ruckus app.  Also tried an Android tablet.  Nothing appears to connect to the  Configure.Me SSID, only Ethernet works.  Lastly, FWIW I also tried three diff power adapters that are known to work.

[ctay]

Update:  I may finally have it working.  TLDR: changed IP settings from DHCP to Manual - diff. subnet.

I reset to defaults again (from inside GUI), which still didn't help. Also tried reset to defaults from CLI via SSH (some claim you need to do this to truly reset), "set factory" command didn't work.  Then I tried flashing various supported Unleashed versions, which didn't take (upload successful, but didn't process and complete update).  

Finally I changed IP settings on AP from DHCP to manual and choose a different subnet (from 0.1 to 10.1).  AP immediately rebooted and oddly took almost 20mins to completely come up.  Once online I logged in and noticed the GUI finally showed an active and working access point.  No longer was Configure.Me broadcasting and I was able to create and see a new wireless network.  

Not sure if this AP is too flaky for long term use, but so far it's working.  I'll likely update this post again for those interested.

[sanjay_kumar]

Hi @ctay 
We are glad to hear that the issue is sorted out, I hope everything is working so far.
Please feel free to contact us if you need any assistance.

[ctay · Accepted solution]

Additional update:  AP appears to be working as expected.  The issue is still repeatable if the AP is reset to defaults - unable to connect to Configure.Me, zero working APs and configured Wi-Fi networks not broadcasting.  This was easily remedied by changing Admin/Services | System | IP settings from DHCP to Manual (same IP) and rebooting. Also, from a factory defaulted state, a restore of previously saved backup also puts AP in correctly saved config without need to change IP settings.