Firmware Updates: Best Practices

On a hosted i2unifi server, we run firmware updates for you by default — the Ubuntu host, UniFi OS, and on-site UniFi devices — unless you prefer to manage the schedule yourself.

What i2unifi handles (default)

1. Ubuntu server — host OS maintenance on your VM
2. UniFi OS / controller application — platform updates on your instance
3. Device firmware — gateways, switches, and access points adopted to your controller

We follow a safe order: backup → controller → gateway → switches → access points, and we avoid risky timing (for example end-of-week bulk upgrades without a rollback plan).

If you self-manage upgrades

If you asked to run your own schedule:

1. Read release notes before approving anything in Devices → Updates
2. Download a backup before major upgrades
3. Upgrade controller, then gateway, switches, then APs
4. Test on a pilot device before fleet-wide rollout

Tell i2unifi support if you want to switch between managed and self-managed upgrade policies.

During any upgrade window

• Brief WiFi or VPN interruptions are possible — we notify when maintenance is planned
• Watch Devices → Updates for failed or retrying jobs
• Keep physical access to critical gear if remote access drops mid-upgrade

If something goes wrong

• Note the previous firmware version from device properties
• Contact i2unifi support with device model, target firmware, and error text from the UI
• Restore from backup if configuration corruption is suspected (see Backing Up and Restoring UniFi OS)

Tips

• Keep automatic UniFi backups enabled even when we manage upgrades
• Match device firmware to a supported UniFi OS version — we check compatibility before rolling forward
• Open a ticket if you need upgrades paused before a conference, holiday, or go-live event