If a UniFi access point stops working right after you set a static IP, the usual cause is a bad network setting, not a failed AP. The most common problems are a duplicate IP, wrong subnet mask, wrong gateway, wrong DNS, or a VLAN mismatch. Start by matching the symptom to the failure mode. Then back out the change in the safest way that still lets you reach the AP.
What kind of failure are you actually seeing?
“Stops working” can mean a few different things, and the fix depends on which one you have.
If Wi‑Fi still broadcasts but clients can’t get internet, the radio is probably fine. The issue is usually upstream: gateway, DNS, VLAN, or how the AP is bridged onto the LAN.
If the AP disappears from UniFi Network, but nearby clients still connect, the management path is broken. The AP may still pass traffic while the controller can’t reach it at the new address.
If the AP is unreachable by ping, app, or browser right after the change, treat it as an IP configuration problem first. Stop changing random settings and check whether the new address actually fits the network the AP is plugged into.
Before you start
Before you change anything else, confirm three things: the AP is on the right switch port, the port is carrying the VLAN you expect, and you know the subnet that VLAN uses.
A manual IP only works when the AP’s address, subnet mask, default gateway, and DNS settings match the live LAN it sits on. The address also has to be unique on that network. If the AP sits on a tagged VLAN, the switch port and the AP’s management network have to agree, or the AP can look dead even though it is still powered.
If you can still reach the AP through UniFi Network or by ping, use that path first. If you can’t, recover access before you make more changes.
The static-IP mistakes that usually break UniFi APs
The most common mistake is a duplicate IP. If another device already uses the address you assigned to the AP, the result can be flaky access, an offline controller entry, or a device that seems to come and go.
The next mistake is a bad subnet mask. If the mask does not match the LAN, the AP may think the gateway or controller is on a different network than it really is.
A wrong gateway can make the AP look dead from the outside even if the Wi‑Fi radio is still up. The AP may continue to broadcast SSIDs, but it may not be able to reach the router, DNS, or UniFi controller reliably.
A wrong DNS setting usually does not stop local Wi‑Fi by itself, but it can break anything that depends on name resolution. That can make the AP appear healthy from the client side while management, cloud access, or other network services fail.
A wrong VLAN is just as disruptive. If you put the AP’s management address on a VLAN that the switch port is not actually carrying, the AP may lose management access the moment the change takes effect.
How to check whether the AP’s static IP conflicts with another device
Check the address from the router, switch, or any device that can see the same subnet. You want to know whether the IP you gave the AP is already in use, not just whether the AP can answer from your desk.
A safe way to do that is to look for the address in your DHCP lease list, ARP table, or client list. Then compare the MAC address you expect with the device that is actually using it. If the same IP shows up for a different MAC, or the lease table already contains that address, assume you have a conflict until proven otherwise.
If the AP is still reachable, try a ping from a device on the same VLAN. If you get replies from the wrong device, or the address answers inconsistently, that is another clue that something else already owns it.
If the address does not show up anywhere and the AP is still offline, the conflict may be with a device outside your management view. Treat the static assignment as suspect and move to recovery rather than forcing it.
Check the switch port, VLAN, and UniFi controller next
Before you blame firmware, verify the switch port the AP is plugged into. The port profile has to match the VLAN design you are using, and the AP has to be connected to the network that can actually reach its management IP.
If you recently changed the AP to a static address on a different VLAN, check whether the port is trunked or access-only, and whether the management VLAN is allowed on that port. A mismatch here is a common reason the AP still broadcasts Wi‑Fi while UniFi shows it offline.
Also check the UniFi controller side. If the AP is reachable locally but not in UniFi Network, the controller may still be looking for it on the old address, or discovery may be blocked by the VLAN layout. That is a management-path problem, not proof that the AP hardware failed.
How to recover access if the AP is unreachable after the change
- If you can still reach the AP from the same LAN or VLAN, change it back to DHCP first. That is the quickest safe rollback when you still have management access.
- If you cannot reach it through UniFi Network, try to get onto the same VLAN as the AP’s management address and test ping again. If the address responds there but not from elsewhere, the issue is usually routing, VLAN, or gateway related.
- If the AP is completely unreachable, put the switch port and the AP back into a known-good state. In practice, that often means restoring the previous port profile or temporarily moving the AP to the network it originally used.
- Once you can manage the AP again, remove the manual static IP and use DHCP unless you have a specific reason to keep a fixed address.
How to prevent this next time
For most homes and small offices, a DHCP reservation is safer than a manual static IP for a UniFi access point. You still get a fixed address, but the router handles the lease and you avoid manual mistakes with gateway, subnet mask, and DNS.
Use a manual static IP only when you need it and you can verify the entire path: the AP address is unique, the subnet mask matches the LAN, the gateway points to the right router, DNS is valid for that network, and the switch port carries the VLAN where the AP lives.
If your network changes often, or if the AP sits on a tagged management VLAN, DHCP reservation is usually the cleaner choice.
Conclusion
Once the AP is reachable again, set the address method you can support reliably and leave it there.
Frequently Asked Questions
Why does my UniFi AP still show the SSID but not show up in UniFi Network after a static IP change?
That usually means the radio is still up but the management path is broken. Check the gateway, subnet mask, VLAN, and duplicate-IP possibility first, then confirm the switch port and controller can reach the new address.
Should I use a manual static IP or a DHCP reservation for a UniFi access point?
A DHCP reservation is safer in most cases because it keeps the address stable without making you hand-enter the full network setup on the AP. Use a manual static IP only if you need it and you’ve confirmed it matches the live LAN and VLAN.