Tag: network troubleshooting

“Your Connection Is Not Private” Error: How to Fix It on Any Browser

Seeing “Your connection is not private”? Fix it in Chrome, Edge, Firefox, or Safari with six ranked steps — clock, cache, VPN, DNS — and get browsing again today.

The “Your connection is not private” error throws up a full-screen red warning and refuses to load the page you wanted. It looks alarming, but it almost always means your browser spotted a mismatch with the site’s SSL/TLS certificate — and the cause usually sits on your own device, not the website. The single most common trigger I run into is a system clock that drifted by a few hours.

I have cleared this error on dozens of laptops and phones, and the same short checklist fixes nearly all of them. The steps below work in Chrome, Edge, Firefox, and Safari across Windows, Mac, Android, and iPhone, ranked from quickest to most involved.

Quick Answer

Check your device’s date and time first, because a wrong clock causes this error more than anything else. If the clock is correct, clear your browser’s cache and cookies, then load the site in incognito mode. Still blocked? Disable your VPN or antivirus HTTPS scanning and retry. Most cases clear within two minutes.

What do the error codes actually mean?

Chrome and Edge print a sub-code beneath the main warning, and reading it points you straight to the right fix instead of guessing.

Error Code What It Means Best Starting Fix
NET::ERR_CERT_DATE_INVALID Device clock is wrong, or the site’s cert expired Fix 1 — correct date/time
NET::ERR_CERT_AUTHORITY_INVALID Certificate issuer not trusted by your browser Fix 4 — check antivirus HTTPS scanning
NET::ERR_CERT_COMMON_NAME_INVALID Domain name doesn’t match the certificate Try the www. or non-www. version of the URL
NET::ERR_CERT_WEAK_SIGNATURE_ALGORITHM Site uses outdated encryption Fix 6 — update your browser

Reading the sub-code first tells you which fix to try before you touch anything.

How do I fix the error step by step?

Work through these six fixes in order. I almost always solve it by Fix 3, but the later steps catch the stubborn cases.

Fix 1: Correct your device’s date and time

SSL certificates have a strict validity window. If your clock is wrong, even by a few hours, browsers reject perfectly valid certificates because they look expired or “not yet valid.”

  1. Windows: Right-click the taskbar clock → Adjust date/time → toggle Set time automatically off, then back on.
  2. Mac: Apple menu → System Settings → General → Date & Time → enable Set date and time automatically.
  3. iPhone: Settings → General → Date & Time → enable Set Automatically.
  4. Android: Settings → General Management → Date and Time → enable Automatic date and time.
  5. Reload the page after the clock syncs.

Pro tip: If your Windows PC keeps resetting to the wrong time after every reboot, the CMOS battery on the motherboard is likely dead — a common failure on machines more than five or six years old. I have swapped a couple of these myself, and the part costs only a few dollars.

Fix 2: Clear your browser’s cache and cookies

Stale cached certificate data can clash with an updated cert on the server. Clearing it forces a fresh TLS handshake.

  1. Press Ctrl+Shift+Del on Windows or Cmd+Shift+Del on Mac (works in Chrome, Edge, and Firefox).
  2. Set the time range to All time.
  3. Check Cached images and files and Cookies and other site data.
  4. Click Clear data, then reload the page.

Fix 3: Open an incognito or private window

Browser extensions — especially ad blockers, VPN add-ons, and security tools — can interfere with certificate validation. Incognito mode disables most extensions by default.

  1. Press Ctrl+Shift+N in Chrome or Edge, or Ctrl+Shift+P in Firefox.
  2. Navigate to the same URL.
  3. If the page loads, an extension is the culprit. Disable them one at a time at chrome://extensions or Firefox’s about:addons to find which one.

Fix 4: Disable your VPN or antivirus HTTPS scanning

Antivirus programs — including Avast, Kaspersky, ESET, and Bitdefender — intercept HTTPS connections and substitute their own certificate. If their certificate store is outdated, browsers flag every substituted cert as untrusted.

  1. Temporarily disable your VPN and reload the page.
  2. If it still fails, open your antivirus settings and find HTTPS scanning, Web Shield, or SSL filtering, then turn it off.
  3. If the page loads, update your antivirus to the latest version before re-enabling HTTPS scanning.

Troubleshooting tip: On corporate or school networks, a firewall or proxy may perform the same SSL interception. If you are on managed Wi-Fi and the error appears on every HTTPS site, contact your IT department — this is expected behavior and only they can resolve it.

Fix 5: Flush your DNS cache

A stale DNS record can route your browser to an outdated server IP, where the certificate no longer matches the domain. Flushing DNS forces a fresh lookup.

  1. Windows: Open Command Prompt as Administrator and run: ipconfig /flushdns
  2. Mac: Open Terminal and run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  3. Reload the page after the command completes.

Fix 6: Update your browser

Browser updates ship with new root certificates. An outdated browser may not recognize certificates signed by newer or recently added certificate authorities.

  1. Chrome: Three-dot menu → Help → About Google Chrome — it checks and installs updates automatically.
  2. Edge: Three-dot menu → Help and feedback → About Microsoft Edge.
  3. Firefox: Hamburger menu → Help → About Firefox.
  4. Restart the browser after updating, then retry the page.

Run the fixes top to bottom and you will clear the error before reaching the end in nearly every case.

Why does this error mean my device, not the site?

The certificate check happens locally, so a wrong clock, stale cache, or intercepting antivirus on your machine breaks the validation before the site is ever to blame. That is why the same page often loads fine on a phone right next to a laptop showing the error.

If your pages still misbehave after the certificate clears, a deeper cleanup helps. My guide on how to clear browser cache and cookies walks through every browser, and if the browser itself feels unstable, see how to stop Chrome from crashing. For the underlying mechanics, Let’s Encrypt’s documentation explains how TLS certificates are issued and validated.

The validation runs on your hardware, which is why local fixes resolve it far more often than anything on the server.

Common Mistakes to Avoid

  • Clicking “Advanced” and proceeding on unfamiliar sites. The bypass is meant for developers testing local servers. On a login, banking, or shopping page it exposes your credentials to interception. Fix: only proceed on sites you personally manage.
  • Clearing the cache with a short time range. Choosing “Last hour” or “Last 7 days” often leaves old cached certificates in place. Fix: always select All time.
  • Assuming the website is broken before checking your device. The common triggers — wrong clock, cached data, antivirus interference — are all local. Fix: rule them out before blaming the site.
  • Permanently disabling antivirus HTTPS scanning. Leaving it off removes real protection. Fix: turn it off only long enough to confirm the cause, then re-enable it or update the antivirus.
  • Dismissing the warning on public Wi-Fi. On open networks a persistent warning can signal a genuine man-in-the-middle attack. Fix: do not proceed on public Wi-Fi without a trusted VPN active.

Frequently Asked Questions

Is this error the same in Chrome, Firefox, and Edge?

Yes, it is the same underlying TLS certificate problem in all of them. Chrome and Edge say “Your connection is not private,” while Firefox says “Your connection is not secure.” Last week I hit the identical issue on the same site in both Chrome and Firefox after my laptop clock drifted, and one date fix cleared both.

Does this error mean I have been hacked?

Almost never — the vast majority of cases trace back to a local issue like a wrong clock, stale cache, or antivirus interference. A real man-in-the-middle attack would typically show NET::ERR_CERT_AUTHORITY_INVALID on a site that normally loads cleanly, which is rare on home Wi-Fi.

Can the website owner cause this error for all visitors?

