Hi  @ZoloNN 

Thanks for posting here.

The disconnection indicates that the device has lost communication with the controller. Under this condition:

Remote operations (including reboot) via the controller interface are impossible – "You can't cook without ingredients."

The remote reboot option only appears when the device is online and properly connected.

Note: Our community platform uses automated content filtering, which may occasionally flag legitimate posts as spam. If your post was incorrectly identified, you may message us or kindly wait for manual review by moderators (Typical processing time: 1-2 business days).

  @Vincent

No, he means the actual deviuce web GUI (the one that says, for example "WEB SERVER FORBIDDEN CONTROLLER SOFTWARE RUNNING" like on switches and gateways when you go to their IP

It desperately needs a reboot button since you can still log into them with the device user/password you set in omada

I have experienced similar with the gateways - they can sometimes get stick in a disconnected state, but the web gui of the device still thinks its in controller mode so you cant do anything until you physically power cycle, especially if you dont have SSH enabled (which has a reboot command)

upvoted

Hi @GRL,

exactly that I wanted to say.

Thank you for support.

Hi @Vincent-TP,

the problem is, when the SD-WAN is down, I'm out of any option to do anything on remote site.

As the VPN connection on remote site is still working, I can reach web interface of my remote gateway - but as controller on primary site can't connect to the remote site (no SD-WAN), there is no management/troubleshooting possibility....

if you lose connection to the site with controller - all your devices are converted to expensive paperweight pieces

And even last issue on primary site: controller thought the primary router is disconnected - and physical intervention (powercycle) was needed to restore normal operation.

  @ZoloNN  

@GRL 

Thank you for the explanation—I understand now. This is indeed a reasonable request. We appreciate the feedback and will document it to share with the R&D team.

Hi @Vincent-TP,

Thank you for your support and listening to the community.