ChatGPT Not Working? 9 Fixes in 5 Minutes (2026)

Quick answer: The fastest ChatGPT not working solution is to reset your ChatGPT session (log out, delete site data for chat.openai.com / openai.com , then sign in again) and remove blockers (VPN, DNS filtering, extensions).

What exactly is failing?

• If you cannot sign in, start with account, session, and browser reset steps.
• If the page loads but actions fail, isolate the network, DNS, VPN, or extension layer.
• If only one browser or one device is affected, treat it as a local client problem first.
• If everything fails everywhere, suspect a service incident or account-side restriction.

Common causes

• Corrupted cookies, cache, or local storage.
• A broken browser extension, app state, or outdated client.
• A network, DNS, VPN, or proxy issue.
• A temporary service-side outage or rate limit.

Start with the right diagnosis

1. Check whether the problem affects one browser, one device, or all environments.
2. Test in a private window or a clean browser profile.
3. Try another network such as a mobile hotspot.
4. Confirm whether the issue started after an update, sign-in change, or browser setting change.

Quick answer: The fastest ChatGPT not working solution is to reset your ChatGPT session (log out, delete site data for chat.openai.com/openai.com, then sign in again) and remove blockers (VPN, DNS filtering, extensions).

If it still fails, isolate whether the problem is an OpenAI outage, your browser profile/storage, or your network (WebSockets/SSE, proxy, TLS inspection).

Quick Fix Checklist

• 1-minute outage check: open status.openai.com. If ChatGPT is degraded, stop retrying and wait (retries can trigger 429).
• Hard refresh the page: Windows: Ctrl+F5 / macOS: Cmd+Shift+R.
• Force a clean session (most effective): log out → delete site data (cookies + local storage + cache) for chat.openai.com and openai.com → sign in again.
• Incognito test: open ChatGPT in a Private/Incognito window (quickly rules out extensions + corrupted storage).
• Disable interference for one test: VPN/proxy, ad blockers, privacy/script blockers, “ChatGPT enhancer” extensions, and DNS filtering (NextDNS/AdGuard/Pi-hole).
• Switch network: try a mobile hotspot. If it works there, your Wi‑Fi/router/corporate network is blocking something.
• Verify device time: set time/date to Automatic (fixes login loops and “session expired”).
• Try another browser/profile: a new browser profile beats Incognito when policies or service workers are corrupted.
• Mobile app reset: force close → update app → clear cache (Android) / offload or reinstall (iOS).

Causes (realistic, not generic)

• Corrupted site storage or service worker: causes blank screen, infinite spinner, UI not responding, or “Something went wrong” after login.
• WebSockets/SSE blocked: messages won’t send, responses don’t stream, or it hangs on “Generating…” (common with VPNs, DNS filters, strict firewalls).
• Extension injection: ad blockers, script blockers, password managers, “AI helper” overlays can break the ChatGPT UI or block requests.
• Account/session conflicts: switching between Google/Apple/email sign-in or many active sessions can trigger login loops.
• Browser privacy/cookie rules: strict tracking prevention, blocked cookies, or aggressive “clear on exit” settings can break authentication.
• Corporate proxy/TLS inspection: HTTPS interception can cause 403, repeated redirects, or failed handshakes.
• Rate limits (429): rapid retries, multiple tabs, or heavy usage can temporarily block requests.
• Browser/OS issues: outdated browser, broken GPU acceleration, or captive portals can cause blank pages or stuck loading.

Cause / Symptom	Fix that works
Blank page, endless loading, UI glitches (storage/service worker)	Delete site data for chat.openai.com/openai.com; then remove service worker + cache (see Step 2)
Messages won’t send or won’t stream (WebSockets/SSE blocked)	Disable VPN/DNS filtering; test on hotspot; allowlist OpenAI domains; avoid TLS inspection
Login loop / “Session expired” (token/time/session conflict)	Set time to automatic; log out everywhere; delete site data; use one sign-in method
403 / Access denied (proxy, geo, TLS inspection, policy)	Try a clean network/device; disable HTTPS inspection; remove corporate proxy; check browser policies
429 Too Many Requests (rate limit)	Stop retries; wait 10–30 minutes; close extra tabs; reduce parallel usage; use backoff for API

Step-by-Step Fix

1) Confirm it’s not an OpenAI incident

• Check status.openai.com for ChatGPT incidents.
• If there’s an incident: wait and avoid repeated refreshes/sign-in attempts (can worsen rate limiting).
• If status is green: continue.

2) Do a true “site data” reset (cookies + storage + service worker)

This is the most reliable ChatGPT not working solution for blank screens, stuck loading, and post-login errors.

• Chrome/Edge: Settings → Privacy and security → Cookies and other site data → See all site data and permissions → search openai → delete entries for chat.openai.com and openai.com.
• Firefox: Settings → Privacy & Security → Cookies and Site Data → Manage Data → remove openai.com (and any chat.openai.com entries).
• Safari (macOS): Settings/Preferences → Privacy → Manage Website Data → search openai → Remove.

Advanced (non-obvious) fix: remove the service worker cache if the UI still loads wrong after clearing cookies.

