Your Mac is connected to Wi-Fi, the icon shows full bars, but every page times out. You open System Settings → Wi-Fi → Details → TCP/IP and see the dreaded line: "Wi-Fi has a self-assigned IP address and will not be able to connect to the Internet." The address starts with 169.254.
Here is the key thing to understand before you touch anything: this is not a DNS problem and it is usually not a broken router. A self-assigned IP means your Mac asked the router for an address (DHCP) and never got an answer, so macOS made up its own address in the 169.254.x.x range (called APIPA). Nothing routes on that range, which is why you are "connected" with zero internet. Fix the handshake and you fix the internet.
The fixes, fastest first
1. Renew the DHCP lease
This is the direct fix and it works surprisingly often. Go to System Settings → Wi-Fi → Details (next to your network) → TCP/IP and click Renew DHCP Lease. Your Mac re-asks the router for a real address. If the IP changes from a 169.254 number to something like 192.168.x.x, you are fixed.
2. Toggle Wi-Fi off and on (and forget the network)
Turn Wi-Fi off from the menu bar, wait ten seconds, turn it back on. If that does not clear the 169.254 address, forget the network (System Settings → Wi-Fi → the "i" next to your network → Forget This Network) and rejoin with the password. This wipes a stale saved configuration that can block a clean lease.
3. Restart the router — and give it two full minutes
If your Mac cannot get a lease, the DHCP server on the router may have run out of addresses or wedged. Unplug the router, wait 30 seconds, plug it back in, and wait a full two minutes for it to finish booting before you test again. If a phone or another laptop also cannot get on, the router (not your Mac) is the problem.
4. Set a manual IP as a test
To prove the Wi-Fi radio still works, set an address by hand. In TCP/IP, change Configure IPv4 to Manually and enter an address on your router's range (for most home routers: IP 192.168.1.50, Subnet Mask 255.255.255.0, Router 192.168.1.1). If the internet comes back with a manual address, DHCP is the culprit — switch Configure IPv4 back to Using DHCP afterward so it works on other networks.
5. Reset your network location
Sometimes the saved network configuration itself is corrupt. Go to System Settings → Network, click the … menu, choose Locations → Edit Locations, add a new location, switch to it, and reconnect to Wi-Fi. A fresh location forces macOS to build the network stack from scratch. (See our guide on network locations if you have never used them.)
6. Delete the network configuration files
This is the nuclear option for a self-assigned IP that will not clear, and it fixes the stubborn cases. Turn Wi-Fi off. In Finder, press ⌘⇧G and go to /Library/Preferences/SystemConfiguration/. Move these files to the Trash:
com.apple.airport.preferences.plist-
com.apple.network.identification.plist(orNetworkInterfaces.plist) preferences.plist
Restart your Mac. macOS rebuilds all of these clean, and the self-assigned IP is almost always gone. You will need to rejoin your Wi-Fi network and re-enter the password, so have it handy.
7. Check for a VPN, firewall, or content blocker
A crashed VPN client or an overzealous third-party firewall can strangle the DHCP request. Quit any VPN app, and in System Settings → Network → Firewall confirm nothing is blocking system services. If you have a VPN that will not fully quit, our notes on a VPN that will not connect apply here too.
How this is different from other "no internet" errors
It is easy to confuse these because the symptom — no internet — looks the same. They are not the same fix:
- Self-assigned IP (169.254.x.x) — DHCP failed. Your Mac never got a valid address. That is this page.
- DNS server not responding — you have a real IP, but names are not resolving. Fixed by flushing or changing DNS.
- "You are not connected to the Internet" — a broader banner, often a captive portal or a Safari-only issue.
If your address is fine but pages still fail, the DNS route is where to go — and switching to a public DNS server is a quick win.
When it is the hardware, not the software
If you have renewed the lease, reset the location, deleted the plists, and the Mac still lands on 169.254 on more than one network — while your phone gets online on the same Wi-Fi — the Wi-Fi card or antenna may be failing. On MacBooks the Wi-Fi module is soldered to the logic board, so a repair is rarely worth it on an older machine.
You do not have to eat that loss. A MacBook with flaky Wi-Fi still has real value, and we buy them — see what a MacBook with broken Wi-Fi is worth. If you would rather just upgrade, our Apple clearance section has refurbished MacBooks with a fresh, tested Wi-Fi card and a warranty.
Frequently Asked Questions
What does "self-assigned IP address" actually mean on a Mac?
It means your Mac asked your router for an IP address using DHCP and got no reply, so macOS assigned itself a placeholder address in the 169.254.x.x range. That range does not route to the internet, which is why Wi-Fi shows "connected" but nothing loads.
Why does it start with 169.254?
That block is reserved for APIPA (Automatic Private IP Addressing). Any device — Mac, Windows, phone — falls back to it when DHCP fails. Seeing 169.254 is the tell-tale sign the problem is the address handshake, not DNS or the website.
Is a self-assigned IP a router problem or a Mac problem?
Test another device on the same Wi-Fi. If the phone or another laptop also cannot get online, it is the router (restart it, or its DHCP pool is full). If only your Mac fails, it is your Mac — work through the lease renewal, location reset, and plist deletion above.
Will deleting those .plist files erase my data?
No. Those files only store network configuration — saved Wi-Fi networks, IP settings, and locations. macOS rebuilds them automatically on restart. You will just need to rejoin your Wi-Fi and re-enter the password.
My Mac only gets a self-assigned IP on one specific network. Why?
That points at that network, not your Mac. The router's DHCP pool may be exhausted, or a MAC-address filter is blocking your Mac. On your own router, restart it; on someone else's, ask them to reboot it or check their device limit.
Could this mean my MacBook's Wi-Fi card is dying?
It can, but only if it persists across multiple networks after every software fix. A dying card usually also brings dropped connections and weak signal even next to the router. If you are at that point, get a trade-in quote rather than paying for a soldered-board repair.