Separate the local Wi-Fi link from the upstream internet connection. Signal bars alone do not prove that the router can reach the internet.
Chrome reached the network, but the connection was closed before the page finished loading. A router, VPN, security filter, proxy, browser state, or the website itself can reset the session.
Chrome cannot validate the website certificate for the current connection. A wrong clock, expired certificate, captive portal, interception, or unsafe site configuration can trigger the warning.
The device has joined the router, but the router, modem, DNS path, captive portal, or internet provider is not delivering usable access.
The 5 GHz radio may be disabled, using an unsupported channel, sharing one hidden band-steered name, or out of range for the device.
The router may use another gateway address, the device may not be connected locally, HTTPS may be required, or a VPN, browser, or management restriction may block the page.
The DNS lookup did not return a usable address for the domain. The name may be mistyped, expired, temporarily unavailable, filtered, or failing through the current DNS resolver.
The destination was reached, but nothing accepted the connection on the requested service. The website may be down, blocked, misconfigured, or reachable only through a specific network.
The cable link is active, but the router, DHCP, DNS, VLAN, authentication, or internet service is not providing usable access.
A red LOS light means loss of optical signal on many fiber ONTs or gateways. The fiber path, connector, provider network, or optical terminal is not receiving usable light.
A mesh node may lose power, backhaul signal, Ethernet link, firmware coordination, or account association with the main router.
DNS, IPv6, MTU, filtering, date/time, browser security, or a partial provider routing issue can make selected sites fail while others work.
A continuously blinking DSL light means the modem is trying to synchronize with the telephone-line service but has not established a stable DSL link.
A red internet or WAN light usually means the router cannot establish a usable upstream connection to the modem or provider, but exact LED meanings vary by model.
Unstable power, overheating, firmware crashes, failing hardware, a loop, or heavy load can make a router reboot without warning.
The server understood the request but refuses to authorize it. Permissions, login state, region, IP reputation, security rules, or a private resource can produce HTTP 403.
The service is rate-limiting requests from the browser, account, app, or IP address. Repeated refreshes, automation, extensions, shared networks, or service limits can trigger HTTP 429.
A gateway or proxy received an invalid response from an upstream server. The website, hosting platform, CDN, load balancer, or origin service is usually responsible for HTTP 502.
The server is temporarily unable to handle the request. Maintenance, overload, failed dependencies, disabled application pools, or capacity limits commonly produce HTTP 503.
A gateway waited too long for an upstream service to respond. Slow database work, overloaded application servers, network faults, or timeout settings commonly cause HTTP 504.
Distance, walls, metal, appliances, interference, and poor access-point placement can make one room much slower even when the internet plan is fast.
Weak signal, interference, roaming between access points, power saving, router instability, or a driver problem can repeatedly break the connection.
The router may not be broadcasting the expected band or name, the device may not support that band or channel, or the wireless adapter may be disabled or too far away.
A stale saved profile, keyboard or character issue, changed router security mode, band-steering mismatch, or device compatibility problem can make a valid password fail.