ChatGPT Not Working on Wi‑Fi? 9 Fixes (2026)

Quick answer: Use a clean DNS (1.1.1.1) and disable VPN/proxy/Private Relay—then turn off or allowlist any router/DNS filtering that blocks OpenAI and WebSockets.

If ChatGPT works on mobile data but not Wi‑Fi, your Wi‑Fi path (DNS, firewall, captive portal, or router security) is almost certainly blocking or breaking the connection.

Quick Fix Checklist

• Confirm it’s Wi‑Fi-only: test ChatGPT on mobile data. If it works there, focus on your Wi‑Fi network path.
• Force a clean session: try Incognito/Private mode or a new browser profile (bypasses extensions + some cached auth loops).
• Disable VPN/Proxy/Private Relay: turn off VPN apps, browser proxy settings, iCloud Private Relay, and “secure browsing” network features.
• Switch DNS (fastest high-signal fix): set DNS to 1.1.1.1 / 1.0.0.1 (Cloudflare) or 8.8.8.8 / 8.8.4.4 (Google).
• Check for filtering: Pi-hole/AdGuard Home/NextDNS, router “Parental Controls,” “Safe Browsing,” “Threat protection,” or ISP content filters.
• Trigger captive portal: open http://neverssl.com on Wi‑Fi (hotels/schools/public networks).
• Try another device on the same Wi‑Fi: if all devices fail, it’s router/ISP/policy; if one fails, it’s device-level.

Causes (realistic, not generic)

When ChatGPT fails only on Wi‑Fi, the app is rarely the root cause. It’s usually one of these network behaviors:

• DNS filtering/sinkholing: Pi-hole/NextDNS/AdGuard or ISP DNS blocks OpenAI/CDN domains, causing blank pages, login loops, or “Network error.”
• Router security modules: “Threat protection,” “Web protection,” “Ad blocking,” or parental controls block categories or CDNs used by ChatGPT.
• WebSockets/HTTP2 interference: transparent proxies, SSL inspection, or strict firewalls break the real-time connection used for responses.
• Captive portal / walled garden: Wi‑Fi requires a login/accept page; HTTPS sites may fail until you authenticate.
• IPv6 problems: broken IPv6 routing can make modern apps fail while basic sites still load.
• MTU/MSS fragmentation: PPPoE/DSL or certain WAN links fragment TLS traffic; ChatGPT may stall mid-load or mid-response.
• Device-level profiles: MDM/work profiles, custom root certificates (TLS inspection), or “always-on VPN” policies can block ChatGPT only on certain networks.
• Browser cache layers: corrupted service worker/cache storage can cause infinite loading on one network but not another.

Cause / symptom	What it looks like	Fix (most effective)
DNS filtering	Blank page, endless loading, login loop	Switch DNS to 1.1.1.1; check Pi-hole/NextDNS logs; allowlist blocked entries
Router “threat/web” protection	Works on mobile data, fails on home Wi‑Fi	Disable the module to test; then add allow rules or per-device bypass
WebSockets/HTTP2 blocked	“Network error” mid-response	Disable VPN/proxy/Private Relay; ask IT to allow WebSockets and exempt OpenAI from SSL inspection
Captive portal	Nothing loads until you “sign in”	Open http://neverssl.com and complete the portal login
IPv6/MTU issues	Partially loads, stalls, or fails only on one ISP/router	Disable IPv6 to test; set PPPoE MTU 1492 + enable MSS clamping

Step-by-Step Fix

Work top to bottom. Stop when ChatGPT works on Wi‑Fi.

1) Do the fastest “is it DNS?” test (takes 2 minutes)

If ChatGPT works immediately after this change, your previous DNS (ISP DNS, Pi-hole, NextDNS, router DNS filter) was the blocker.

• Set Wi‑Fi DNS to 1.1.1.1 and 1.0.0.1 (or 8.8.8.8 / 8.8.4.4).
• Reconnect to Wi‑Fi (toggle Wi‑Fi off/on) and reload https://chat.openai.com.

