Fix an offline UniFi AP or failed adoption

Goal and prerequisites

Restore management of an AP without losing a working configuration unnecessarily. The AP may be unpowered, unreachable, missing an IP address, associated with another management host or affected by an incorrect network change. Treat those as separate possibilities.

Have the AP model and MAC address, its expected switch port, a known-good patch cable, a compatible PoE source and a wired administrator computer. Record the last successful connection and the most recent configuration change. Do not start by forgetting every offline device; preserve the evidence and any working client service.

Work through the connection path

  1. Determine the scope. Check whether clients on the AP still work. If they do, investigate the management path first. If several APs went offline together, inspect their shared switch, gateway or Network host before treating each AP as a separate failure.
  2. Verify power. Inspect the AP indicator and switch PoE status. Check its required power mode and the overall budget using PoE switch or injector guide. Try the known-good approved power source and short cable. A disabled status LED is possible, so combine the light with port telemetry rather than using it as the only evidence.
  3. Verify Ethernet. Check the actual switch port and negotiated link. Trace the wall outlet to its patch-panel connection. For a meshed AP, verify that the parent is powered and has a working uplink before changing the child.
  4. Locate its address. Search the gateway DHCP leases and Network client/device lists by MAC address. WiFiman Discovery can help on the local network. An address from an unexpected subnet points towards an incorrect port assignment or another DHCP server. If the AP cannot obtain an address, investigate the access port and DHCP path. [1]
  5. Test the cable path safely. Temporarily replace the AP with a laptop connected to the same data path. Disconnect or bypass any passive injector first; connect the laptop only to a normal data port or suitable standards-compliant switch port. Check whether the laptop receives the expected lease and can reach its gateway. If it cannot, the fault exists before adoption. [1]
  6. Undo a recent management change. If the AP disappeared after a VLAN override, native-VLAN change or firewall edit, restore the previous switch-port and routing settings through your wired administration path. Keep an unchanged management port available. Re-establish connectivity before attempting another adoption. [2]
  7. Confirm the correct Network host. Open the existing console or OS Server instance for this site. Check that Network is running and supports the AP model. Installing a second management instance can create an empty site that does not own the AP. Restore the original host or its supported backup where appropriate. [3]
  8. Check local communication. For a custom host firewall or routed management path, verify the documented UniFi ports. Important examples include device-to-host TCP 8080, discovery UDP 10001 within the local network, and the applicable UDP 3478 communication. Scope rules to the actual device and host networks and consult the full reference. Do not expose the management service publicly merely to fix local discovery. [4]

Resolve adoption state

  1. Adopt a factory-ready device. If the correct AP appears as pending, compare its MAC address and select Adopt. Allow provisioning to finish. A repeated adoption loop merits another check of addressing, the host service and supported firmware before resetting the device.
  2. Handle another management owner deliberately. A device marked as managed elsewhere may still belong to the original site. If you control that site, restore its management connection or use the supported reassignment/migration process. If a reset is necessary, first record its important configuration and confirm the right device. [3]
  3. Use Layer 3 adoption only when required. A device separated from its Network host by a routed subnet needs the supported Layer 3 procedure. After establishing routing and required access, an authorised administrator can set the AP's inform destination to the actual Network host. For example, if that host is 192.168.10.5, the AP command is set-inform http://192.168.10.5:8080/inform. That example address must be replaced with the real reachable host; it is not automatically the gateway. Follow the official guide for the device's SSH credentials and complete adoption in Network. [5]
  4. Reset only after the path is understood. Follow the exact model's documented physical reset procedure while it is powered. A physical reset does not automatically remove its old record from the management application. Adopt it into the correct site and reapply the intended settings. [3]

Verify and retain evidence

Confirm the AP remains online, has the intended management IP and reports the expected uplink. Join each required SSID and verify its DHCP lease and allowed network access. Watch for repeated provisioning, restarts or disconnects during normal use.

If a factory-ready AP still fails on a short cable and a known-good supported power source, retain its model, firmware, port events and support information for escalation. Recovery mode is a separate model-specific process for cases that require it; it is not the first step for an ordinary VLAN or cable fault.

Sources

Back to the series

Leave a comment

Please note, comments need to be approved before they are published.