Routers · Ubiquiti
Ubiquiti UniFi Gateways Adopting Devices Fails
When your Ubiquiti UniFi Gateway gets stuck in an adoption loop or reports 'Adoption Failed', the issue usually stems from IP inform mismatches, firewall port blocks, or corrupted adoption keys.
Symptoms
- Gateway or connected device stuck in 'Adopting' state in UniFi Network Application
- Status displays 'Adoption Failed' shortly after initiating connection
- Device repeatedly loops between 'Adopting', 'Disconnected', and 'Pending Adoption'
- UniFi device status listed as 'Managed by Other' after migration or factory reset
- SSH output shows inform URL status as 'Unreachable' or returning HTTP errors
- Device LED stays solid white instead of transitioning to solid blue
Quick troubleshooting
Step 1
SSH into the device and update the inform address
Use an SSH client (like PuTTY or Terminal) to connect to the device's IP address using the default admin credentials or site SSH keys. Run `set-inform http://<your-controller-ip>:8080/inform` and immediately click Adopt in your UniFi Network Application dashboard. Re-run the command once more right after initiating adoption to lock in the controller address.
Step 2
Verify firewall rules and open required ports
Ensure the device hosting your UniFi Network Application is not blocking incoming traffic. Unbind or allow TCP port 8080 (inform port), TCP port 8443 (dashboard UI), and UDP port 3478 (STUN service) on the host operating system firewall. If using a multi-VLAN network, verify cross-VLAN routing rules allow communication back to the controller.
Step 3
Forget the device from the UniFi Network Application
If the device displays 'Managed by Other' or is trapped in a dirty configuration state, open the device properties panel in the UniFi console. Navigate to Settings, scroll down, and select 'Forget Device'. This clears stale encryption keys from the database so the controller accepts a clean adoption handshake.
Step 4
Perform a physical factory reset using the pinhole button
With the device powered on, press and hold the reset pinhole button on the front or rear panel for roughly 10 seconds until the status LED flashes white/off. Allow the hardware 2 to 3 minutes to reboot into a pristine factory state (solid white light) before attempting re-adoption.
Likely causes
- Mismatched or unreachable set-inform IP address or hostname
- Local host firewall blocking TCP port 8080 or UDP port 3478 on the controller host
- Network Application controller version incompatible with newer device firmware
- Stale encryption tokens left in the UniFi controller database from a previous site
- VLAN or subnet isolation preventing Layer 2 discovery packets from reaching the gateway
- Physical link degradation or failing flash memory on the gateway unit
What's going on
Adoption is the process by which Ubiquiti UniFi devices bind themselves to a central UniFi Network Application controller. Whether you are setting up a console from the Ubiquiti UniFi Gateways lineup or adopting downstream access points and switches into your gateway, adoption relies on two key phases: Layer 2 network discovery and Layer 3 HTTP 'inform' reporting.
When adoption fails, the handshake between the gateway/device and the controller breaks down mid-stream. The controller sees a device asking to join, but secure cryptographic keys cannot be exchanged, or the device loses sight of the controller's internal IP address while rebooting.
Symptoms people notice
- Endless Adoption Loop: The dashboard switches between "Adopting", "Getting Ready", and "Disconnected" every few minutes.
- Adoption Failed Banner: Red error flags appear in the UniFi Network Application status column.
- Managed by Other Status: The console recognizes the hardware but refuses to adopt it because the unit retains security keys from a former setup.
- White LED Indication: The hardware LED remains solid white (ready for adoption) rather than switching to blue (adopted and operating).
- Inform URL Timeout: Checking the device via command line shows
Status: Server RejectorStatus: Unable to resolve...under the inform URL.
Likely causes
- Incorrect Set-Inform URL: The device is pointing to a default IP (like
192.168.1.20) or an outdated controller hostname that is no longer reachable on the network. - Firewall Port Interruption: TCP port 8080 or UDP port 3478 are disabled or blocked on the machine hosting the UniFi Network Application.
- Database Conflicts: Leftover cache entries in the UniFi Network Application block newly issued adoption request keys.
- VLAN Subnet Isolation: Management VLAN settings or guest isolation rules isolate the controller's management network from untagged device ports.
- Outdated Application Software: Older UniFi Network Application versions cannot adopt hardware running newer factory firmware, and vice versa.
Quick checks first
Before digging into command lines, perform a basic infrastructure check:
- Physical Connectivity: Ensure the ethernet cable is fully seated in the WAN/LAN ports and link lights show active data transfer.
- Verify Controller IP: Double-check the network IP address of your cloud key, network application server, or gateway console. Ensure it hasn't changed due to a non-reserved DHCP address.
- Test Local Ping: Ping the problem device's IP from the controller host machine to verify standard network path connectivity.
- Check Controller Software: Verify your UniFi Network Application is up to date via the main application settings page.
When it's a real hardware fault
While 90% of adoption failures stem from software, routing, or credential mismatches, hardware faults do happen. Internal eMMC flash degradation on older UniFi hardware can make flash memory read-only. When this occurs, the gateway accepts the set-inform command temporarily, but fails to write the security tokens to persistent storage—causing adoption to fail immediately upon reboot.
Ethernet PHY chip failure or blown PoE negotiation chips on integrated switch ports can also cause packet drops precisely during high-bandwidth configuration updates. If the unit regularly loses power, smells hot, or drops Ethernet link status at the hardware layer during adoption attempts, internal component failure is likely.
Soft resets vs board/panel work
For enterprise networking equipment like UniFi Gateways, fix efforts should remain focused on configuration resets, SSH provisioning, and firmware updates. Soft resets via software and hardware resets via the physical pinhole restore factory partition images without damaging the unit.
Attempting internal board-level soldering or eMMC memory replacement on compact router logic boards is rarely practical for homeowners. If a gateway fails to hold internal storage settings despite multiple physical resets, component replacement of the gateway hardware itself is recommended over attempting DIY board repairs.
Next steps
If you have resolved your set-inform path and cleared old database tokens, your UniFi Gateway should adopt and provision smoothly. For further reading on device diagnostics, network hardware comparisons, and common router pitfalls, visit our general Router Troubleshooting Hub or browse equipment teardowns and reviews in our Reviews Hub.
Next steps
Try the DIY guide if you're comfortable opening the device. Still stuck? Browse related problems for similar symptoms.
Related problems
- Rokid AR Glasses No Display / Nebula Not Detecting
- Viture XR Glasses No Display / Nebula Not Detecting
- Xreal AR Glasses No Display / Nebula Not Detecting
- Meta Oakley Smart Glasses Camera Capture Fails or Blurry
- Meta Ray-Ban Smart Glasses Camera Capture Fails or Blurry
- Samsung Smart Glasses Smart Glasses Case Not Charging Buds/Arms