Yes, an expired, misconfigured, or revoked certificate blocks every visitor until the owner renews or corrects it. I once watched a small store’s site go dark for an afternoon when its certificate lapsed, and nothing on my end could load it until they renewed.

Is it ever safe to click “Proceed to site (unsafe)”?

Only on sites you personally manage for local development or testing. For example, I bypass it on my own localhost dev server, but never on any page asking for a password, payment details, or personal information.

Why does the error appear in Firefox but not Chrome?

Firefox keeps its own certificate store, while Chrome and Edge use the Windows or macOS system store. An antivirus certificate injected into the OS store may not be trusted by Firefox, so I have seen the warning show up only in Firefox on the same machine.

Conclusion

This error is fixable in minutes without specialist knowledge: start with the clock, clear the cache, test in incognito, then work through the rest in order. If all six fixes fail, the problem is server-side and only the site owner can correct it. Next, tame your browser’s resource use with my guide to cutting Chrome’s RAM usage.

Last updated: June 25, 2026

iMessage Won’t Send on iPhone: How I Fix Green Bubbles and “Not Delivered” Errors

iMessage won’t send on iPhone and turning green or showing “Not Delivered”? Here is the exact order I work through to get blue bubbles back, usually in under two minutes.

When iMessage won’t send on my iPhone, iOS gives me one of two warnings: a red “Not Delivered” alert under the bubble, or the bubble flipping green because my phone quietly fell back to standard SMS. After years of fixing this for family members, I have learned that both signs point to the same thing. Something is blocking iMessage from reaching Apple’s servers, and the cause is almost always small.

The triggers range from a lapsed Apple ID session to a weak Wi-Fi signal, and most take under two minutes to clear. I work through the steps below in order, because the first one resolves it for me roughly nine times out of ten.

Quick Answer

Open Settings, tap Messages, and toggle iMessage off. Wait 10 seconds, then switch it back on and give it up to a minute to re-register. If the bubble is still green, confirm you are signed into your Apple ID and that your internet connection works. Most iMessage failures clear in under a minute this way.

The single most reliable fix is toggling iMessage off and on to force a fresh session.

Why does iMessage turn green or say “Not Delivered”?

A blue bubble means your message travelled over Apple’s iMessage network, end-to-end encrypted and free over Wi-Fi or cellular data. A green bubble means iOS fell back to SMS or MMS through your carrier, which may cost money and drops read receipts. A “Not Delivered” notice means the message failed entirely and reached the recipient by neither route.

What each warning sign means

The first time I saw a green bubble to my sister, I assumed iMessage was broken on my end. It was not. The colour and the error each map to a specific cause, so reading the sign correctly saves you from chasing the wrong fix.

Cause What you’ll see
iMessage disabled or signed out All bubbles turn green
No or weak internet connection “Not Delivered” or stuck “Sending…”
Recipient’s iMessage is off Green bubble (their end, not yours)
Apple server outage Multiple recipients affected at once
Device clock set incorrectly iMessage fails to authenticate

Match the sign to the table first, then jump straight to the fix that fits.

How do I toggle iMessage off and back on?

This clears a stale session token, and it is the first thing I try every single time because it works so often.

  1. Open Settings and tap Messages.
  2. Toggle iMessage off.
  3. Wait 10 seconds.
  4. Toggle iMessage back on and wait up to 60 seconds for registration to complete.

If you also use FaceTime, toggle it off and on at the same time, since it shares the same Apple ID authentication layer. When FaceTime is misbehaving too, my guide on fixing FaceTime when it won’t connect walks the same sign-in path.

Toggling iMessage forces a fresh registration with Apple and fixes most failures on its own.

What if my internet connection is the problem?

iMessage needs an active internet connection, and when my signal is weak the messages either queue up or fail silently with no obvious reason.

  1. Open Safari and load any website. If it fails, the problem is your connection, not iMessage.
  2. On Wi-Fi, go to Settings → Wi-Fi, toggle it off and back on, or move closer to your router.
  3. On cellular, switch Airplane Mode on for 15 seconds, then off.

Open Settings → Cellular, scroll down, and confirm iMessage is allowed to use cellular data. If that toggle is off, iMessage breaks the moment you leave Wi-Fi range. If pages won’t load at all, my walkthrough on Safari not loading on iPhone covers the connection-side steps.

Confirm a working data connection before blaming iMessage itself.

Should I sign out of my Apple ID and back in?

Yes, when the toggle looks fine but messages still fail, a corrupted iCloud credential is usually the culprit. Signing out and back in rebuilds it.

  1. Go to Settings → [your name].
  2. Scroll to the bottom, tap Sign Out, enter your Apple ID password, and choose to keep a local copy of your data.
  3. Return to Settings and sign back in with your Apple ID.
  4. Go to Settings → Messages and re-enable iMessage.

A fresh sign-in clears a broken credential that toggling alone cannot reach.

Why does my iPhone clock break iMessage?

iMessage uses your device clock to authenticate with Apple’s servers, so even a few minutes of drift can break the handshake. I once hit this after a long flight across time zones.

  1. Open Settings → General → Date & Time.
  2. Enable Set Automatically.
  3. If it was already on, toggle it off, wait five seconds, then turn it back on to force a fresh sync.

An accurate, auto-set clock keeps iMessage authentication from silently failing.

How do I reset network settings safely?

A network reset wipes saved Wi-Fi passwords, VPN profiles, and cellular APN settings to give iMessage a clean slate. It does not delete your photos, apps, or personal data, which is why I keep it as a later step rather than a scary last resort.

  1. Go to Settings → General → Transfer or Reset iPhone.
  2. Tap Reset → Reset Network Settings.
  3. Enter your passcode and confirm. Your iPhone will restart.
  4. Reconnect to your Wi-Fi network, then open Settings → Messages and confirm iMessage is still enabled.

Before you reset, check Apple’s System Status page to rule out a server-side outage. A red dot next to iMessage means the problem is Apple’s, not yours.

Reset the network last, and only after confirming Apple’s own servers are healthy.

Common Mistakes to Avoid

  • Messaging an email the recipient never linked to iMessage. Fix: switch to their phone number, which is far more likely to be registered.
  • Assuming a green bubble means you are being ignored. Fix: accept it usually means the recipient is on Android or has iMessage off, and the message still delivers as SMS.
  • Skipping the internet check. Fix: load a website first, because a silently dropped Wi-Fi session causes more “iMessage broken” reports than anything else.
  • Force-quitting the Messages app. Fix: toggle iMessage in Settings instead, since force-quitting can interrupt an in-progress sync.
  • Ignoring a full storage warning. Fix: free up space, because a packed iPhone can stop the Messages database from writing. My guide on freeing up iPhone storage fast shows the quickest wins.

Frequently Asked Questions

Why does iMessage say “Delivered” but they never got it?

“Delivered” means the message reached Apple’s servers and was pushed to their device, not that they opened it. For example, when my brother’s phone was powered off overnight, my texts showed “Delivered” yet sat unread until he turned it back on the next morning.

Can iMessage work without Wi-Fi?

Yes, iMessage runs over any active internet connection, including 4G and 5G cellular data. I send blue bubbles on the train every day with no Wi-Fi in sight, as long as iMessage is toggled on under Settings → Cellular.

Why do some contacts always show green bubbles?

Those bubbles are green because the recipient is on Android or has iMessage disabled on their Apple device. My one friend with a Pixel always lands as a green SMS thread, and nothing I change on my iPhone will ever turn it blue.

