Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


A Chromebook connected to Wi-Fi but no internet has joined the local access point, but its traffic is not getting past it; a pending captive-portal sign-in, a router or provider outage, or a setting on the Chromebook is the usual cause. Compare another site, app, device, and trusted network to see which one applies, then use ChromeOS Diagnostics. Avoid forgetting enterprise networks or changing proxy, DNS, certificate, and management settings until the evidence points there.
Key Takeaways
- A Wi-Fi connection does not prove that the upstream internet path works.
- Compare devices and networks before changing Chromebook settings.
- Use ChromeOS Diagnostics to preserve connection and IP evidence.
- Open a plain HTTP page only to trigger a trusted captive-portal sign-in.
- Do not use Powerwash or Recovery for ordinary internet troubleshooting.
Start with the device and app troubleshooting guide if you need a broader method for separating device, app, account, and network failures.
Google documents connection troubleshooting.[1] Google also documents saved Wi-Fi settings.[2]
Use the same small set of comparisons before and after each step:
| Observation | Likely scope | Next check |
|---|---|---|
| Every device fails on one Wi-Fi | Router, modem, provider, or captive portal | Check the network owner |
| Only the Chromebook fails on one Wi-Fi | Saved network, compatibility, policy, or address assignment | Run Diagnostics |
| The Chromebook fails on several trusted networks | ChromeOS setting, extension, account policy, or hardware | Test Guest mode if permitted and contact support |
| One site or app fails | Site, app, extension, account, or service | Test another app and site |
| Google services fail but other sites work | Google Services path or managed filtering | Use the Diagnostics scan |
Google recommends testing after each troubleshooting step instead of changing several settings together. If every device on the home network is offline, use the router connected without internet checklist.
Run these checks in order:
If the Chromebook works on another network, the normal router, captive portal, or network policy is the better scope. If it fails everywhere while other devices work, keep the investigation on the Chromebook.
Do not use an unknown open network as a comparison. A test network should have a known owner and a connection policy you understand.
If the Chromebook will not join the Wi-Fi at all, that is a different fault: first confirm that Wi-Fi is on, the password is current, and the network appears in the list.
Hotels, airports, schools, hospitals, and cafés often require a sign-in page or agreement before granting internet access. ChromeOS can show Wi-Fi connected while that authorization is incomplete.
Google recommends visiting a site beginning with http:// to prompt the portal and using a private window if the administrator permits it. Use a simple, non-sensitive page only to trigger the venue's official sign-in flow. Verify the network name, venue branding, and certificate before entering a room code or account information.
If the page does not appear:
Do not install a certificate, disable security warnings, or copy another device's network address to bypass the portal.
After joining a network, ChromeOS requests a known Google web address that should return an empty response. If a sign-in page answers instead, the network is treated as a portal; if the check fails without a redirect, Wi-Fi can stay connected while the network is marked as having no internet.
| State | What it usually means | Next check |
|---|---|---|
| Portal | The check was redirected to a sign-in or agreement page | Open an http:// page and finish the venue's official sign-in |
| No internet | The check received no usable answer | Compare another device, then check the router or provider |
Neither state is a Chromebook fault code. If another device on the same Wi-Fi reaches the internet, return to Diagnostics and the saved network details.
Open Settings > About ChromeOS > Diagnostics, or search for Diagnostics in the Launcher. ChromeOS version 90 and later includes the app.[3]
The Connectivity section automatically tests the default connection and can show Wi-Fi, Ethernet, cellular, Google Services, and IP information.
Diagnostics reports clues, not permission to replace values randomly. A failed name-resolution check does not prove that a public DNS service is the correct permanent configuration.
Restart the smallest affected layer first. Google includes a Chromebook restart in its connection troubleshooting flow.
Do not press a router Reset button. A factory reset can erase provider, telephone, Wi-Fi, and custom network configuration.
Open Settings > Network > Wi-Fi, select the active network, and confirm that it is the intended SSID. Google documents this area for active and known networks.
Check:
The Wi-Fi band guide explains range and compatibility. The guest-network guide explains why a guest SSID can apply different access rules.
Do not delete a certificate, switch an enterprise network to an unverified certificate, or replace administrator-provided values.
Only investigate this layer when the comparison supports it—for example, Guest mode works while the normal profile fails, the captive portal appears after one extension is disabled, or Diagnostics identifies a specific service path.
Use one controlled comparison:
Do not disable required classroom monitoring, family safety, security, proxy, or certificate controls. On a managed Chromebook, a locked or automatically restored setting is evidence that the administrator owns it.
Changing DNS cannot repair a weak signal, router outage, captive portal, or policy block. A manual proxy copied from another device can expose traffic or credentials to an untrusted service.
Forgetting a network removes its saved connection information. Google provides this option under Wi-Fi > Known networks. Use it only after confirming that you have the correct password and can restore every required field.
Do not forget the network when it depends on:
For a normal home network, forget only that SSID, reconnect from the trusted list, and rerun Diagnostics. Do not clear every known network to solve one connection.
Work and school Chromebooks can receive network, certificate, proxy, extension, and sign-in policies. The local user may be unable to change them by design.
Stop and contact the administrator when:
Do not remove enrollment, switch to Developer Mode, or attempt a factory reset. Those actions can erase local work while leaving the organization policy and network problem unresolved.
Powerwash erases local user data, including files in Downloads, and managed devices must be handled by their administrator.[4] ChromeOS Recovery reinstalls the operating system and permanently erases the device's local drive.[5]
Neither procedure is a proportionate response to an ordinary Wi-Fi connection with no internet. Recovery belongs to an explicit operating-system failure such as “ChromeOS is missing or damaged,” not a browser timeout or captive portal.
If a manufacturer or administrator eventually recommends an erase, first sync and back up recoverable files, confirm account access, and follow the exact model-specific process.
Contact the network owner when every device fails, a captive portal will not authorize, or an organization policy owns the connection. Contact the Chromebook manufacturer when the device fails across several trusted networks, Diagnostics shows persistent hardware-related failures, or Wi-Fi repeatedly disappears from the system.
Provide:
Remove passwords, tokens, and unnecessary addresses from any report shared outside the trusted support channel.
The Chromebook has joined the local Wi-Fi access point, but the router, provider, captive portal, address assignment, managed policy, or Chromebook software can still block upstream access.
Visit a simple page beginning with http:// to invite the network's official captive portal. Confirm the network owner and page identity before entering any information.
Open Settings, select About ChromeOS, and then Diagnostics, or search for Diagnostics in the Launcher. The Connectivity section can test the current connection and Google services.
Only after confirming the password and any certificate, identity, proxy, or static settings needed to restore it. Do not forget a managed network without administrator guidance.
Only if evidence isolates name resolution as the problem. DNS changes do not repair captive portals, weak Wi-Fi, router outages, invalid local addresses, or administrator policy.
An extension can affect browser traffic or a portal flow, but test one extension at a time and restore it afterward. Do not disable an organization-required or security extension.
No. Powerwash erases local user data and is not a normal network troubleshooting step. A managed Chromebook must be handled by its administrator.
Send the exact error, Chromebook model and version, network name, whether other networks work, and the saved Diagnostics details. Remove passwords and unrelated personal information. On a Chromebook with no internet after Wi‑Fi association, AethoVPN cannot complete a captive login or fix DHCP; verify those basics before any VPN test.
Sources:
Sources checked 4 October 2026.
Related guides:
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.





