topic Re: single Ruckus R350 always in Provisioning State in Unleashed

single Ruckus R350 always in Provisioning State

goech — Wed, 05 Nov 2025 15:36:20 GMT

I did set up a single ruckus r350 with unleashed and everything is working as expected. I have 3 Wifis in different VLANs and handle the management via the native VLAN1. I can access the management and all the Wifis work as expected in the different VLANs. But somehow the in the management website shows disconnected/provisioning - internet connection is there. Is it because I only have one R350 or do I have to up something more?
I allowd Port 80/443 and 123 outbound on the firewall for the AP. One thing I see is there are some request from the AP on port 60000 but I dont know what this is - allowing it also didnt improve the situation. One thing I do, I use ubnound as DNS - maybe there could be an issue?

I already made an firmware upgrade to 200.18.7.101.244 and did an Firmware reset. Still the issue persists. Any help would be appreciated.

Re: single Ruckus R350 always in Provisioning State

sanjay_kumar — Thu, 06 Nov 2025 07:31:34 GMT

Hi @goech,

Are you referring to the Internet Status on the Dashboard page?
Or are you referring to the "Status" section on the Access Point page?
Could you please share the screen shot?

By default AP will use the below sites to check the internet status. Probably you need to allow these 2 websites in the firewall. Or can also disable the "Internet Status" check from CLI. Follow the below link to disable.
captive.apple.com
www.microsoft.com
www.baidu.com

https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/DNS-Requests-to-baidu-com-from-Unleashed-AP/m-p/39502

Re: single Ruckus R350 always in Provisioning State

goech — Fri, 07 Nov 2025 21:53:52 GMT

I am referring to the AP status. The internet status is fine, I was able to do the firmware update with it.

Here a screenshot:
https://imgur.com/a/Aiowr01

In the upper right corner the ap is read and tells me as status not connected/provisioning.

Re: single Ruckus R350 always in Provisioning State

goech — Sat, 08 Nov 2025 06:09:00 GMT

I just checked all pages and one thing I am wondering is: in the upgrade view the ap is in the state downloading update all the time - is this as expected? https://imgur.com/a/9elP1e4

Re: single Ruckus R350 always in Provisioning State

sanjay_kumar — Mon, 17 Nov 2025 06:37:50 GMT

Hi @goech,

When you switch to Access Points Page, what is the status of the AP?
Does it say Online?

The page is stuck in Upgrade stage, which is causing the AP to show as Not connected.
This happens if the AP is able to detect another Master in the network or the AP is stuck in upgrade loop.

I believe there is no other AP in the premises, have you tried rebooting the AP by any chance?

Re: single Ruckus R350 always in Provisioning State

goech — Mon, 17 Nov 2025 13:23:47 GMT

When I Switch to the Acces Points Page it tells me "Provisioning".
I only have one master in the Network. I did restart the AP many times and I also did a factory reset on the Access Point but the problem still persists.
For Information what happened when I upgraded: When I did the upgrade first via Network it did fail, then I uploaded the binary blob directly and it did upgrade (saw the new version appear) but it didnt quit the mode (was still showing the state "downloading update".

Re: single Ruckus R350 always in Provisioning State

goech — Wed, 07 Jan 2026 06:09:32 GMT

So after a month I still have this problem are there anh more ideas how to fix this?

Re: single Ruckus R350 always in Provisioning State

jp — Fri, 20 Feb 2026 21:40:11 GMT

Btw, same here: I played around wit a single R770 (Unleashed 200.18.7.101.244) in a subnet, fresh reset, quick setup -> AP stays in Status "provisioning" (see screenshots). I cannot edit the AP either. IT is connected to the Internet and connects Wifi clients, etc.
(I am not much after a fix, I just experimented a bit with Wifi7, the AP is not productive)

Re: single Ruckus R350 always in Provisioning State

goech — Sat, 28 Feb 2026 07:43:38 GMT

Okay so after some time and several restart it does go green again, now I could check the aps and found this (maybe its helps to find the root cause?): this are the events from the day it stopped working