Does resetting network settings delete photos or apps?

No, a network reset only clears Wi-Fi passwords, VPN configurations, and cellular settings. When I reset my own iPhone last month, every photo, app, and message stayed exactly where it was.

Why does iMessage work on my iPad but not my iPhone?

Both devices must be signed into the same Apple ID with iMessage enabled separately. When mine drifted out of sync, I opened Settings → Messages → Send & Receive on the iPhone and found the wrong Apple ID listed there.

What if none of these fixes work?

Contact Apple Support or book a Genius Bar appointment, since the cause may be deeper. A persistent failure I troubleshot once traced to a carrier provisioning issue that only my mobile network could clear from their end.

Conclusion

Most iMessage failures come down to a stale session, a dropped connection, or a clock that slipped out of sync, and all three are fixable in under two minutes. Start with the toggle, work down the list, and you should be back to blue bubbles fast. If wireless sharing is also acting up, my guide on fixing AirDrop when it won’t find devices covers the same network layer.

Why Your Mobile Hotspot Isn’t Working — and How to Fix It Fast

Mobile hotspot not working? Fix it in minutes — switch to 2.4 GHz, confirm your data plan allows tethering, and reset network settings. Works on Android and iPhone.

The last time my mobile hotspot was not working, I was in a hotel lobby with a deadline an hour away, watching my laptop see the network but refuse to load a single page. My phone showed full bars, yet the connection was useless. Nearly every hotspot failure I have hit since then traces back to one of six things, and most of them clear in under five minutes without ever calling the carrier.

The fixes below cover both Android and iPhone, ordered from the fastest, most likely cure to the last-resort reset. Work them top to bottom and stop as soon as you are back online.

Quick Answer

Toggle the hotspot off for ten seconds, then back on. On the connecting device, forget the hotspot network and rejoin from scratch. If it is still stuck, switch the band to 2.4 GHz, confirm your carrier plan includes tethering, and check that you have not hit the connected-device limit. One of those five steps fixes most cases.

Why Does My Hotspot Connect but Show No Internet?

This is the failure I see most, and it almost always means the broadcast itself is fine but the link got stale. The first thing I do is toggle the hotspot off and rejoin from a clean slate. On Android, go to Settings → Network & Internet → Hotspot & Tethering → Wi-Fi Hotspot, switch it off, wait ten seconds, then back on. On iPhone, open Settings → Personal Hotspot and toggle Allow Others to Join off and on the same way.

On the device that is trying to connect, tap the hotspot name in the Wi-Fi list, choose Forget, then reconnect as if it were the first time. That two-step restart cleared my hotel-lobby problem in well under two minutes, and it works more often than any other single step.

Pro tip: On iPhone, turning the hotspot on from Control Center keeps it discoverable longer — the broadcast can slow or stop when the screen locks.

A clean off-and-on of the hotspot plus forgetting the network on the other device fixes most “connected but no internet” cases.

Does My Carrier Plan Actually Allow Tethering?

A hotspot draws from your phone’s cellular data, and plenty of budget plans either block tethering outright or throttle it to a crawl after a soft cap. When the hotspot toggle is greyed out or connected devices crawl at near-zero speeds, I open the carrier app first instead of blaming the hardware. Apple keeps a carrier-by-carrier Personal Hotspot guide that shows exactly which plans support it.

On iPhone, also check for a pending carrier settings update: go to Settings → General → About and wait a few seconds — a prompt appears automatically if one is available. A missed carrier update bit me right after I swapped to a new SIM, so I check this every time a plan changes.

Confirm tethering is included and your carrier settings are current before touching any other fix.

Should I Switch the Hotspot to 2.4 GHz?

Phones often default to 5 GHz or “Auto,” which is faster but struggles through walls and with older devices. If the connecting device sits more than 10 to 15 feet away or is a few years old, I switch to 2.4 GHz and the problem usually disappears on the spot. The range trade-off is worth it.

On Android: Settings → Network & Internet → Hotspot & Tethering → Wi-Fi Hotspot → AP Band → 2.4 GHz. iPhone manages the band automatically, but keeping the screen on during sharing gives me the most stable signal. The table below shows how each connection type compares.

Connection Type Range Speed Best For
Wi-Fi 2.4 GHz ~30 m (100 ft) Moderate Older devices, through walls
Wi-Fi 5 GHz ~10 m (35 ft) Fast Close range, streaming
Bluetooth tethering ~10 m Slow Low-data tasks, saves battery
USB tethering Wired Fastest Reliable sessions, charges phone

Drop to 2.4 GHz whenever distance, walls, or an older device are in play.

Have You Hit the Connected-Device Limit?

Most hotspots allow only 5 to 10 devices at once. When the cap is reached, new devices are refused silently — no error message, just no connection. On Android, go to Settings → Hotspot & Tethering → Connected Users (the exact label varies by version) to see what is joined and disconnect anything you are not using.

On iPhone there is no visible device list, so the fastest move I have found is to change the hotspot password. That boots everyone at once and lets you reconnect only the devices you actually need.

If new devices connect to nothing, you have probably maxed out the device cap — clear the unused ones first.

Could Outdated Software Be Breaking the Hotspot?

Outdated firmware can quietly break tethering, and I have watched a single pending update fix a hotspot that resisted everything else. On Android: Settings → System → System Update. On iPhone: Settings → General → Software Update. Carrier settings update separately on iPhone — check under Settings → General → About and wait for a prompt.

A pending carrier update is a frequent culprit right after a plan change, so I treat any recent switch as a reason to check here before going further.

Install both OS and carrier updates whenever the hotspot started failing after a recent change.

When Should I Reset Network Settings?

When nothing above has worked, a network reset clears the corrupted APN, DNS, and Wi-Fi configurations that silently block hotspot traffic. I save this for last because it wipes every saved network.

  • Android: Settings → System → Reset Options → Reset Wi-Fi, Mobile & Bluetooth
  • iPhone: Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings

Troubleshooting tip: Have your home Wi-Fi password ready before you start — the reset erases all saved networks. If the connecting device still shows the network but loads nothing afterward, our guide on fixing Wi-Fi that connects with no internet walks through the deeper steps.

Reset network settings only as a last resort, and have your saved passwords ready first.

Common Mistakes to Avoid

  1. Letting the iPhone screen lock during sharing. iOS slows or stops broadcasting when the screen is off too long. Fix: set Auto-Lock to 5 minutes and plug into a power bank so the screen can stay lit without draining the battery.
  2. Misreading the hotspot password. Zero and the letter O, and numeral 1 and lowercase l, are easy to confuse. Fix: open hotspot settings and read the password character by character instead of typing from memory.
  3. Using 5 GHz through walls or across rooms. 5 GHz barely penetrates solid walls. Fix: move both devices to line-of-sight or set 2.4 GHz as your default — you rarely notice the speed difference on browsing or email.
  4. Calling carrier support before rebooting both devices. Restarting the phone and the connecting device takes about 60 seconds. Fix: always do this before dialing support, since it resolves roughly half of hotspot problems.
  5. Assuming a hardware fault when the data cap was hit. Many plans throttle hotspot speed to near-unusable levels after a soft cap. Fix: if pages load slowly rather than not at all, check your usage in the carrier app first.

Frequently Asked Questions

Why can my device see the hotspot but not connect?

It is usually a wrong password, a full device list, or a band mismatch. Forget the network on the connecting device, verify the exact password in hotspot settings, and rejoin. Last month a teammate’s laptop refused my hotspot until we noticed he had typed a capital O where the password used a zero.

