Updates are part of everyday UniFi life: they bring new features, fix bugs and close security holes. At the same time, nobody wants the Wi-Fi to drop in the middle of the workday because an access point decided to install new firmware. The good news: with a little planning, you can organize UniFi updates so that hardly anyone notices them. This guide shows you where updates are managed, which release channels exist, why a backup comes first and how to fix common update problems – based on Ubiquiti’s official documentation.
Two kinds of updates: software and device firmware
With UniFi, you’re essentially updating two different things:
- Console and applications: UniFi OS on the console (e.g. a Cloud Gateway or CloudKey) or on UniFi OS Server, plus the applications running on it – first and foremost UniFi Network.
- Device firmware: the firmware of managed devices such as access points, switches and gateways. According to Ubiquiti, UniFi device updates are found within the settings of their associated application.
This distinction matters for planning, because each type of update affects day-to-day operation differently.
Controller updates: your network keeps running
A common misconception is that updating the controller software takes the whole network down. For the self-hosted UniFi Network Server, Ubiquiti states clearly: while the Network application is being updated, your network continues to function as normal – devices remain connected with internet access, and traffic continues to be routed. The same principle applies to UniFi OS Server: if it goes offline, your devices keep running with the last available configuration.
On the Network Server, running instances of the application are closed before installation, so the management interface isn’t available during that time. Actual network operation, however, doesn’t depend on the controller software running.
Device firmware: this is where planning counts
Device firmware is a different story. While a device installs its firmware, Ubiquiti says the status LED on access points, switches and routers flashes quickly white/blue – with an explicit warning not to interrupt the process. (The UDM base model flashes only white during an upgrade.)
Ubiquiti’s Recovery Mode documentation shows why this matters: an unresponsive UniFi device is often the result of a power loss occurring at the same time as an update. Ubiquiti points to UniFi Power Backup as a way to prevent unexpected power losses. For you, that means: never start firmware updates while someone is working on power, PoE switches or cabling.
To keep users from noticing anything, a few simple rules have proven useful:
- Use a maintenance window: run firmware updates outside business hours or during a quiet period instead of triggering them on a whim mid-morning.
- Don’t update everything at once: update a single, non-critical device first, check it, then roll out the update to the remaining devices.
- Critical devices last: the gateway and core switches affect every user. Schedule them for a time when a short interruption won’t hurt anyone.
- Have someone available on site: if an update causes trouble, it helps if someone can physically reach the device.
Where to manage updates
Centrally: Update Manager in Site Manager
Ubiquiti describes Update Manager as the centralized hub for viewing and managing all updates across your UniFi deployments. It’s part of Site Manager and available on the web at unifi.ui.com and in the UniFi mobile app. If you look after several sites, this gives you a single overview. Learn more in our guide UniFi Site Manager explained.
Locally: auto-update and release channel
According to Ubiquiti, this is how you configure auto-updates and the release channel – it also works if remote management is disabled and you don’t have access to Site Manager:
- Connect to the site, via Site Manager or local management.
- Navigate to Settings > Control Plane > Updates.
- Click your UniFi console or UniFi application.
- Select the release channel and/or configure auto-update settings.
Ubiquiti explicitly recommends that most users enable automatic updates or trigger updates through the user interface. According to Ubiquiti, updates can also be scheduled and monitored through the UniFi Network application – which is the key to placing them in your maintenance window. Release notes for all updates are published at community.ui.com/releases; checking them before larger version jumps is worth it.
Official or Early Access?
UniFi offers two release channels: Official and Early Access. Early Access gives you early access to upcoming features and improvements. To use it, Early Access must first be enabled in your UI account at account.ui.com, then in Site Manager via the profile icon. Only then can site owners with the appropriate permissions select the Early Access channel for UniFi OS and applications under Settings > Updates.
For production business networks, the Official channel is the obvious choice. For the self-hosted Network Server on Linux, Ubiquiti itself “strongly” recommends staying with the stable release. If you only want to test Early Access firmware on individual devices, Ubiquiti lets you paste a firmware link from community.ui.com/releases into the settings of the device’s properties panel – and return to an official release the same way.
| Release channel | Suitable for | Note |
|---|---|---|
| Official | Production networks, business sites | Default channel, no extra opt-in needed |
| Early Access | Test environments, individual test devices | Must be enabled in your UI account and in Site Manager |
Before you update: back up
A current backup is your safety net if something doesn’t work as expected after an update. On consoles such as Cloud Gateways and CloudKeys, enable automated system backups under Settings > Control Plane > Backups (“System Backups”). According to Ubiquiti, a cloud backup is then generated automatically every week – and prior to each major update. Only the owner can manage these backups, because they’re saved to their UI account; you can view them at account.ui.com/backups. If you can’t use cloud backups, download a local offline backup from the same place.
For the self-hosted Network Server, Ubiquiti recommends downloading a backup file from the system settings when updating; on Linux installations, the database should be backed up before upgrading. Our guide UniFi controller backup & restore explains backup and recovery in detail.
Special case: self-hosted controllers
If UniFi Network runs on your own server, different rules apply:
- Legacy UniFi Network Server: according to Ubiquiti, updates must be manually checked for and initiated each time. If the server runs a version prior to 8.6, you need to update it manually. On Windows and macOS, the update is downloaded on the original host machine and running instances of the application are closed first. On Debian/Ubuntu, updating via APT is possible – according to Ubiquiti, only for users with appropriate Linux knowledge.
- UniFi OS Server: the successor can be updated like a console, via Update Manager in Site Manager or locally in the Control Plane settings.
On top of that, self-hosting means you also handle operating system and server environment updates yourself. For a comparison of the options, see our guide UniFi OS Server: self-host or cloud?.
When an update fails
If an update fails or doesn’t start at all, Ubiquiti recommends these checks:
- Check internet access: devices must be online for updates. Offline updates are possible using the Update Cache method.
- Verify DNS settings: use reliable DNS servers such as 1.1.1.1 or 8.8.8.8.
- Ensure port access: UDP 53 and UDP 123 must not be blocked by your gateway or ISP.
- Contact your ISP if it blocks required ports.
The Update Cache is useful beyond troubleshooting, too: you store a device update once in the Network application’s system settings, and other devices use it from there instead of each downloading it from the internet. Ubiquiti recommends this for networks with many similar devices and for setups where the management network has no internet access.
Updating via SSH, on the other hand, is not an officially supported process according to Ubiquiti and may prevent a console from functioning. Ubiquiti advises using it only at the request of UI Support. If a device stops responding entirely after a failed update, Recovery Mode is the last resort – try a reboot and a factory reset first.
Checklist: updates without downtime
| Step | What you do |
|---|---|
| 1. Read release notes | Check changes and known issues at community.ui.com/releases |
| 2. Back up | Automated system backups enabled, or download a manual backup |
| 3. Check the channel | Run production sites on the Official channel |
| 4. Pick a time | Set a maintenance window outside core business hours |
| 5. Go step by step | Controller/application first, then one test device, then the rest |
| 6. Don’t interrupt | No power disconnects while the LED is flashing quickly white/blue |
| 7. Verify | Check that all devices are back online and adopted |
Conclusion
Updating the controller software doesn’t interrupt your network – devices keep working with their last configuration. The critical part is the device firmware itself. With a backup, the Official channel, a fixed maintenance window and a step-by-step approach, you can handle those updates too. If you’d rather not deal with controller updates, backups and operations yourself and are looking for a managed UniFi controller hosted in Germany, get in touch with clevendo.
Frequently asked questions
Will my network go down when I update the UniFi controller?
No. According to Ubiquiti, your network continues to function as normal while the Network application is updated: devices stay connected and traffic keeps being routed. The management interface isn’t available during installation, though.
Where do I configure automatic updates?
Under Settings > Control Plane > Updates: select the console or application and configure auto-update and the release channel. UniFi device updates are found in the settings of their associated application. For all sites at once, use Update Manager in Site Manager.
Should I use Early Access on production networks?
For production sites, the Official channel is the safer choice. Early Access is suited to trying out new features in a test environment or on individual devices.
What does a quickly flashing white/blue LED mean?
The device is currently upgrading its firmware. Ubiquiti advises not to interrupt the process – so don’t disconnect power or PoE during this time.
Does UniFi create a backup automatically before updates?
If you’ve enabled automated system backups under Settings > Control Plane > Backups, yes: according to Ubiquiti, a cloud backup is generated every week and prior to each major update.
Why does my UniFi update fail?
Common causes are missing internet access, unreliable DNS servers or blocked ports UDP 53 and 123. Ubiquiti recommends checking these points in order and contacting your ISP if necessary.



