Services in IOT controller is offline even after hours
Summary
This article explains why services may remain in an offline or starting state for hours on a newly deployed vRIoT (Ruckus IoT Controller) instance.Question
Why are the services in an offline state for hours on a new vRIoT controller instance?
Customer Environment
Ruckus IoT (vRIoT)Symptoms
- A new vRIoT instance is deployed.
- Services do not come online even after 1–2 hours.
- The GUI displays: “Services are still starting”.
- Console access shows: “Application not running”.
Troubleshooting Steps
Checked console logs indicating the application services were not running.
Investigated network dependencies and confirmed ports required for service communication were blocked.
Resolution
To bring services online, ensure the following ports are open in the network:
- Port 123 (NTP) – Required for time synchronization
- Port 1883 – MQTT communication
- Port 8883 – Secure MQTT communication
Once these ports are allowed, the vRIoT services will start successfully.
Article Number:
000010132
Updated:
February 17, 2026 06:56 AM (3 months ago)
Tags:
Troubleshooting, Configuration, vRIoT
Votes:
1
This article is:
helpful
not helpful