How many devices can connect to a mobile hotspot at once?

Most phones support 5 to 10 simultaneous connections, though carriers can lower that cap. Check the settings under your hotspot section for the exact limit. On a road trip with three laptops and two phones sharing one hotspot, I had to drop an idle tablet before a fourth laptop could join.

Does using a mobile hotspot use a lot of data?

Yes — streaming video or video calls can burn several gigabytes per hour. Pause background app updates and cloud backups on connected devices to protect your allowance. I once watched a single afternoon of video calls eat 4 GB before I caught it.

Can I use the hotspot while on a phone call?

On 4G LTE and 5G networks, yes — calls and data run at the same time. On older networks, some phones pause data during a call. Enabling Wi-Fi Calling sidesteps this entirely, which is what I switched on after a 3G-only client kept dropping my shared connection mid-call.

My hotspot connects but shows no internet — what is wrong?

The phone itself most likely lost cellular data, not the hotspot. Toggle Airplane Mode on for five seconds, then off; if cellular does not return, restart the phone. When this happened to me on a Windows laptop, the real issue was DNS — our guide on the DNS server not responding error covers the next steps.

What is the difference between hotspot and USB tethering?

A hotspot creates a wireless network other devices join over Wi-Fi, while USB tethering links one device by cable. Tethering is faster, more stable, and charges your phone at the same time. On a four-hour upload I needed to finish, I chose USB tethering and it never dropped once.

Conclusion

A mobile hotspot that will not cooperate almost always responds to one of the six steps above — restart and rejoin, switch to 2.4 GHz, check your plan, then reset network settings as a last resort. For persistent Wi-Fi drops on a Windows PC after connecting, see our guide on fixing Wi-Fi that keeps disconnecting.

Bookmark this page so the checklist is ready the next time your hotspot quits at the worst possible moment.

Safari Not Loading on iPhone: How I Get It Working Again

Safari not loading on your iPhone? I walk through seven ranked fixes — Airplane Mode, force-quit, cache, DNS, and more — so pages start opening again fast.

You tap a link, Safari spins for a second, then nothing loads. Or you see the message “Safari cannot open the page because your iPhone is not connected to the internet,” even though Wi-Fi shows full bars. I have hit this on my own iPhone more times than I can count, usually right when I needed a boarding pass to load, and the cause is almost never as serious as it feels. Safari not loading on iPhone almost always traces back to a stale network connection, corrupted browser data, or a temporary software glitch, and you can fix all three yourself in minutes.

The fixes below run from fastest to most thorough. Most people are back online before they reach the fourth one, so work down the list in order and stop the moment a page loads.

Quick Answer

To fix Safari not loading on iPhone, open Control Center and toggle Airplane Mode on, wait five seconds, then turn it off. Next, force-quit Safari and reopen it. If pages still fail, go to Settings > Safari > Clear History and Website Data, then restart your iPhone. Most users are back online in under two minutes.

Does your iPhone actually have internet? Toggle Airplane Mode

Before blaming Safari, confirm your iPhone actually has internet access. Open another app that needs the internet, such as Maps or Mail. If that also fails to load, the problem is your network connection, not the browser itself.

  1. Swipe down from the top-right corner to open Control Center.
  2. Tap the Airplane Mode icon to turn it on. Wait five seconds.
  3. Tap it again to turn it off. Your iPhone reconnects to Wi-Fi or cellular.
  4. Try loading a page in Safari.

When I am on hotel or café Wi-Fi, this is also where I get caught: after reconnecting, I navigate to any http:// URL to force the network login page to appear. These public networks often require you to accept a terms or sign-in screen before they allow real browsing, and Safari will load nothing until you do.

If other apps fail too, fix the network with an Airplane Mode toggle before you touch Safari.

Is Safari frozen? Force-quit and reopen it

A Safari session can lock up without fully crashing, so the app looks open but no page ever finishes. Force-quitting clears the stuck process in seconds, and it is the step I reach for the instant the spinner stalls.

  1. Swipe up from the bottom edge (Face ID models) or double-press the Home button (Touch ID models) to open the App Switcher.
  2. Swipe the Safari card upward and off the screen.
  3. Return to your Home Screen and open Safari again.

A frozen Safari process clears in seconds once you swipe its card away in the App Switcher.

Will a restart fix Safari not loading?

A restart clears temporary memory, resets background processes, and refreshes your network stack. In my experience it resolves more Safari loading issues than any other single step, so I do it early rather than treating it as a last resort.

  1. Hold the Side button and either Volume button until the power slider appears.
  2. Drag the slider to shut down.
  3. After 30 seconds, hold the Side button until the Apple logo appears.

A full restart refreshes the network stack and fixes more loading failures than any other single step.

Could corrupted cache be blocking pages? Clear Safari data

Corrupted cached files or outdated cookies can silently block pages from loading correctly, even when your connection is fine. Clearing them gives Safari a clean slate.

  1. Go to Settings > Safari.
  2. Scroll down and tap Clear History and Website Data.
  3. Confirm by tapping Clear History and Data.

This signs you out of websites and removes your browsing history, but your bookmarks and Reading List are untouched. After a long trip, this is the step that fixed a half-loading airline site for me when nothing else would.

Clearing history and website data wipes corrupted cache without removing your bookmarks or Reading List.

Is Screen Time blocking the site?

Screen Time restrictions can silently block entire websites, even ones you need for work or school, and you may not remember ever setting them. I once spent ten minutes troubleshooting a “broken” site that turned out to be on a Never Allow list I had forgotten about.

  1. Go to Settings > Screen Time > Content & Privacy Restrictions.
  2. Tap Content Restrictions > Web Content.
  3. Make sure it shows Unrestricted Access, or review the “Never Allow” list for blocked sites.

If Screen Time shows a passcode prompt you do not recognise, check whether Family Sharing is active under your Apple ID. A family organiser may have set restrictions remotely, and only they can remove them.

Check Web Content under Screen Time when one specific site refuses to load but others work fine.

Which DNS server should you switch to?

Your carrier’s default DNS servers can go down or slow to a crawl, making Safari look broken when it is really a name-resolution problem. Switching to a faster public DNS such as Cloudflare’s 1.1.1.1 often fixes it immediately at no cost. I keep 1.1.1.1 set on my home Wi-Fi for exactly this reason.

  1. Go to Settings > Wi-Fi and tap your network name.
  2. Tap Configure DNS and switch from Automatic to Manual.
  3. Tap Add Server and enter 1.1.1.1.
  4. Remove the original server entries and tap Save.
DNS Provider Primary Secondary Best For
Cloudflare 1.1.1.1 1.0.0.1 Speed and privacy
Google 8.8.8.8 8.8.4.4 Reliability
OpenDNS 208.67.222.222 208.67.220.220 Family content filtering

Set Manual DNS to 1.1.1.1 on your Wi-Fi when sites time out but the connection itself looks healthy.

Does updating iOS fix Safari bugs?

Safari is built into iOS, so browser bugs are patched through system updates, not through the App Store. If you are running an older iOS version, a known bug may be causing the loading failure, and the fix is simply staying current.

  1. Connect your iPhone to Wi-Fi and plug it in to charge.
  2. Go to Settings > General > Software Update.
  3. If an update is available, tap Download and Install.

If the update itself stalls, see my walkthrough on what to do when an iOS update won’t install before retrying Safari.

Updating iOS patches the Safari engine directly, since the browser ships as part of the system.

