Device showing offline in UniFi? here’s what it actually means

You log into your UniFi Controller and notice one of your devices is showing as “Offline.” Before you start yanking cables or planning a replacement order, it’s worth knowing that “Offline” in UniFi doesn’t always mean the device is dead. It could be a small hiccup, a miscommunication, or something more serious, but it's almost always fixable.

Let's dive in !!

what does “offline” mean?

In UniFi, “Offline” means the device hasn’t checked in with the controller in a while. Most UniFi gear pings the controller regularly. If the controller doesn’t hear back within a certain window, usually 1 to 2 minutes, it marks the device as offline.

It doesn’t mean the device is completely dead. It could be:

• The device is up but can’t talk to the controller
• The controller is down or unreachable
• There’s a temporary network problem
• The device is rebooting or stuck in an update

the usual suspects: why it happens

1. power problems

This is the simplest and most common reason.

• No LED = no power. Check the PoE switch or power adapter.
• Flashing LED = booting or firmware issue.
• Solid LED but offline = could be stuck mid-boot or can't reach controller.

Make sure the device is getting power and try a reboot.

2. network issues

Even if the device has power, it might be on the wrong VLAN, subnet, or isolated by firewall rules.

• DHCP might have failed.
• The switch port might be misconfigured.
• VLAN tags might be stripped or incorrect.

Use a tool like UniFi’s Device Discovery Tool or Fing to see if it’s actually on the network.

3. inform URL is broken

Every UniFi device phones home to the controller using an “inform URL.” If that URL is wrong, it’s as if the controller doesn’t exist to the device.

This often happens after moving a device from one controller to another, or after a restore.

To check and fix it:

1. SSH into the device
2. Run:
   bash

   mca-cli
   set-inform http://<controller_ip>:8080/inform
   

If that doesn’t help, a full reset and re-adopt is usually faster.

4. firmware failed or stuck

Devices can get stuck during a firmware update. If you powered off an access point mid-upgrade, it may be stuck in a boot loop.

Options:

• Reboot it and see if it recovers.
• SSH in and check the firmware version.
• Use recovery mode to manually flash a clean firmware image.

5. controller problems

Sometimes, it’s not the device. The controller might be:

• Offline
• Outdated
• Running a different version than the device
• Broken after an update

If the controller went down during a firmware rollout, devices can show offline even when they’re fine.

Restart the controller service or the server/VM it’s hosted on.

how to fix it, step by step

step 1: check LEDs

A quick visual check tells you a lot. If there's no light at all, it's a power issue. If it's blinking, it's trying to boot. Solid lights usually mean it's on and waiting.

step 2: reboot the device

Unplug and replug the Ethernet cable. For PoE devices, that’s enough to restart. If it doesn’t come back, try a different port or cable.

step 3: try SSH access

If you’ve enabled SSH on your devices, login and check system logs or ping the controller manually.

If SSH fails, it's likely a network or power issue.

step 4: check the controller

Make sure the controller is online, accessible, and running the right version. Try accessing it from another device or browser.

Also, double-check if it's reachable remotely if you're off-site.

step 5: reset and re-adopt

If nothing works:

1. Hold the reset button for 10–20 seconds until the LED flashes
2. Reboot and wait for the device to show in the controller
3. Re-adopt it with the correct inform URL

step 6: firmware recovery

If it's still not coming back, flash the firmware manually.

• Put the device into TFTP recovery mode (usually by holding reset at boot)
• Push firmware using TFTP from a local machine
• Let it boot and re-adopt

common scenarios and solutions

access point offline after power cut

Try re-seating the cable or replacing the PoE injector. If the switch port is dead, move it.

switch offline but still powering devices

Check uplink cable. The switch might be working locally but not connected to the controller.

device shows “disconnected” and won’t adopt

Probably a stale inform URL. SSH in and manually set the inform again.

multiple devices offline after an update

Check if the controller version is compatible with device firmware. Try rolling back if needed.

pro tips to avoid offline headaches

• Always use static DHCP leases or static IPs for key devices
• Avoid rebooting controllers during firmware updates
• Make backups of controller configs before updates
• Use UniHosted if managing client networks, updates and access just work
• Label your cables, switches, and ports, it makes debugging easier

when it’s time to replace the device

Some hardware failures do happen. Signs it’s time to RMA:

• No power even after multiple ports and injectors
• No SSH access despite being pingable
• Won’t adopt even after reset and firmware reflash

If it’s still under warranty, file a ticket with Ubiquiti. If not, time to order a replacement.

final thoughts

“Offline” doesn’t always mean your UniFi device is broken. It usually means it can’t reach the controller for some reason, power, network, or software-related. Follow a few logical steps, and you can usually bring it back in minutes.

But if you're tired of chasing offline messages across multiple sites, let us handle the controller for you. At Unihosted, we provide a stable, scalable cloud-based controller so your focus stays on the network, not fighting with updates or downtime.