192.168.1.1 and 192.168.0.1 are popular private gateway addresses, not universal router addresses. If one does not open, that does not mean the router is broken.

The router may use a different factory address

Manufacturers and ISPs use many local ranges, including 10.x.x.x and other 192.168.x.x networks. Mesh systems and mobile hotspots often choose different defaults from traditional routers.

The address may have been changed

An installer, previous owner, ISP, or network administrator can change the LAN subnet. Your connected device will normally learn the current gateway automatically through DHCP, so checking the gateway is more reliable than guessing.

You may be connected to a different router

Homes with an ISP gateway plus a second router, mesh system, extender, or access point can contain several networking devices. The default gateway shown by your device points to the router currently handling its traffic.

Guest networks can block administration

Guest Wi-Fi is often isolated from local devices, including the router management interface. Join the main network or use Ethernet.

Use the correct local address

Follow How to Find Your Router IP, then type that address directly into the browser address bar.

Factory defaults are historical, current gateway is factual

Routers can change LAN subnet during setup, mesh/ISP systems use other defaults, and access-point mode makes an upstream router the gateway. Read the client default gateway instead of assuming the factory address survived.

VPN overlap

A work VPN can route 192.168.0.0/24 or 192.168.1.0/24 away from your home LAN. Disconnect the VPN for a controlled test; a long-term fix may be choosing a less-common home subnet if you administer the router.

Typos

192.168.l.l and similar letter substitutions are not IPv4 addresses. Use digits and type the address in the browser URL bar with http:// if necessary.

Diagnostic rule: prove the failing layer before changing settings

Start with physical/link state, then local IP/gateway, then router/WAN status, then DNS/application behavior. This order prevents destructive resets and random configuration changes from hiding the original problem. Write down what works and what fails after each step.

When to stop and contact the provider/vendor

Escalate when the fault is upstream of equipment you control, when provider provisioning is involved, when hardware is under warranty, or when the next step would erase settings you cannot reconstruct. Capture model, firmware, timestamps and test results first.

A four-layer field test you can use before changing configuration

1. Link and association

Verify that Ethernet shows a physical link or that Wi-Fi is connected to the intended SSID. A device connected to a similarly named guest, extender or neighbor network can make every later test misleading. On a phone, temporarily disable cellular data if you need to prove the browser is using the local LAN.

2. Local addressing

Read the client IPv4/IPv6 address, subnet/prefix, default gateway and DNS servers. A self-assigned 169.254.x.x IPv4 address usually means DHCP failed. A normal private address without a reachable gateway points to a different failure than a working gateway with no internet.

3. Gateway and WAN

Open or ping/test the gateway using a method appropriate to the device. If local management works, inspect router WAN status rather than resetting Wi-Fi. Look for WAN address, link state, lease/session status and provider alarms on modem/ONT equipment.

4. Name resolution and application

Separate DNS from connectivity. If an IP destination works but names fail, investigate resolver settings/cache. If DNS and routing work but one site/app fails, the problem may be remote, TLS-related, filtered or application-specific.

Document before escalating

Record exact error messages, timestamps, model/firmware, wired versus wireless result and whether multiple devices are affected. This turns “internet broken” into evidence an ISP or vendor can act on.

Evidence to collect before drawing a conclusion

Record the exact topology, device model/firmware, client configuration, expected result, actual result and one before/after test. Networking problems become easier when claims can be reproduced rather than described only as “slow,” “broken” or “not working.”

What not to do while diagnosing the problem

Do not factory-reset the router merely because a familiar address does not open. Do not change DNS, Wi-Fi channels, DHCP and firewall rules simultaneously. Do not download “router unlock” utilities or enter administrator credentials into a public website. Those actions add risk without proving the failing layer.

A good stopping point

Stop local troubleshooting when the evidence clearly shows a provider outage/provisioning issue, failing hardware, or a model-specific recovery process you cannot safely complete. Preserve logs/screenshots and the exact tests that isolated the fault, then escalate with those facts.

After the fault is fixed

Remove temporary test settings, reconnect any VPN/security tools you disabled, verify several devices, and document the final LAN/gateway/DNS configuration. If a reset was required, restore security settings intentionally rather than assuming every factory option is appropriate.