• Chrome/Edge: open DevTools → Application → Service Workers → Unregister (for chat.openai.com), then Application → Clear storage → Clear site data.
• Reload https://chat.openai.com/ and sign in again.

3) Eliminate extension conflicts (fast isolation)

• Open ChatGPT in an Incognito/Private window.
• If it works there, disable extensions in normal mode—start with:
• Ad blockers (uBlock, AdBlock, Brave Shields)
• Script/privacy blockers (NoScript, Ghostery)
• Password managers with autofill overlays
• “ChatGPT enhancer”, “prompt manager”, or “AI sidebar” extensions
• Re-enable one-by-one to identify the exact extension causing the break.

4) Fix VPN, DNS filtering, and WebSocket/SSE blocking

If ChatGPT loads but won’t send messages or won’t stream responses, treat it as a network transport problem.

• Disable VPN/proxy and retry.
• If you use NextDNS/AdGuard/Pi-hole, temporarily disable filtering or allowlist:
• chat.openai.com
• openai.com
• auth.openai.com (commonly used for sign-in)
• Hotspot test: connect to a mobile hotspot and try again. If it works, your router/firewall/DNS filter is the cause.
• Work/school networks: ask IT to allow WebSockets/SSE to OpenAI and to avoid TLS inspection for ChatGPT traffic if policy permits.

5) Fix login loops, “session expired”, and repeated redirects

• Use one sign-in method only: Google or Apple or email/password. Switching methods often creates conflicting sessions.
• Set time/date to automatic (Windows/macOS/iOS/Android). Incorrect time breaks token validation.
• Log out everywhere (if you can), then sign in again after clearing site data.
• Safari/iOS note: if you use Safari with strict privacy settings, try Chrome/Firefox as a test to confirm it’s a cookie/privacy rule issue.

6) Fix 403, “Access denied”, and blocked pages

• Try a clean environment: personal device + home network (or hotspot) + no VPN.
• Remove corporate proxy settings: system proxy or PAC files can force traffic through a filter that blocks ChatGPT.
• Check browser policies (managed devices): work/school policies can block scripts, cookies, or WebSockets. A new browser profile may still inherit policies—test on an unmanaged device to confirm.

7) Resolve 429 / rate limit issues (web and API)

• Web (ChatGPT): stop rapid refreshes and repeated retries; close extra ChatGPT tabs; wait 10–30 minutes.
• API (developers): check your OpenAI dashboard usage/limits, implement exponential backoff + jitter, and reduce parallel bursts across workers.

8) Browser/OS fixes that solve “stuck loading” (edge cases)

• Update your browser (old versions can break modern JS features and auth flows).
• Disable hardware acceleration (rare, but can fix blank/white screens): Chrome/Edge → Settings → System → turn off “Use hardware acceleration”. Restart browser.
• Captive portal check: on public Wi‑Fi, open any non-HTTPS site to trigger the login page, then retry ChatGPT.

9) Mobile app fixes (iPhone/Android)

• Update the app first (App Store/Google Play), then force close and reopen.
• Android: Settings → Apps → ChatGPT → Storage → Clear cache. If still broken, Clear storage (you’ll sign in again).
• iPhone: Settings → General → iPhone Storage → ChatGPT → Offload App → reinstall. If still broken, delete and reinstall.
• If it works on cellular but not Wi‑Fi, fix the network (DNS filter/firewall), not the app.

Still Not Working

• Run a clean isolation test (fastest way to pinpoint the layer):
  • New browser profile (not Incognito)
  • No extensions
  • No VPN/proxy
  • Mobile hotspot

  If this works, the issue is your normal browser profile or network policy.

• Check what’s actually failing (real tech support step):
  • Open DevTools → Network → reload ChatGPT.
  • Look for red/failed requests and note the status codes (403/429/5xx) and blocked domains.
  • If you see “blocked by client”, it’s usually an extension or content blocker.
• Reset only OpenAI-related browser data (avoid nuking everything): delete site data for openai.com/chat.openai.com, then restart the browser completely (quit, not just close the tab).
• Work/school device edge cases:
  • MDM/browser policies can block cookies, scripts, or WebSockets even in a new profile.
  • Security tools doing TLS inspection can break auth or streaming—test on an unmanaged device to confirm.
• Escalate with useful proof (saves days):
  • Record: exact error text, time, browser/app version, network type (home/corp/VPN), and whether hotspot works.
  • For IT: provide the symptom (login loop vs can’t send vs no streaming) and the domains you need allowlisted (chat.openai.com, openai.com, auth.openai.com).
• If you suspect an account issue: try signing in on a different device/network. If only one account fails everywhere, use the in-app Help/Support option (when available) and include the captured error/time.

If you want the fastest path to a working session, use this order: status check → delete site data + service worker reset → Incognito test → disable VPN/DNS filtering → hotspot test.

Advanced fixes

1. Reset site data or app state, then sign in again.
2. Disable extensions, VPN, proxy, DNS filtering, or security interception temporarily for one clean test.
3. Use a new browser profile or reinstall the affected app if the problem is isolated to one environment.
4. If the issue persists across devices and networks, escalate with exact error details and timing.

Frequently Asked Questions