Common Mistakes to Avoid

  • Clearing Safari data while offline. Clearing cache works best when a live connection is ready to reload pages. Fix the network first, then clear data.
  • Assuming the site is down. Test the same URL in Chrome on your iPhone or on another device. If it loads there, Safari, not the website, is the problem.
  • Skipping the restart. Most people try everything else first because a restart feels excessive. Do not skip it; it fixes more loading failures than any other step here.
  • Changing DNS on cellular. The DNS fix only applies to Wi-Fi networks. Cellular DNS is controlled by your carrier and cannot be changed from Settings.
  • Running an outdated iOS version. Safari bugs are patched through iOS updates, not standalone browser updates, so keeping iOS current is the best long-term prevention.

Frequently Asked Questions

Why does Safari say “server cannot be found” on some sites but not others?

It is a DNS resolution error: Safari looked up the domain name but got no result back. Switch to a public DNS server or toggle Airplane Mode to clear your DNS cache. When this happened to me on a flaky office network, setting 1.1.1.1 manually cleared it instantly.

Will clearing history and website data delete my saved passwords?

No. Passwords stored in iCloud Keychain are kept separately and survive the clear. Only browsing history, cookies, and cached files are removed. I clear my Safari data regularly and have never had to re-enter a saved login afterward.

Safari won’t load on Wi-Fi but works on cellular, why?

The problem is specific to that Wi-Fi network, not your iPhone. Forget and rejoin the network, then switch to a public DNS. On my home network, the fix was power-cycling the router after a firmware update left it serving bad DNS.

Can a VPN cause Safari to stop loading pages?

Yes. VPN apps can route traffic through slow or geo-blocked servers that never respond. Disable your VPN temporarily and test Safari; if pages load without it, the VPN configuration is the cause. Mine started failing after a server I used was taken offline.

How do I reset Safari without losing my bookmarks?

Use Clear History and Website Data, which preserves all bookmarks and your Reading List. Only browsing history, cookies, and cached site data are removed. I rely on this every time a site half-loads, and my saved pages have always stayed intact.

Conclusion

Safari not loading on iPhone almost always comes down to a network glitch, stale cache, or an iOS bug, all fixable in a few minutes without a tech appointment. Start with the Airplane Mode toggle and a force-quit, then work down the list until a page loads.

Dealing with other iPhone headaches? Learn how to free up iPhone storage when it’s full or get six proven fixes for an iPhone that won’t charge, two issues that often surface alongside browsing trouble.

Android Won’t Connect to Wi-Fi? How to Get Back Online Fast

When my Android wouldn’t connect to Wi-Fi, these fixes got it back online in minutes — forget the network, reset network settings, switch DNS, and more. Try them in order.

My phone showed a full Wi-Fi signal, yet nothing loaded — and the next morning it hung on “Obtaining IP address” and never joined at all. I have hit this on my own Pixel and on a Samsung I was helping a friend with, and the cause was almost never broken hardware. An Android that won’t connect to Wi-Fi is nearly always a software hiccup you can clear in minutes from Settings.

Most of these failures trace back to a stale network cache, a duplicate IP address, a wrong saved password, or a small software bug. I have ordered the fixes below the way I actually work through them — quickest first — so you stop as soon as one sticks.

Quick Answer

To fix an Android that won’t connect to Wi-Fi, toggle Airplane Mode on and off, then forget the network and reconnect with the password. If that fails, restart both your router and phone. For stubborn cases, open Settings > General Management > Reset > Reset Network Settings to wipe saved network data and start fresh.

Why won’t my Android connect to Wi-Fi?

Android Wi-Fi failures almost always come down to one of these causes:

  • Stale network settings — your phone is holding old IP or DNS data that no longer matches the router.
  • IP address conflict — two devices on the network grabbed the same IP address.
  • Authentication error — the saved password no longer matches, common after a router or password change.
  • Router issue — the fault is with the router, not your phone.
  • Software bug — a recent Android update introduced a Wi-Fi glitch.

The first time my own phone did this, the culprit was a stale lease after my ISP swapped the router — a 30-second reset fixed it. Working through the steps below in order covers every one of these causes in well under 15 minutes.

How do I quickly reset the Wi-Fi connection?

Toggle Airplane Mode on and off

This 10-second move forces Android to drop every wireless connection and rebuild it clean. It is the first thing I try, every time.

  1. Swipe down from the top of the screen to open Quick Settings.
  2. Tap Airplane Mode to turn it on, then wait 10 seconds.
  3. Tap Airplane Mode again to turn it off.
  4. Give Wi-Fi a moment to reconnect, then test it.

If the toggle is not in your shortcuts, swipe down twice to expand the full Quick Settings panel.

Restart your phone and router

A full restart clears temporary memory and re-establishes the connection from scratch. In my experience this single step fixes the problem more often than any other.

  1. Hold the power button and select Restart.
  2. While the phone reboots, unplug the router’s power cable, wait 30 seconds, then plug it back in.
  3. Wait 60 seconds for the router to fully start before reconnecting.

If other devices on the network also have no internet, the fault is the router or your ISP — not your phone. If a restart does not help and only mobile data is affected, see my guide to Android mobile data not working.

Toggling Airplane Mode and restarting both devices clears the most common stalls in under two minutes.

How do I fix Android connected to Wi-Fi but no internet?

Forget the network and reconnect

A corrupted Wi-Fi profile causes endless failures. Deleting it and reconnecting fresh clears authentication errors right away.

  1. Go to Settings > Wi-Fi (or Settings > Network & Internet > Wi-Fi on stock Android).
  2. Tap and hold the problem network, then select Forget. On some phones, tap the gear icon next to the network, then choose Forget.
  3. Tap the network again and re-enter the password carefully.

Passwords are case-sensitive. If you are unsure of yours, check the label on the back or bottom of the router.

Switch to Google’s public DNS

A slow or broken DNS server stops pages from loading even when the phone is technically connected. Pointing it at Google’s public DNS is free, fast, and per Google’s own Public DNS documentation, uses the addresses 8.8.8.8 and 8.8.4.4.

  1. Go to Settings > Wi-Fi, tap the gear icon next to your network, then expand Advanced options.
  2. Set IP settings to Static.
  3. Set DNS 1 to 8.8.8.8 and DNS 2 to 8.8.4.4.
  4. Tap Save and test the connection.

The day my pages loaded at a crawl on a hotel network, swapping to 8.8.8.8 fixed it instantly while the default DNS stayed dead. If you are connected but nothing loads, a DNS swap or a forget-and-reconnect almost always restores the internet.

How do I fix an IP address conflict on Android?

Assign a static IP

If two devices share the same IP address, neither connects reliably. Giving your phone a static IP sidesteps the clash entirely.

  1. Go to Settings > Wi-Fi, tap the gear icon next to your network, then Modify Network (or Edit) and expand Advanced options.
  2. Change IP settings from DHCP to Static.
  3. In the IP address field, change the last number to something high, like 192.168.1.200, to avoid clashing with other devices.
  4. Leave the Gateway field unchanged, then tap Save.

Clear the Wi-Fi system cache

Android stores Wi-Fi configuration data that can corrupt over time. Clearing the cache removes stale entries that block new connections.

  1. Go to Settings > Apps, tap the three-dot menu, and select Show system apps.
  2. Find Wi-Fi or WifiConfigStore.
  3. Tap it, then go to Storage > Clear Cache.

The exact name varies by Android version and maker; if you cannot find it, this step simply is not available on your device — move on. A static IP plus a cache clear resolves the intermittent, random-looking drops that nothing else explains.

