Error Medic

Connected to WiFi But No Internet Connection: Complete Troubleshooting Guide (iPad, iPhone & More)

Fix 'connected to WiFi but no internet' on iPhone, iPad & more. Step-by-step DNS flush, IP renewal, router resets & advanced fixes. Solved in minutes.

Last updated:
Last verified:
2,562 words
Key Takeaways
  • Root cause 1: IP address conflict or DHCP failure — your device received an invalid or duplicate IP address, so the router cannot route traffic correctly.
  • Root cause 2: DNS misconfiguration or DNS server failure — your device can connect to the network but cannot resolve domain names to IP addresses, making all web requests fail.
  • Root cause 3: Captive portal not dismissed, ISP outage, or router firmware bug — the device shows full bars but the gateway itself has lost its upstream WAN connection.
  • Quick fix summary: Forget the WiFi network and reconnect, renew your DHCP lease, switch to Google DNS (8.8.8.8) or Cloudflare (1.1.1.1), power-cycle your router and modem, and — as a last resort — reset network settings on iPhone/iPad.
Fix Approaches Compared
MethodWhen to UseTimeRisk
Toggle Airplane ModeQuick first attempt; clears transient network state on iPhone/iPad< 1 minNone
Forget & Rejoin WiFi NetworkWrong password cached, stale DHCP lease, or corrupted network profile2 minMust re-enter password
Renew DHCP Lease (manual IP renewal)IP conflict shown in Settings > WiFi > network details, or 169.254.x.x self-assigned IP2 minTemporary disconnection
Change DNS to 8.8.8.8 / 1.1.1.1Pages don't load but ping to IP address works; DNS server unresponsive3 minVery low
Power-cycle Router & ModemMultiple devices affected; router uptime very long; ISP line reset needed5 minBrief outage for all users
Flush DNS Cache (macOS/Windows)Browser shows DNS_PROBE_FINISHED_NXDOMAIN or ERR_NAME_NOT_RESOLVED1 minNone
Reset Network Settings (iPhone/iPad)All other fixes failed; persistent profile corruption; after iOS update5 minErases all saved WiFi passwords & VPN configs
Factory Reset RouterFirmware corruption, forgotten admin password, persistent WAN failure15-30 minHigh — erases all router config
Contact ISPOutage confirmed on ISP status page; modem cannot sync (blinking WAN light)VariableNone (escalation only)

Understanding "Connected to WiFi But No Internet Connection"

When your device shows full WiFi signal bars yet every browser tab returns an error — Chrome's ERR_INTERNET_DISCONNECTED, Safari's "Safari Cannot Open the Page", or Windows' "No Internet, secured" yellow triangle — you have a Layer 3 or Layer 4 problem, not a Layer 1 wireless problem. The radio link between your device and the router is healthy; the breakdown is happening further up the stack.

This guide covers the most common scenarios: iPhone connected to WiFi but no internet, iPad connected to WiFi but no internet, Windows PCs, macOS, and Android. The diagnostic logic is the same across all platforms.


Step 1: Confirm the Scope — One Device or All Devices?

Check another device on the same network immediately. This single question splits your troubleshooting path:

  • All devices affected → The problem is almost certainly your router, modem, or ISP. Skip straight to Step 4 (router/modem power-cycle).
  • Only one device affected → The issue is device-specific: IP conflict, DNS cache, network profile corruption, or VPN/proxy interference.

On iPhone/iPad: Open Settings → WiFi → tap the (i) icon next to your network. Note the IP Address shown. If it starts with 169.254.x.x, your device has a self-assigned (APIPA) address, which means DHCP failed completely.


Step 2: Quick Wins — Try These First (All Devices)

2a. Toggle Airplane Mode (iPhone & iPad)

  1. Swipe to Control Center.
  2. Tap the Airplane icon — wait 10 seconds.
  3. Tap again to disable. WiFi will reconnect automatically.

2b. Restart Your Device A full reboot clears cached network state, flushes the local DNS resolver, and forces a fresh DHCP request. On iPhone X and later: press and hold Side + Volume Down → slide to power off.

2c. Forget and Rejoin the WiFi Network (iPhone/iPad)

  1. Settings → WiFi → tap (i) next to the network name.
  2. Tap Forget This Network → Forget.
  3. Tap the network name in the list → enter your password → Join.

This is often the single fastest fix for iPhone/iPad users because iOS caches DHCP leases and network configurations aggressively.


Step 3: Renew Your IP Address / Fix DHCP

