- Required adoption ports blocked
- Camera and NVR on isolated VLAN without proper rules
- Stale previous controller association
Problem Description
A UniFi Protect camera appears but will not adopt into the Protect host. This often results from VLAN/path restrictions, stale adoption state, firmware mismatch, or discovery traffic blocked by network policy.
Symptoms
- Camera shows pending adoption forever
- Adopt button fails repeatedly
- Camera reappears after reset but won’t add
- Only one model fails to adopt
- Camera works on network but not in Protect
- Adoption fails across multiple switches
Recognize these? Here's what usually causes it.
Common Causes
- Required adoption ports blocked
- Camera and NVR on isolated VLAN without proper rules
- Stale previous controller association
- PoE power instability during adoption
- Host/camera firmware mismatch
- Discovery broadcast blocked
Most fixes happen in the first 3 steps.
Do not repeatedly reset cameras without fixing network policy. You will keep reproducing the same adoption failure state.
Tools & Requirements
Step-by-Step Solution
Validate network path requirements
Ensure camera and Protect host can communicate over required adoption ports and that firewall/VLAN rules allow bidirectional traffic. Many adoption failures are pure network-policy issues even when both devices have valid IP addresses.
Clear old controller association
Factory reset the camera fully before re-adoption to remove stale controller bindings. Cameras previously attached to another Protect host may appear discoverable but reject adoption until ownership state is reset.
Adopt on simple baseline segment
Temporarily place camera and Protect host on same straightforward network segment for initial adoption. This removes complex inter-VLAN variables. After successful adoption and firmware sync, move camera back to target topology.
Check PoE and firmware alignment
Verify camera receives stable PoE power and that Protect host firmware is current. Insufficient power or old host software can interrupt adoption handshakes and leave devices in pending loops.
Finalize and retest in production VLAN
After adoption, move camera to intended network, confirm it remains connected, and test live stream plus recordings. If adoption fails only in final VLAN, refine ACL/routing policy rather than resetting camera again.
Quick Solutions
Still having issues? This is usually the deeper cause below.
Camera issues that start suddenly almost always trace back to an upload bandwidth drop — run a speed test before assuming hardware failure.
Adopt cameras on a clean baseline network first in complex VLAN environments, then migrate to production segmentation.
Live view problems that start suddenly usually trace back to an upload speed drop — the camera itself is fine, the bandwidth path to the cloud isn't.
- Required adoption ports blocked
- Camera and NVR on isolated VLAN without proper rules
- Stale previous controller association
- PoE power instability during adoption
- Host/camera firmware mismatch
Before you go — try one of these (they fix most cases).
Most popular upgrades chosen by UniFi Protect Camera Adoption owners.

4 Channel 360° Dash Cam Front Rear Inside & Left Right,4K...

4K Security Cameras Wireless Outdoor with 360° Pan&Tilt,A...

Wyze Cam v3, 1080P HD WiFi Wired Indoor/Outdoor Home Secu...
As an Amazon Associate we earn from qualifying purchases.
Need More Help? UniFi Protect Support
Note: The contact information below connects you directly to UniFi Protect's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.