What should I do when nothing else works?

Verify your date and time

A wrong date or time triggers SSL certificate errors that silently break Wi-Fi authentication, especially on hotel and café login pages.

  1. Go to Settings > General Management > Date and Time (Samsung) or Settings > System > Date & Time (stock Android).
  2. Make sure Automatic date and time is on.
  3. If it was already on, toggle it off, wait 10 seconds, then back on to force a resync.

Reset network settings

This returns Wi-Fi passwords, Bluetooth pairings, and mobile data settings to factory defaults without touching personal data. It is the single most effective fix for persistent problems.

  1. Go to Settings > General Management (Samsung) or Settings > System (stock Android).
  2. Tap Reset > Reset Network Settings.
  3. Confirm and let it finish; the phone restarts automatically.
  4. Reconnect to Wi-Fi and enter the password again.

Write down your Wi-Fi passwords and note your Bluetooth devices first, since you will re-enter and re-pair them all afterward. If pairing acts up later, my guide to Android Bluetooth not pairing covers it.

Install pending software updates

Wi-Fi bugs are routinely patched in Android updates and security releases. If your phone is on outdated software, a known fix may already be waiting.

  1. Go to Settings > Software Update (Samsung) or Settings > System > System Update (stock Android).
  2. Tap Check for Updates and install anything available.
  3. Restart the phone and test Wi-Fi.

A network reset followed by any pending update clears the deepest software faults short of a factory reset.

Common Mistakes to Avoid

  1. Restarting only the phone, not the router. A stuck IP lease lives on the router. Fix: restart both devices together.
  2. Typing the password wrong. Passwords are case-sensitive. Fix: confirm it on the router label or connect another device with the same credentials.
  3. Jumping to a factory reset. That wipes photos, apps, and data. Fix: Reset Network Settings solves most of the same problems without erasing anything.
  4. Ignoring IP conflicts. Duplicate IPs cause failures that look random. Fix: check the router’s connected-device list for duplicate addresses and assign a static IP.
  5. Forgetting the captive portal. Hotels and cafés need a login page before the internet works. Fix: open a browser to trigger the portal and accept the terms.

Frequently Asked Questions

Why does my Android say “Connected” but there’s no internet?
The phone reached the router, but the router can’t reach the internet or DNS is failing. Switch to Google DNS (8.8.8.8) and restart the router. When I had this at home, every device was offline too, which pointed straight at the ISP rather than my phone.

Why does my Android keep disconnecting from Wi-Fi?
Repeated drops usually come from aggressive battery saving that powers down the Wi-Fi radio. Ease off battery optimization for network services. On my old phone, moving it closer to the router also stopped the drops, since a weak signal was half the problem.

Will resetting network settings delete my photos or apps?
No. Reset Network Settings only clears Wi-Fi passwords, Bluetooth pairings, and mobile data settings. I have run it many times and my photos, contacts, and apps were always untouched.

My Android connects but pages load very slowly. What’s wrong?
Slow loading on a connected signal usually means a DNS problem or a congested network. Switch to 8.8.8.8 and 8.8.4.4 first. When my whole household was slow, the bottleneck turned out to be the ISP, not any single phone.

Why does my Android connect to some Wi-Fi networks but not others?
The fault is that network’s configuration, not your phone. It may use MAC filtering or a security protocol your device dislikes. At a friend’s house, forgetting and reconnecting fixed a WPA3 mismatch for me in seconds.

Conclusion

Android Wi-Fi trouble is almost always fixable without a store visit. Start with the quick wins — Airplane Mode, a router restart, and forget-and-reconnect — then move to Reset Network Settings if needed.

If your phone is still sluggish or burning battery after reconnecting, read how I handle a slow Android phone and an Android battery draining fast — and try these steps before booking any repair.

ChatGPT Not Working? A Calm, Step-by-Step Recovery Guide

ChatGPT not working again? I walk through the exact checks I run — server status, cache, extensions, VPN, and DNS — to get it answering in minutes flat.

You type a question into ChatGPT, hit enter, and nothing comes back — just “An error occurred,” a “Network error,” or a spinner that never stops. The first time it happened to me mid-deadline, I assumed my account was banned. Almost every time ChatGPT stops working, the cause is something temporary on your own device, not a ban or a dead account.

Quick Answer

When ChatGPT is not working, first check status.openai.com for an outage. If servers are healthy, do a hard refresh (Ctrl + Shift + R on Windows, Cmd + Shift + R on Mac), then clear your browser cache and cookies. Still stuck? Disable extensions or open ChatGPT in an incognito window to isolate the cause.

Is ChatGPT Actually Down, or Is It Just Me?

Before changing a single setting, I confirm the problem is not on OpenAI’s end. It takes ten seconds and saves a lot of pointless troubleshooting.

  1. Open status.openai.com in a new tab.
  2. Look for active incidents or any “degraded performance” notice.
  3. If an outage is listed, the only real fix is to wait — OpenAI’s engineers are already on it.

On the status page I always click “Subscribe to updates.” The one time servers were genuinely down, I got an email the moment service returned instead of refreshing the page every two minutes. If you want a backup tool while you wait, my comparison of ChatGPT vs Gemini vs Claude shows which free chatbot to switch to for the task at hand.

If the status page shows green, the problem is on your device — keep going.

How Do I Force ChatGPT to Reload Cleanly?

A normal refresh (F5 or Ctrl + R) reloads the page from your browser’s cache, which may be the exact broken file causing the error. A hard refresh forces a fresh download straight from OpenAI’s servers.

  1. Click anywhere inside the ChatGPT tab.
  2. Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac).
  3. Wait for the page to fully reload, then send a test message.

When a hard refresh leaves the page blank or stuck, I stop and move to the cache clear below — that pattern usually means the cached data is corrupted, not merely stale.

A hard refresh fixes the broken-file errors a plain refresh quietly reloads.

Why Does Clearing My Cache and Cookies Fix ChatGPT?

Expired session cookies and corrupted cache files are the single most common cause of persistent ChatGPT errors I see. Clearing them forces a clean login and wipes out the bad data that keeps tripping the page.

In Google Chrome

  1. Press Ctrl + Shift + Delete (Windows) or Cmd + Shift + Delete (Mac).
  2. Set the time range to All time.
  3. Check Cached images and files and Cookies and other site data.
  4. Click Clear data.
  5. Reload ChatGPT and log back in.

The same shortcut opens an almost identical dialog in Firefox and Microsoft Edge. One detail that matters: if you suspect a corrupted session, log out of ChatGPT first, then clear cookies, then log back in. Logging out first ensures the bad session token is fully removed rather than left behind.

Clearing cache and cookies after a clean logout resolves most stubborn, repeat errors.

Can a Browser Extension Stop ChatGPT From Replying?

Yes — and this one fooled me for an hour once. Ad blockers, script blockers, and privacy extensions can silently block the JavaScript requests ChatGPT needs to stream responses. There is often no error at all: the interface loads, but it never answers.

  1. In Chrome, click the puzzle-piece icon at the top right and choose Manage Extensions.
  2. Toggle every extension off.
  3. Reload ChatGPT and test it.
  4. If it works, switch extensions back on one at a time until the culprit appears.

In my case, uBlock Origin in aggressive-filtering mode was blocking OpenAI’s endpoint, so ChatGPT loaded visually but never sent my message. The faster test: open an incognito window, where extensions are disabled by default. If ChatGPT works there, an extension is your problem.

A blocking extension can break ChatGPT with no error message at all.

