How to Fix WiFi Not Working on Ubiquiti UniFi Access Points: Controller Adoption, Inform URL, and SSH Factory Reset Fixes

Ubiquiti UniFi access points are some of the most capable consumer and prosumer Wi-Fi hardware available, but their controller-based management model introduces a unique set of failure modes. An AP that “just won’t adopt,” shows “Adoption Failed,” or goes “Isolated” after an update can feel like a brick — even though the fix is usually a few commands away. This guide covers every common failure state in order from least to most disruptive to fix.

Understanding UniFi Device States

Before troubleshooting, it helps to know what each status actually means:

• Pending Adoption: The controller has discovered the AP on the network but has not yet claimed management of it. The AP is reachable and waiting.
• Adopting: The controller is actively trying to complete the adoption handshake. If it stays here more than a couple of minutes, the handshake has silently failed.
• Adoption Failed: The controller tried and failed — usually because the AP is already managed by a different controller, or the AP cannot reach the controller’s inform URL.
• Isolated: The AP is powered on and visible to another AP but has lost its uplink to the controller. Common with wireless-uplink (mesh) APs.
• Offline: The AP is not reachable at all — power or physical connectivity issue.

Fix 1: Verify Basic Network Reachability

Start with the basics. The UniFi controller communicates with APs on TCP port 8080 (inform) and uses layer-2 discovery (DHCP option 43 or mDNS) to find new devices. Both the controller and the AP must be on the same L2 broadcast domain, or you need a DHCP option pointing APs to the controller’s IP.

Find the AP’s IP from your router’s DHCP client list, then ping it from the machine running the controller: ping <ap-ip>. If the ping fails, the issue is physical — check the PoE injector or PoE switch port, the Ethernet cable, and the switch port status.

If the ping succeeds but the AP won’t appear in the controller, make sure the controller’s firewall (Windows Defender, UFW, etc.) is not blocking port 8080 inbound.

Fix 2: Manually Set the Inform URL via SSH

This is the most reliable fix for “Pending Adoption” and “Adoption Failed” states. SSH into the AP and manually tell it where the controller is:

ssh ubnt@<ap-ip>
# password: ubnt (default, unless changed)

set-inform http://<controller-ip>:8080/inform

The AP will acknowledge the command and appear in the controller’s device list within about 30 seconds. Click Adopt in the UniFi dashboard, then run set-inform a second time — the two-step handshake is required. The AP reboots, and the state changes to Connected.

If you’re running a UniFi Cloud Console (UDM-Pro, UDM-SE, or CloudKey), the inform URL uses HTTPS on port 443: https://<console-ip>:443/inform.

Fix 3: Fix Modern SSH Compatibility

Newer OpenSSH clients (version 8.8+) drop support for legacy RSA/DSS host key algorithms that older UniFi firmware uses. If your SSH connection is refused or immediately dropped, add the legacy algorithms explicitly:

ssh -o HostKeyAlgorithms=+ssh-rsa,ssh-dss ubnt@<ap-ip>

Once connected, run the set-inform command as above. To avoid typing this every time, add the following to ~/.ssh/config:

Host 192.168.1.*
    HostKeyAlgorithms +ssh-rsa,ssh-dss

Fix 4: AP Is Already Managed by Another Controller

“Adoption Failed” most commonly means the AP still holds credentials for a previous controller. The AP will only accept adopt commands from the controller it was last associated with — or from no controller at all (after a factory reset).

If you still have access to the old controller, go to Devices → select the AP → Forget (or “Remove”) in the old controller UI. The AP clears its controller binding and becomes available to adopt fresh.

If you don’t have the old controller anymore, SSH into the AP with the old controller’s SSH credentials (not the default ubnt/ubnt), then run set-inform pointing at your new controller. The AP will override its stored controller association.

Fix 5: Fix an Isolated Access Point

An isolated AP has lost its uplink to the controller but is still detected via another nearby AP. This happens most often with wireless mesh (uplink) configurations when the parent AP reboots or the uplink RSSI drops below threshold.

To recover a wired AP that is isolated: check the Ethernet cable and switch port. A flapping port causes repeated isolation events. If the port is healthy, go to UniFi Network → Devices → select the AP → Forget Device, then physically power-cycle the AP and re-adopt it.

For a wireless mesh AP that is isolated: move it closer to the parent AP temporarily, wait for it to reconnect, then update its placement. Wireless uplink APs need a signal level of −70 dBm or better at the uplink AP for a stable connection. See our guide on WiFi signal strength and dBm values for reference.

Fix 6: Physical Factory Reset

When SSH access is unavailable and adoption is completely broken, a physical factory reset is the cleanest path. All UniFi APs have a recessed reset button, typically located next to the Ethernet port:

1. Power on the AP and wait for the LED to stabilize (solid white or flashing white).
2. Press and hold the reset button for 10 seconds using a pin or paperclip.
3. Release when the LED begins flashing rapidly, indicating the reset is in progress.
4. Wait 2–3 minutes for the AP to reboot fully — the LED will return to a slow white pulse.
5. The AP reappears in the controller as a new “Pending Adoption” device. Adopt it normally.

After a factory reset, the AP uses default SSH credentials (ubnt / ubnt) until the controller pushes new credentials during adoption.

Fix 7: SSH Factory Reset (When the Button Is Inaccessible)

If the AP is ceiling-mounted and you can still SSH in, use the command-line reset instead:

ssh ubnt@<ap-ip>
set-default

The set-default command clears the AP’s configuration and reboots it into the same state as a physical reset. Avoid the older syswrapper.sh restore-default command on current firmware — it can leave the AP in a state where it is pingable but not SSH-accessible, requiring a power cycle to recover.

Fix 8: Firmware Mismatch

A firmware mismatch between the AP and the controller can silently prevent adoption. If your controller was recently upgraded to a major new version and the AP is running firmware from several releases back, the adopt handshake may fail without a clear error message.

After a factory reset, SSH into the AP and upgrade the firmware manually before adopting:

upgrade https://<firmware-download-url>

Current UniFi firmware files are available from Ubiquiti’s release page. Alternatively, in newer UniFi OS versions, the controller can push a firmware upgrade to an unadopted AP from the Devices tab by clicking the AP and selecting Update Firmware before completing adoption.

Quick Reference Checklist

1. Ping the AP from the controller machine — if it fails, check PoE and cabling.
2. Open firewall port 8080 (TCP) on the controller host if the AP is discoverable but won’t adopt.
3. SSH into the AP and run set-inform http://<controller-ip>:8080/inform.
4. Add -o HostKeyAlgorithms=+ssh-rsa,ssh-dss if modern OpenSSH refuses to connect.
5. Use the old controller to “Forget” the AP if it is bound to a previous controller.
6. For isolated wireless APs, move closer to the parent and let it reconnect, then reposition.
7. Factory reset (physical button or set-default via SSH) as a last resort.
8. Check for a firmware mismatch if adoption still fails after a reset.

Nearly every UniFi adoption problem falls into one of three categories: the AP can’t reach the controller (network issue), it still thinks another controller owns it (controller binding issue), or a firmware mismatch is blocking the handshake. Work through the checklist above in order and you’ll have your AP online. For ongoing network management tips, see our guide on setting up VLANs to segment your IoT and guest devices.