How to set DNS quickly:

• iPhone/iPad: Settings → Wi‑Fi → (i) → Configure DNS → Manual → Add Servers → 1.1.1.1, 1.0.0.1 → Save.
• Android: Settings → Network & Internet → Internet/Wi‑Fi → your network → Advanced → Private DNS: set to dns.cloudflare.com (or turn Private DNS off if it’s set to a filtering provider).
• Windows 11: Settings → Network & internet → Wi‑Fi → Hardware properties → DNS server assignment → Edit → Manual → IPv4: 1.1.1.1 / 1.0.0.1.
• macOS: System Settings → Network → Wi‑Fi → Details → DNS → + → add 1.1.1.1 and 1.0.0.1.

2) If you use Pi-hole / AdGuard Home / NextDNS: allowlist based on logs (not guesses)

Exact domains can change by region/CDN, so the reliable method is to watch what gets blocked while you load ChatGPT.

• Open your DNS filter dashboard → Query Log.
• Load ChatGPT on Wi‑Fi and look for blocked queries around the same timestamp.
• Temporarily disable blocking for 2 minutes. If ChatGPT works instantly, re-enable and allowlist the specific blocked entries shown in the log.

Tip: If you run filtering at the router level, also check whether the router is forcing its own DNS (some “family safety” modes ignore device DNS).

3) Turn off router “security” features that commonly break ChatGPT

Many routers block silently, so test by disabling first, then re-enable with an exception.

• In your router/app, look for: Threat Protection, AiProtection, Web Filter, Parental Controls, Safe Browsing, Ad Blocking, DNS Filter, Content Filter.
• Disable the feature temporarily and retest ChatGPT.
• If it works, create an allow rule or bypass policy for the affected device (preferred over leaving protection off globally).

4) Fix VPN/proxy/WebSocket interference (most common “Network error” cause)

• Windows proxy check: Settings → Network & internet → Proxy → turn off “Use a proxy server” (unless required by your organization).
• Browser extensions: disable extensions that modify traffic (privacy filters, ad blockers with DNS, corporate agents, “VPN in browser” add-ons).
• iOS/macOS: disable iCloud Private Relay (Settings → Apple ID → iCloud → Private Relay).
• Managed networks: if your workplace/school uses SSL inspection, ask IT to exempt OpenAI/ChatGPT traffic from TLS inspection and allow WebSockets + HTTP/2.

5) Clear the specific browser storage that causes ChatGPT loops (non-obvious but effective)

Standard “clear cache” sometimes misses the pieces that break modern web apps. Clear site data for OpenAI and reset the service worker.

• Chrome/Edge: Settings → Privacy and security → See all site data and permissions → search openai → Delete displayed data.
• Chrome/Edge (extra reset): open DevTools (F12) → Application → Service Workers → Unregister (for chat.openai.com) → reload.
• Safari (iOS): Settings → Safari → Advanced → Website Data → search openai → Delete.
• Sign in again and retest on Wi‑Fi.

6) Captive portal fix (hotels, airports, campuses)

• Connect to Wi‑Fi.
• Open http://neverssl.com to force the login/acceptance page.
• Complete the portal sign-in, then reopen ChatGPT.

If the portal never appears: forget the network and reconnect, or temporarily disable “Auto-Join” and rejoin to trigger the prompt.

7) Advanced router/ISP fixes (stalls, partial loads, or only one ISP)

• Disable IPv6 (test): Router settings → IPv6 → Off/Disable → apply → reconnect device. If it fixes it, your IPv6 route is unstable; keep IPv6 off or switch to an ISP-supported IPv6 mode.
• Fix MTU/MSS (PPPoE/DSL edge case): if WAN uses PPPoE, set router MTU to 1492 and enable MSS clamping if available. This prevents TLS fragmentation that can break modern apps.
• Change Wi‑Fi security mode: set to WPA2-Personal (AES) or WPA2/WPA3 mixed. Some WPA3-only implementations cause device-specific handshake issues.
• Resolve DNS-over-HTTPS conflicts: if you changed device DNS but the browser forces DoH to a filtering provider, set browser DoH to Off or Use system DNS and retest.

