Routers · Ubiquiti
Ubiquiti Router Can't Connect New Devices
When existing clients stay online but new phones, IoT accessories, or laptops refuse to join your Ubiquiti network, the issue usually stems from DHCP pool exhaustion, WPA3/PMF security mismatches, or controller provisioning glitches.
Symptoms
- New devices get stuck on 'Obtaining IP address...' or 'Authenticating...'
- Client devices report 'Incorrect Password' despite using the verified Wi-Fi passphrase
- Smart home/IoT accessories fail initial pairing on 2.4GHz networks
- Existing devices stay online normally while all newly added devices fail to join
- UniFi Network Controller logs frequent DHCP timeout or AP association errors
- New client connects for 2 seconds, then immediately disconnects without internet
Quick troubleshooting
Step 1
Check and Expand the DHCP Scope
Log into your UniFi Controller or EdgeOS dashboard, navigate to Networks, and verify your Subnet mask and DHCP Range. If your pool is full due to short-lived randomized MAC addresses, expand the IP range or shorten the lease duration from 24 hours to 8 hours to free up leases immediately.
Step 2
Disable PMF and Lower Security to WPA2 Personal
Open your Wireless Network settings in the UniFi Console and change Protected Management Frames (PMF) from 'Required' to 'Optional' or 'Disabled'. Additionally, temporarily lower security from WPA3 to WPA2-PSK to rule out handshake incompatibilities on older phone or laptop chipsets.
Step 3
Create a Dedicated 2.4GHz IoT Network
If smart home plugs or cameras fail to onboard, create a separate SSID restricted strictly to the 2.4GHz band with Fast Roaming (802.11r) turned off. Many IoT chipsets fail to complete registration when 5GHz steering and BSS Transition are enabled on a unified network.
Step 4
Clear Blocked Clients and Verify MAC Rules
In the UniFi Network app, navigate to the Clients tab and adjust the filter to show 'All Historical Clients' and 'Blocked'. Confirm that the new device's MAC address hasn't been accidentally flagged, blacklisted, or assigned a static IP outside your gateway's subnet.
Step 5
Force-Provision Access Points and Restart Gateway
Perform a soft restart of your UniFi Dream Machine, Security Gateway, or Cloud Key through the system menu. Once back online, go to Devices, select your Access Points, and click 'Force Provision' to push a fresh configuration matrix to all broadcast nodes.
Likely causes
- DHCP Scope Exhaustion (no remaining free IP addresses in the subnet pool)
- Protected Management Frames (PMF) set to Required, blocking incompatible chipsets
- WPA3-Only or WPA2/WPA3 Mixed mode handshake failure on legacy Wi-Fi hardware
- MAC Address Filtering or 'Blocked Clients' rules active in UniFi OS
- Band Steering or Fast Roaming (802.11r) interfering with initial client association
- Unsynchronized provisioning state between the UniFi Gateway and Access Points
What's going on
Ubiquiti networking hardware—including UniFi OS Gateways, Dream Machines, and EdgeRouters—is designed for high-density enterprise stability. However, its strict security features and advanced network management tools can occasionally lock out newly added devices.
When your existing devices continue browsing without issue while a new phone, laptop, or smart plug is flatly rejected, the underlying cause is almost always software-driven. Common culprits include an exhausted DHCP lease table, enforced PMF (Protected Management Frames), or an out-of-sync configuration file between the primary gateway and downstream Access Points.
Symptoms people notice
- Existing connected clients function normally, but new devices cannot obtain an IP address.
- Handsets hang indefinitely on "Connecting..." or display an immediate "Failed to Connect" error.
- Smart home setup apps report that the accessory cannot find or authenticate with the Wi-Fi network.
- Entering the correct Wi-Fi passphrase returns an instantaneous "Incorrect Password" prompt.
- UniFi OS logs display repeating "DHCP Timeout" or "Client Association Failed" events for specific MAC addresses.
Likely causes
- DHCP Pool Exhaustion: Your network subnet (e.g.,
192.168.1.100–192.168.1.254) has run out of assignable IP addresses due to static assignments or long lease retention times. - PMF (Protected Management Frames) Enforcement: Enabling mandatory PMF blocks legacy wireless chips that do not support 802.11w standards.
- WPA3 Handshake Incompatibility: Mixed WPA2/WPA3 security settings often cause client-side connection drops during initial key exchanges.
- Band Steering & Fast Roaming: 802.11r transition features can confuse single-band 2.4GHz smart devices during pairing.
- Stale AP Provisioning: An Access Point running on cached settings that haven't synced with recent Controller security changes.
Quick checks first
Before changing router settings, verify the client device itself. Modern smartphones use MAC Address Randomization ("Private Wi-Fi Address"), which generates a new virtual hardware address when connecting to refreshed networks. This feature can quickly consume open IP addresses on smaller subnets.
Next, log into your UniFi Console (unifi.ui.com) or EdgeOS interface. Inspect your active network topology to confirm the gateway is issuing valid IP ranges. If you are experiencing broader connectivity hurdles across your setup, consult our master routers troubleshooting guide.
When it's a real hardware fault
While almost all join failures on Ubiquiti systems are logic or configuration errors, physical component failures do occur:
- Degraded Access Point Radios: Physical damage or thermal wear on an AP's 2.4GHz or 5GHz radio can prevent RF acknowledgement frames from reaching client devices.
- PoE / Port Interruption: Flaky Power over Ethernet injectors or bad Ethernet cabling can cause an AP to reboot under high power draw when new clients attempt to associate.
- Corrupted Gateway Storage: Internal eMMC flash degradation on older Cloud Keys or Gateways can cause local database corruption, locking client authorization tables.
For broader device evaluations, check our main hardware reviews hub or explore dedicated Ubiquiti hardware guides.
Soft resets vs board/panel work
Unlike standard consumer routers that feature a simple push-button reset to fix minor bugs, Ubiquiti UniFi environments rely on centralized controller management. Avoid factory resetting your APs or Gateway as a first step unless you have a fresh system backup (.unf or .unifi file) saved locally.
Instead, use the UniFi OS management panel to execute a soft restart of the network application or gateway hardware. Board-level repairs on enterprise router PCBs or AP circuit boards are rarely practical; if internal flash storage or Ethernet PHY chips fail, component replacement or an official RMA is the proper path forward.
Next steps
- Expand your primary subnet mask (e.g., move from
/24to/23) or lower your DHCP lease duration to 8 hours. - Create a dedicated 2.4GHz-only IoT network with WPA2-PSK security and PMF disabled.
- Trigger a manual AP provision refresh from your UniFi Network interface.
- If client join failures persist, check System Log > Events in UniFi OS to identify specific association handshake codes.
Next steps
Try the DIY guide if you're comfortable opening the device. Still stuck? Browse related problems for similar symptoms.