Does Incognito Mode or a Different Browser Help?

An incognito (private) window isolates you from stored cookies, cached data, and most extensions in a single move, so it is my fastest test for browser-specific trouble.

  1. Press Ctrl + Shift + N (Chrome/Edge) or Ctrl + Shift + P (Firefox).
  2. Go to chat.openai.com and test ChatGPT.

If it works in incognito, the fix lives in your normal browser — clear the cache or hunt down the extension. If it still fails in incognito, open a completely different browser to rule out browser-level corruption entirely. One catch: some extensions are allowed to run in incognito, so check each one’s incognito permission under Manage Extensions if a private window still misbehaves.

Incognito mode tells you in seconds whether your normal browser profile is the problem.

Could My VPN or DNS Be Blocking ChatGPT?

Both can, and they produce nearly identical “it just won’t connect” symptoms. VPNs route traffic through shared servers, and OpenAI sometimes rate-limits or blocks IPs tied to busy exit nodes. A stale DNS entry for OpenAI’s servers triggers “network error” messages even when your Wi-Fi looks perfect.

Turn Off Your VPN or Proxy

  1. Open your VPN app and disconnect completely.
  2. Reload ChatGPT and test without the VPN active.
  3. If it works, reconnect using a different server location — ideally one geographically closer to you, since those carry less flagged traffic.

Flush Your DNS Cache

First confirm the internet itself is fine at fast.com or speedtest.net, then flush DNS.

On Windows

  1. Press Win + R, type cmd, and press Enter.
  2. Type ipconfig /flushdns and press Enter.
  3. You will see “Successfully flushed the DNS Resolver Cache.”
  4. Reload ChatGPT.

On Mac

  1. Open Terminal (search in Spotlight).
  2. Type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  3. Enter your Mac password and press Enter.
  4. Reload ChatGPT.

If the network errors persist after this, the issue is broader than ChatGPT, and OpenAI’s own help center documents service-side connection problems worth ruling out.

A flagged VPN IP or a stuck DNS entry can make ChatGPT look completely broken while everything else loads fine.

Which Fix Should I Try First?

When I am short on time, I work top to bottom — the fixes are ordered by how often they solve the problem versus how long they take.

Fix Best for Time
Check server status Total outage, error on every device 10 sec
Hard refresh Blank page, stuck spinner 15 sec
Clear cache + cookies Repeat errors, login loops 2 min
Disable extensions Loads but never replies 2 min
VPN off / DNS flush “Network error” only 1 min

For a sibling tool that throws similar errors, the same logic powers my guide on Google Gemini not responding.

Working the table top to bottom resolves most cases by the cache or extension step.

Common Mistakes to Avoid

  • Assuming it is always an outage. Most errors are local. If status.openai.com shows green, keep troubleshooting your own device.
  • Using a normal refresh instead of a hard refresh. Ctrl + R reloads from cache; Ctrl + Shift + R forces a fresh download. Use the hard refresh.
  • Forgetting extensions can run in incognito. If you granted incognito access, the extension can still break ChatGPT there — check its permissions under Manage Extensions.
  • Reconnecting to the same VPN server. Toggling off and back on to the same node changes nothing. Switch locations or disable the VPN while testing.
  • Clearing cookies without logging out first. A corrupted session token can survive a cache clear. Log out, clear, then log back in.

Skip these five traps and you avoid the dead ends that waste the most troubleshooting time.

Frequently Asked Questions

Why does ChatGPT say “An error occurred”?
It usually means a server-side hiccup, an expired session token, or a dropped connection. Clearing your cache and disabling extensions fixes it in most cases. Last week mine cleared instantly the moment I logged out, wiped cookies, and signed back in.

Is ChatGPT down right now?
Check status.openai.com for live server status. If no incident is listed but ChatGPT still fails, the problem is on your device or local network. I once spent ten minutes blaming OpenAI before realizing my own VPN was the block.

Why does ChatGPT keep stopping in the middle of a response?
A brief connection dip while ChatGPT streams the reply is the usual cause, though hitting the output limit also cuts answers short. Switch to wired Ethernet or move closer to your router; for the token-limit version, see my guide on why ChatGPT cuts off mid-response.

Why can’t I log in to ChatGPT?
Clear your cookies and cache fully, then try again. When I use “Sign in with Google,” I open a separate tab first to confirm that account is working, which has saved me twice from blaming ChatGPT for a Google session glitch.

Does a VPN stop ChatGPT from working?
Not always, but it can — some VPN IP ranges are rate-limited by OpenAI. Disable the VPN and test; if it loads, reconnect on a different server. A nearby server location fixed it for me every time.

Why does ChatGPT work on my phone but not my computer?
Your desktop browser likely has a conflicting extension, a corrupted cache, or different DNS than your phone. Start with the cache clear and extension check on the computer. That combination has resolved every phone-works-but-laptop-fails case I have hit.

Conclusion

Nearly every “ChatGPT not working” moment comes down to a quick server check, a hard refresh, a cache clear, a disabled extension, or a VPN and DNS reset. Work the list top to bottom and you will usually be back in business within a minute or two.

Bookmark this page so the next time ChatGPT throws an error, your fix checklist is one click away.

DNS Server Not Responding on Windows: How I Get Back Online

DNS server not responding on Windows? I walk through the exact sequence I use — flush the cache, restart the router, and swap to 8.8.8.8 — to load pages again in minutes.

You type a website, hit Enter, and Windows throws back “DNS server not responding.” Your Wi-Fi icon still shows connected, yet nothing loads. The error means your PC could not translate a site name like google.com into the numeric IP address it needs, a job handled by DNS (the Domain Name System), which works like the internet’s phone book. Almost every time I see this, the cause is a stale cache, a router hiccup, or one wrong DNS setting — not a broken connection.

I have fixed this on dozens of friends’ laptops, and the same short sequence clears it nearly every time. Below is exactly what I run, in order, starting with the fastest move.

Quick Answer

To fix “DNS server not responding” on Windows, restart your router, then open Command Prompt as administrator and run ipconfig /flushdns. If the error stays, switch your DNS to Google (8.8.8.8 / 8.8.4.4) or Cloudflare (1.1.1.1 / 1.0.0.1) in your adapter settings. Those three steps resolve most cases.

What causes “DNS server not responding”?

When you request a website, Windows asks a DNS server for that site’s IP address. If the lookup fails, you get this error. The usual culprits:

  • Router crash or overload — your router needs a restart to clear its memory.
  • Corrupted DNS cache — old or wrong records saved on your PC break the lookup.
  • ISP’s DNS server is down — your provider’s servers are slow, overloaded, or offline.
  • Outdated network adapter driver — the software running your Wi-Fi or Ethernet card has a bug.
  • Antivirus or firewall blocking DNS — security software intercepts requests and blocks them by mistake.
  • Corrupted TCP/IP stack — Windows’ core networking settings have gone wrong.

The error is almost always a small software glitch on your PC or router, not a dead connection.

How do I quickly restart the router and modem?

A router restart is the single most effective first step. It clears the router’s memory, drops stale connections, and pulls a fresh DNS assignment from your ISP. When every device in the house is affected — phones, tablets, laptops — this is almost certainly the fix. The first time it happened to me, this alone solved it before I touched a single Windows setting.

  1. Unplug your router (and modem, if it is a separate box) from the power outlet.
  2. Wait 30 seconds.
  3. Plug the modem back in first. Wait until its lights stabilize — about 60 seconds.
  4. Plug the router back in. Wait another 60 seconds.
  5. Try loading a website on the affected device.