8) Device-level blockers (profiles, certificates, and “always-on” policies)

If ChatGPT fails only on one device on the same Wi‑Fi, check for system-level settings that override your network.

• iOS/iPadOS: Settings → General → VPN & Device Management → remove unknown VPN/configuration profiles (if you don’t need them).
• Windows: Settings → Accounts → Access work or school → disconnect old/unused management accounts; check installed security agents that proxy traffic.
• Antivirus “HTTPS scanning”: temporarily disable HTTPS/SSL scanning features and retest (they can break WebSockets).

9) Quick isolation test (proves it’s the Wi‑Fi path)

• Connect to the same Wi‑Fi but use a personal hotspot or a trusted VPN briefly.
• If ChatGPT works immediately, your Wi‑Fi network is blocking/rewriting traffic (DNS filter, firewall, proxy, or router module).

Use this only to confirm the cause—then fix the underlying DNS/filter/router rule so you don’t rely on a VPN.

Still Not Working

If you’ve tried DNS + VPN/proxy + captive portal and it still fails, treat this like a network incident and narrow it down with targeted checks.

Deeper troubleshooting (high value checks)

• Check if it’s account/device vs network: try the same ChatGPT account on another device on the same Wi‑Fi, and a different account on the failing device.
• Try both app and web: if the app fails but the website works (or vice versa), the issue may be app cache, OS networking, or a content filter targeting one user agent.
• Restart network stack: reboot modem + router (power off 30 seconds), then restart the device. This clears stale routes and DNS caches on some gateways.
• Flush DNS / reset network:
  • Windows: Command Prompt (Admin) → ipconfig /flushdns then netsh winsock reset → reboot.
  • macOS: reboot (fastest), or flush DNS via Terminal if you’re comfortable.
• Check date/time: incorrect device time can break TLS and look like “site won’t load.” Set time to automatic.
• Look for ISP-level filtering: if multiple routers on the same ISP line show the issue, ask the ISP about content filtering, “safe browsing,” or DNS interception.

Escalation steps (what to send to IT/ISP/support)

• Capture the exact error: “Network error,” blank page, stuck on login, or specific HTTP error.
• Note what fixes it: does switching to 1.1.1.1 help? Does it work on hotspot? Does disabling threat protection help?
• Provide timestamps + network name: helps correlate firewall/DNS logs.
• Ask for specific policy changes: allow OpenAI/ChatGPT traffic, allow WebSockets/HTTP2, and exempt OpenAI endpoints from SSL inspection if used.

Last-resort fixes (when you just need it working)

• Reset network settings: iOS Settings → General → Transfer or Reset → Reset → Reset Network Settings; Windows Settings → Network reset.
• Reinstall the ChatGPT app: if only the app fails on Wi‑Fi after cache resets.
• Use a different network: if you’re on school/work Wi‑Fi and it’s blocked by policy, a personal hotspot may be the only compliant option.
• Check OpenAI status: if it fails on both Wi‑Fi and mobile data, verify https://status.openai.com.

How to Check for a Temporary Outage

Before changing device settings, confirm that the problem is not caused by a temporary outage.

Why this happens

Service interruptions can make normal accounts, apps, and networks appear broken even when nothing is wrong locally.

How to fix it

1. Try the web version to see whether the same action fails outside the app.
2. Check official status pages or recent outage discussions if available.
3. Avoid repeated retries if the platform appears unstable.
4. Wait a few minutes and test again from the same trusted network.

Important notes

• If both the app and browser fail in the same way, the issue is much more likely to be service-side.
• Changing passwords or reinstalling apps will not help during a real outage.

Frequently Asked Questions