On iPhone/iPad:

  1. Settings → WiFi → tap (i) next to your network.
  2. Scroll down to Renew Lease → tap it → confirm.
  3. Wait 15 seconds and test.

On macOS:

sudo ipconfig set en0 DHCP

Or via System Preferences → Network → WiFi → Advanced → TCP/IP → Renew DHCP Lease.

On Windows: Open Command Prompt as Administrator:

ipconfig /release
ipconfig /renew

If after renewal you still get a 169.254.x.x address, the DHCP server (usually your router) is not responding. Move on to Step 4.


Step 4: Power-Cycle Your Router and Modem

This is the highest-yield fix when multiple devices are affected.

  1. Unplug your modem (the box connected to the coax or phone line) from power.
  2. Unplug your router (separate device if applicable) from power.
  3. Wait a full 60 seconds — this allows capacitors to discharge and the ISP's CMTS/DSLAM to clear the session.
  4. Plug the modem back in first. Wait for the WAN/Internet light to become solid (not blinking). This can take 1–3 minutes.
  5. Plug the router back in. Wait another 60–90 seconds.
  6. Reconnect your device and test.

Modem light reference:

  • Solid white/green WAN light = synced with ISP ✅
  • Blinking WAN/US+DS lights after 5+ minutes = ISP line issue, call your ISP.

Step 5: Fix DNS — The #1 Silent Culprit

You can test if DNS is the problem by pinging a known IP address directly:

On macOS / Linux terminal:

ping -c 4 8.8.8.8

On Windows cmd:

ping 8.8.8.8
  • Ping to 8.8.8.8 succeeds but websites don't load → Pure DNS failure. Fix DNS immediately.
  • Ping to 8.8.8.8 also fails → Not a DNS issue; the gateway itself has no internet.

Change DNS on iPhone/iPad:

  1. Settings → WiFi → tap (i) next to your network.
  2. Scroll to DNS → tap Configure DNS → tap Manual.
  3. Delete existing servers → tap Add Server → enter 1.1.1.1 → Add Server → 8.8.8.8 → Save.

Change DNS on macOS: System Preferences → Network → WiFi → Advanced → DNS tab → click (+) → add 1.1.1.1 and 8.8.8.8 → OK → Apply.

Flush DNS Cache (macOS Sonoma/Ventura/Monterey):

sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder

Flush DNS Cache (Windows 10/11):

ipconfig /flushdns
netsh winsock reset
netsh int ip reset

Restart your PC after the Winsock reset.


Step 6: Check for Captive Portal / Proxy Interference

If you're on a hotel, corporate, school, or coffee shop WiFi, a captive portal may not have loaded. Your device connects to the local network but all HTTP/S traffic is intercepted until you log in.

If a proxy is configured on your device unintentionally:

  • iPhone/iPad: Settings → WiFi → (i) → HTTP Proxy → verify it says Off.
  • Windows: Settings → Network & Internet → Proxy → toggle off "Use a proxy server".

Step 7: Reset Network Settings (iPhone & iPad — Last Resort)

If all steps above have failed, iOS network settings may be corrupt. Warning: this erases all saved WiFi passwords, VPN configurations, and cellular APN settings.

  • iOS 16 and later: Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings → enter passcode → confirm.
  • iOS 15 and earlier: Settings → General → Reset → Reset Network Settings.

The device will reboot. Reconnect to your WiFi network and test.


Step 8: Advanced — Check Router Admin for IP Conflicts and Logs

Log into your router's admin panel (typically 192.168.1.1 or 192.168.0.1) using your admin credentials.

  1. Navigate to the DHCP Client List or Connected Devices page.
  2. Look for duplicate IP addresses assigned to different MAC addresses — a classic IP conflict.
  3. Check the System Log or WAN Status for PPPoE errors, authentication failures, or "No Cable" messages.
  4. Ensure the DHCP pool has not been exhausted (e.g., pool set to only 10 addresses but 12 devices are connected).

If you see repeated WAN disconnect/reconnect events in the router log, your ISP line is unstable — call your ISP with this log data in hand.


Step 9: Check for ISP Outage

Before spending more time troubleshooting, verify:

  • Visit your ISP's status page (Comcast: downdetector.com/status/xfinity, AT&T: att.com/outages, etc.) from cellular data.
  • Check downdetector.com for your ISP.
  • Call ISP support and ask for any known outages in your area.

Frequently Asked Questions