Pro tip: Always unplug the power cable rather than pressing the router’s physical Reset button. The Reset button restores factory settings and wipes your custom Wi-Fi password — pulling the power does not.

Power-cycling the router fixes the majority of whole-house DNS errors in under three minutes.

How do I flush the DNS cache?

Windows saves DNS lookups in a local cache to speed up browsing, but that cache can go stale or corrupt. Flushing it forces Windows to fetch fresh records for every site. This is the step that bails me out most often on a single problem PC.

  1. Press Windows key + R, type cmd, then press Ctrl + Shift + Enter to open Command Prompt as administrator.
  2. Type this command and press Enter:
    ipconfig /flushdns
  3. You should see: “Successfully flushed the DNS Resolver Cache.”
  4. Restart your browser and test a website.

Troubleshooting tip: If you see “Access is denied,” you did not open Command Prompt as administrator. Close it, search for Command Prompt in the Start menu, right-click it, and choose Run as administrator.

Flushing the cache clears most single-device DNS failures without changing any settings.

Which DNS server should I switch to?

Your ISP’s DNS server may be down or just slow. Switching to a fast public resolver is one of the most reliable fixes, and it often speeds up browsing as a bonus. I keep Cloudflare set on my own machine for exactly this reason.

  1. Press Windows key + R, type ncpa.cpl, and press Enter to open Network Connections.
  2. Right-click your active connection (Wi-Fi or Ethernet) and select Properties.
  3. Click Internet Protocol Version 4 (TCP/IPv4), then click Properties.
  4. Select Use the following DNS server addresses and enter:
    Preferred DNS server: 8.8.8.8
    Alternate DNS server: 8.8.4.4
  5. Click OK, then Close. Open a browser and test.

Not sure which resolver to pick? Here are the three most popular free options and their addresses:

Provider Primary DNS Secondary DNS
Google Public DNS 8.8.8.8 8.8.4.4
Cloudflare 1.1.1.1 1.0.0.1
OpenDNS 208.67.222.222 208.67.220.220

Cloudflare’s 1.1.1.1 is consistently among the fastest resolvers worldwide and takes a privacy-first approach. If you want the full walkthrough for phones, Macs, and your router too, see my guide on how to change your DNS server on any device. You can confirm a public resolver is reachable on Cloudflare’s DNS status page.

A public resolver replaces a flaky ISP DNS and frequently makes pages load faster too.

What if the error still will not clear?

If the first three steps did not work, the problem sits deeper in Windows. Work through these in order.

Restart the DNS Client service

Windows runs a background DNS Client service that handles every lookup. If it froze, restarting it can clear the error on its own.

  1. Press Windows key + R, type services.msc, and press Enter.
  2. Scroll to DNS Client.
  3. Right-click it and select Restart.
  4. If Restart is greyed out, Windows is managing the service automatically — move on.

Reset the TCP/IP stack and Winsock

The TCP/IP stack and Winsock catalog are the core pieces Windows uses on any network. Corruption in either causes persistent DNS errors. Resetting them is safe and takes about two minutes.

  1. Open Command Prompt as administrator.
  2. Run each command, pressing Enter after each:
    netsh winsock reset
    netsh int ip reset
    ipconfig /release
    ipconfig /flushdns
    ipconfig /renew
  3. Restart your computer once all commands finish.

Troubleshooting tip: If ipconfig /renew reports “media disconnected,” skip it — that is normal for Wi-Fi adapters in certain states and does not affect the reset.

Update or roll back the network adapter driver

An outdated or buggy driver can cause intermittent DNS failures. Updating usually fixes it, but if the error started right after a Windows update, rolling back is often the answer.

  1. Right-click the Start button and choose Device Manager.
  2. Expand Network Adapters.
  3. Right-click your Wi-Fi or Ethernet adapter and select Update driver → Search automatically for drivers.
  4. If the error followed a recent update, open the adapter’s Properties, go to the Driver tab, and click Roll Back Driver.

Temporarily disable antivirus or firewall

Some antivirus tools and third-party firewalls intercept DNS requests to scan them and can block them by accident. Disabling protection briefly is a safe test — just avoid untrusted sites while it is off.

  1. Right-click your antivirus icon in the system tray (bottom-right of the taskbar).
  2. Choose an option like Disable protection, Pause, or Turn off temporarily.
  3. Try loading a website. If it works, your security software is the culprit.
  4. Re-enable protection immediately after the test.
  5. Look for DNS filtering, “Web Shield,” or HTTPS scanning in its settings and add an exclusion, or ask the vendor’s support team.

These deeper resets clear the stubborn cases that survive a router restart and a cache flush.

Common Mistakes to Avoid

  • Pressing the router’s physical Reset button instead of power-cycling it. That button restores factory settings and deletes your Wi-Fi password. Fix: unplug the power cable instead — same effect, no side effects.
  • Skipping “Run as administrator” in Command Prompt. The ipconfig /flushdns and netsh commands fail or error without admin rights. Fix: right-click Command Prompt and choose Run as administrator.
  • Forgetting to click OK when changing DNS. New servers do not apply until you click OK in both the TCP/IPv4 Properties and adapter Properties windows. Fix: click OK on every window, not Close.
  • Testing in the same browser tab. Browsers cache their own DNS and page data. Fix: open a fresh private/incognito window to test.
  • Leaving antivirus disabled after the test. An unprotected PC is a real risk. Fix: re-enable protection the moment the diagnostic is done.

Frequently Asked Questions

What does “DNS server not responding” mean?
It means your PC asked a DNS server to turn a website name into an IP address and got no reply, so the browser cannot load the page. For example, my laptop showed it once while the Wi-Fi icon stayed connected — the connection was fine, only the name lookup had stalled.

Why does this error only affect one device?
When other devices work fine, the problem lives on that one computer — usually a corrupted cache, a wrong DNS setting, or a driver bug. On my own machine, flushing the cache (above) and switching to Google’s DNS cleared it while every phone in the house stayed online.

Is it safe to use Google’s public DNS (8.8.8.8)?
Yes. Google’s 8.8.8.8 / 8.8.4.4 and Cloudflare’s 1.1.1.1 / 1.0.0.1 are free, reliable, and used by hundreds of millions of people. I have run Cloudflare as my default for over a year with zero issues and faster lookups than my ISP’s.

Will resetting TCP/IP delete my files or settings?
No. The TCP/IP and Winsock reset only restores Windows’ internal networking rules to default. When I ran it on a relative’s PC, every file, app, and saved Wi-Fi password stayed exactly as it was.

Can a VPN cause “DNS server not responding”?
Yes. VPNs route DNS through their own servers, and a failing one can trigger this error. I have seen a half-connected VPN cause it — disconnecting the VPN and testing directly fixed it instantly.

What if none of the fixes work?
Then the fault is likely with your ISP, so contact them for remote diagnostics. If your connection is slow rather than dead, my guide on how to fix slow internet covers speed-focused tweaks. When a friend’s error persisted past every step here, the ISP confirmed a regional DNS outage on their end.

Conclusion

The “DNS server not responding” error sounds technical, but it is almost always fixable in minutes. Restart the router, run ipconfig /flushdns, and switch to Google’s 8.8.8.8 — that clears the vast majority of cases. Work through the steps in order and test after each one.

If your Wi-Fi shows connected but nothing loads at all, read my guide on Wi-Fi connected but no internet. If your connection drops over and over, see Wi-Fi that keeps disconnecting next.