When Your Wi-Fi Works but the Web Does Not
A Wi-Fi connection only confirms that your phone, computer, or tablet can communicate with a local wireless router; it does not prove that the router can reach the internet. This guide explains how to isolate the failure by testing other devices, checking router indicators, restarting equipment in the right order, reviewing service outages, and distinguishing Wi-Fi signal issues from DNS, IP address, VPN, or captive-portal problems. It also covers safe router checks, useful command-line tests, and the signs that point to an internet service provider or hardware fault rather than a device setting.
Seeing a strong Wi-Fi signal while every website, app, and video fails to load is frustrating, but the message is more precise than it first appears. Your device has joined the local wireless network, yet something between the router and the wider internet is unavailable. The fault may be a temporary provider outage, a modem or router problem, a device-specific configuration issue, or a network service such as DNS. A methodical check prevents unnecessary resets and helps identify the right fix quickly.
What “Connected, No Internet” Actually Means
Wi-Fi is the radio link between your device and a nearby access point or router. Internet access requires additional pieces to work: the router must have a valid connection to the modem or fiber gateway, the service provider must be online, and your device must receive working network settings.
A device can therefore display Connected while being able to reach only local devices, such as a printer, shared storage, or the router’s administration page. It cannot necessarily reach websites or cloud services.
Start by separating a local Wi-Fi association from an internet-path problem. Signal bars describe radio strength, not the health of your broadband service.
First Checks That Narrow Down the Cause
Before changing settings, determine whether the issue affects one device or the entire network. Connect a second phone, computer, or tablet to the same Wi-Fi network and try opening several well-known sites. If possible, turn off cellular data on a phone during the test so it cannot silently use mobile service instead.
- All devices fail: focus on the modem, router, cabling, provider service, or router-wide DNS settings.
- Only one device fails: focus on that device’s Wi-Fi profile, IP settings, VPN, security software, or browser configuration.
- Some sites work but names do not resolve: DNS is a likely cause.
- A sign-in page appears: the network may use a captive portal, common in hotels, airports, schools, and public venues.
Also check the router or gateway lights. Exact labels differ by manufacturer, but an internet, WAN, online, or globe indicator that is red, amber, blinking unusually, or off often points beyond the wireless connection itself. A normal Wi-Fi light does not rule out a WAN failure.
Use the Right Restart Order
A controlled restart refreshes temporary faults and can restore a lost provider session. Do not immediately press the recessed factory-reset button: that action may erase your network name, password, and provider settings.
- Save any important work and disconnect nonessential network equipment.
- Unplug the modem, fiber gateway, or cable gateway, then unplug the separate router if you have one.
- Wait at least 60 seconds to allow residual power and stale sessions to clear.
- Reconnect the modem or gateway first and wait until its online or broadband status appears normal. This can take several minutes.
- Reconnect the router and wait for its Wi-Fi and internet indicators to stabilize.
- Reconnect one device and test the internet before testing the rest of the household.
Inspect the Ethernet cable between a standalone modem and router at the same time. It should be firmly seated in the modem’s Ethernet port and the router’s WAN or Internet port, not a numbered LAN port. If you have a known-good cable, swapping it is a low-risk test.
Match the Symptom to the Most Likely Fix
| Observed symptom | Likely cause | Useful next action |
|---|---|---|
| Every device has no access | Provider outage, modem issue, or WAN connection failure | Restart modem and router, inspect status lights, then check the provider’s service-status channel. |
| One phone or computer fails | Corrupt saved network, VPN, proxy, or invalid IP configuration | Forget the Wi-Fi network, reconnect, disable VPN or proxy temporarily, and renew the connection. |
| Web addresses fail, but a direct IP test works | DNS resolution failure | Restart the router, use automatic DNS, or try a trusted public DNS service if appropriate. |
| Public Wi-Fi says connected but blocks browsing | Captive portal has not been completed | Open a browser and visit a plain HTTP page such as neverssl.com to trigger the sign-in screen. |
| Internet drops only far from the router | Weak signal, interference, or poor access-point placement | Test near the router, move it to a central open location, or consider mesh or an additional access point. |
Fix a Single Device Without Disrupting Everyone
Forget and rejoin the network
On Windows, select the network icon, open Wi-Fi settings, manage known networks, select the network, and choose Forget. On macOS, open System Settings, choose Wi-Fi, find the known network list, and remove the affected network. On iPhone, iPad, and Android devices, use the Wi-Fi network details screen to forget or remove it. Rejoin using the correct password.
This removes a stored profile that may contain outdated security or addressing information. If the router password was changed recently, forgetting the network is especially useful.
Check VPN, proxy, and private-DNS settings
A VPN can report a successful Wi-Fi connection while its tunnel cannot reach its server. Disconnect the VPN temporarily and retest. Likewise, review any manually configured proxy in the operating system or browser. On Android, a Private DNS hostname that cannot be reached may interfere with name resolution; switching it to Automatic is a reasonable diagnostic step.
For devices configured manually, return IP address and DNS settings to automatic (DHCP) unless your workplace, school, or network administrator requires fixed values. Incorrect gateway or subnet values can leave a device connected to Wi-Fi but unable to leave the local network.
Test DNS and the Local Network Path
DNS translates names such as example.com into numerical IP addresses. A broken DNS setting can make the internet appear down even when the connection is otherwise functional. Try opening a site by its normal name first, then compare the behavior with a basic network test.
On Windows, open Command Prompt and run ping 1.1.1.1, then run ping example.com. On macOS or Linux, use Terminal with the same commands. If the numerical address responds but the domain name does not, DNS deserves attention. Ping results are not conclusive because some services block ping, but the comparison can still be informative.
Restarting the router often renews DNS information supplied by the provider. If the problem persists, you may test a reputable public resolver such as Cloudflare or Google DNS, following their official setup instructions. Make only one change at a time and record the original setting so you can reverse it. On managed work or school devices, ask the administrator before altering DNS.
Captive Portals, Public Networks, and Browser Checks
Many public networks require a web-based acceptance page before granting full access. Automatic detection can fail when a VPN, custom DNS configuration, browser extension, or strict privacy feature is active. Disconnect any VPN, open a browser, and visit a non-HTTPS page to prompt the portal. Complete the terms, room number, access code, or payment step if required.
If the portal never appears, forget the public network and reconnect. Avoid entering sensitive credentials on a suspicious or unverified sign-in page. Public Wi-Fi should be treated as untrusted: use HTTPS sites, keep sharing disabled, and consider a reputable VPN only after the portal has authenticated the connection.
When the Router or Provider Is the Problem
If every device remains offline after a proper restart, check your provider’s official outage page or support line using mobile data or another connection. A planned maintenance event, neighborhood outage, damaged line, or account issue cannot be fixed through Wi-Fi settings. Note any error message, the time the issue began, and the color or pattern of gateway lights before contacting support.
Router administration pages can provide useful clues, usually at an address such as 192.168.1.1 or 192.168.0.1. Look for WAN status, connection state, and assigned IP address. Do not expose screenshots containing public IP addresses, Wi-Fi names, serial numbers, or account identifiers. Firmware updates can improve reliability and security, but download them only through the manufacturer’s official interface and avoid updating during an unstable power supply.