bash
#!/usr/bin/env bash
# =============================================================
# WiFi No-Internet Diagnostic Script (macOS / Linux)
# Run with: bash wifi_diag.sh
# =============================================================

echo "===== WiFi No-Internet Diagnostics ====="
echo ""

# 1. Show current IP address and gateway
echo "[1] Network Interface Info:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  ipconfig getifaddr en0 2>/dev/null && echo "  -> Active interface: en0" || \
  ipconfig getifaddr en1 2>/dev/null && echo "  -> Active interface: en1" || \
  echo "  -> Could not detect active WiFi interface"
  echo "  Gateway: $(netstat -rn | grep default | awk '{print $2}' | head -1)"
else
  ip addr show | grep 'inet ' | grep -v '127.0.0.1'
  echo "  Gateway: $(ip route | grep default | awk '{print $3}' | head -1)"
fi

echo ""

# 2. Check for APIPA / self-assigned IP (169.254.x.x = DHCP failure)
echo "[2] DHCP Health Check:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  MYIP=$(ipconfig getifaddr en0 2>/dev/null)
else
  MYIP=$(hostname -I | awk '{print $1}')
fi

if [[ $MYIP == 169.254.* ]]; then
  echo "  !! APIPA address detected ($MYIP) -- DHCP server not reachable!"
  echo "  FIX: Check router DHCP settings or power-cycle router."
else
  echo "  OK: IP address is $MYIP (not APIPA)"
fi

echo ""

# 3. Ping gateway
GATEWAY=$(if [[ "$OSTYPE" == "darwin"* ]]; then netstat -rn | grep default | awk '{print $2}' | head -1; else ip route | grep default | awk '{print $3}' | head -1; fi)
echo "[3] Pinging Gateway ($GATEWAY):"
ping -c 3 -W 2 "$GATEWAY" 2>/dev/null && echo "  OK: Gateway is reachable" || echo "  !! Gateway unreachable -- check router"

echo ""

# 4. Ping internet by IP (bypass DNS)
echo "[4] Pinging 8.8.8.8 (tests raw internet, bypasses DNS):"
ping -c 3 -W 2 8.8.8.8 2>/dev/null && echo "  OK: Internet IP reachable" || echo "  !! Cannot reach 8.8.8.8 -- no internet path"

echo ""

# 5. DNS resolution test
echo "[5] DNS Resolution Test (nslookup google.com):"
nslookup google.com 2>/dev/null | grep -E 'Address|Name' || echo "  !! DNS resolution failed"

echo ""

# 6. DNS with alternate servers
echo "[6] DNS Test using 1.1.1.1 (Cloudflare):"
nslookup google.com 1.1.1.1 2>/dev/null | grep -E 'Address|Name' || echo "  !! Failed with 1.1.1.1 -- unusual"

echo ""

# 7. Flush DNS cache (macOS only)
if [[ "$OSTYPE" == "darwin"* ]]; then
  echo "[7] Flushing macOS DNS cache..."
  sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder && echo "  OK: DNS cache flushed"
fi

# 8. HTTP connectivity test
echo ""
echo "[8] HTTP Connectivity Test (curl to captive portal check endpoint):"
curl -s --max-time 5 -o /dev/null -w "HTTP Status: %{http_code}\n" http://captive.apple.com/hotspot-detect.html || echo "  !! HTTP request failed"

echo ""
echo "===== Diagnostics Complete ====="
echo "If tests 3 & 4 fail: power-cycle router/modem or call ISP."
echo "If test 3 OK but test 4 fails: router has no WAN -- call ISP."
echo "If tests 3 & 4 OK but test 5 fails: DNS issue -- change DNS to 1.1.1.1."
echo "If all OK but browser fails: clear browser cache or check proxy settings."

# =============================================================
# Windows equivalents (run in cmd.exe as Administrator):
# ipconfig /all
# ping 8.8.8.8
# nslookup google.com
# nslookup google.com 1.1.1.1
# ipconfig /release && ipconfig /renew
# ipconfig /flushdns
# netsh winsock reset
# netsh int ip reset
# netsh interface ipv4 set dns "Wi-Fi" static 1.1.1.1
# netsh interface ipv4 add dns "Wi-Fi" 8.8.8.8 index=2
# =============================================================
E

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network administrators with 10+ years of experience diagnosing connectivity, DNS, and infrastructure failures across enterprise and consumer environments. Our guides are tested on real hardware and kept current with the latest OS and firmware releases.

Sources

Related Articles in Other Connected To Wifi But No Internet Connection

Explore More wifi Guides