Loading
Xavier Boone

Build guides — UniFi

Deploying Your UniFi OS Server

The controller is where you push configurations, updates, and live visibility across your Ubiquiti gear. Here is where to run it, how to install it, how to adopt your devices, and how to force a clean DHCP renewal when you are done.

28 October 2026  ·  5 min read  ·  UniFi series  ·  Xavier Boone

To run this service properly, host it on a server that is on 24/7 and stays on-site. You can run it on a laptop or any device that isn’t always on and connected — it will install and work — but you forfeit features whenever that device is off or off the network.

The server is what pushes configurations and updates to your devices; the UniFi controller has no impact on the uptime of the network itself. Your internet keeps working whether the controller is up or not. What you lose without an always-on host is everything the controller does for you: you can’t remotely push configurations or updates, you can’t view the live network topology, and you can’t read live logs. The controller also stops logging historical traffic data and client metrics the entire time it is offline or disconnected — that gap in the record can’t be backfilled later.

The short version

Pick a box that stays on and on-site. The controller is a management and logging plane, not part of the data path — but every feature it offers assumes it is always reachable.

Step 1 — Install UniFi OS Server

  1. Once you’ve settled on where you’re comfortable deploying the server, head to the UniFi downloads page and find the UniFi OS Server build that matches your device and operating system.
  2. Download it and follow the installation instructions for your platform.
  3. Create a login and open your server dashboard.

Lock the account down while you’re here

  • Set up MFA before you do anything else.
  • Enroll two methods — one authenticator app and one other — so account recovery is actually possible if you lose a device.
  • The dashboard itself can only be reached from a device on the network.
  • As the admin, you manage logged-in devices and account-level security from account.ui.com.

Step 2 — Open Network and adopt your devices

From the dashboard, select the Network tab in the left navigation menu.

The UniFi OS left navigation menu: a vertical column of application and settings icons running down the side of the dashboard.
The left navigation menu — Network is one of the applications listed here

The Ubiquiti devices on your network will populate the list. Each one has to be adopted before the controller can manage it.

Top of the UniFi Network client-devices view, showing the site name Home.Lab, the Network tab selected, and the device table column headers: Name, Vendor, Connection, Network, WiFi, Experience, Technology, Channel.
The Network application — devices and clients populate here once adopted

Once everything is adopted, bring all devices up to date and renew every device’s DHCP lease so they come up clean on the managed network.

Step 3 — Force a DHCP lease renewal

Four ways to do it, fastest first:

  1. Power cycle the machines. Blunt, but it works.
  2. Unplug and replug the uplinks. Drops the link so the device re-requests on reconnect.
  3. Trigger the DHCP client over SSH. Log in and signal the BusyBox client to renew:
    killall -USR1 udhcpc
  4. Wait for the lease to expire. The device will request a new one on its own — the slowest option, but hands-off.

If a device won’t adopt

Adoption is where most first-time deployments stall. Ubiquiti’s own troubleshooting walkthrough covers the usual causes: Troubleshooting UniFi device adoption.

Step 4 — Create your first SSID

With your access points adopted, stand up a wireless network:

Settings → WiFi → Create New → Create

Name the network, set the security and password, choose which VLAN or network it lands on, and save. The controller pushes the configuration out to every adopted access point at once — which is the entire reason the always-on host is worth it.

#unifi #ubiquiti #homelab #networking #infosec

Discuss
Discuss on LinkedIn More build guides

Contact

Want this done properly on a business network?

A home controller and a managed multi-site deployment are different jobs. If you want the second one scoped — what you have, what it should look like, and what it takes to get there — start here.