ChatGPT Not Working After Update? 12 Fixes (2026)

Quick answer: To fix ChatGPT not working after update, delete ChatGPT/OpenAI site data (cookies + local storage) or clear the app’s storage, then sign in again.

If it still fails, the update likely triggered a conflict (extension, VPN/DNS filter, WebView/Chrome, or blocked WebSockets), so isolate the blocker using the checklist below.

Quick Fix Checklist

• Web (fastest): Delete site data for chatgpt.com (and openai.com) → reload → sign in.
• Web (best test): Try a new browser profile (not just Incognito) to rule out profile corruption and extensions.
• Web (common): Disable ad blockers/privacy/script extensions and any antivirus “web shield”, then reload.
• Network (high impact): Turn off VPN, iCloud Private Relay, AdGuard/NextDNS/Pi-hole, or corporate proxy filtering.
• Android app: Settings → Apps → ChatGPT → Storage → Clear storage (not only cache) → reopen.
• Android (non-obvious): Update/repair Android System WebView + Chrome (mismatches often cause blank screens/login failures after updates).
• iPhone/iPad: Offload or reinstall the app to force a clean asset download.
• API users: Check billing, rate limits, and model/endpoint changes if you see 401/404/429 after updating your client.

Causes (realistic, not generic)

• Stale auth/session tokens: After an update, old cookies/local storage can cause login loops, “Something went wrong”, or repeated CAPTCHA.
• Cached asset mismatch: Your browser/app keeps old JS/CSS bundles while the updated site expects new ones → blank page or infinite spinner.
• Extension/script injection conflict: Ad blockers, privacy hardeners, password managers, translation tools, “reader mode”, and enterprise security extensions can break updated scripts or block required requests.
• Blocked WebSockets / streaming: VPNs, DNS filters, or proxies may block WebSocket/HTTP2 streaming used for chat responses → stuck loading or messages never complete.
• Android WebView regression: ChatGPT app login and embedded web content can break when WebView/Chrome is outdated or corrupted after updates.
• Device time/cert issues: Incorrect date/time or SSL inspection can cause auth failures and 403/handshake errors.
• API client drift: Updating SDKs can change defaults (model names, endpoints, retries) and trigger 401/404/429 if your config is pinned incorrectly.

Cause / symptom	What it looks like	Fix that usually works
Stale cookies/local storage	Login loop, keeps asking to sign in	Delete site data for chatgpt.com + openai.com, then sign in
Cached asset mismatch	Blank/white page, UI missing	Hard refresh + clear site data; then test in a new profile
Extension injection	Buttons don’t work, errors after update	Disable extensions (especially blockers) or use a clean profile
VPN/DNS/proxy filtering	Infinite spinner, messages never finish	Disable VPN/Private Relay/DNS filter; allowlist blocked domains
Android WebView/Chrome mismatch	App crash, blank screen, login fails	Clear app storage; update WebView + Chrome; reinstall WebView updates
API limits/config drift	401/404/429 after updating client	Verify key/project/billing; pin model; add backoff + reduce concurrency

Step-by-Step Fix

1) Web: Delete ChatGPT/OpenAI site data (most reliable fix)

This is stronger than “clear cache” because it removes cookies + local storage that can hold broken sessions after an update.

• Chrome/Edge: Settings → Privacy and security → Site settings → View permissions and data stored across sites (or “All site data”) → search chatgpt and openai → Delete.
• Firefox: Settings → Privacy & Security → Cookies and Site Data → Manage Data → remove chatgpt.com and openai.com.
• Safari (macOS): Safari Settings → Privacy → Manage Website Data → remove openai/chatgpt.

Then fully close the tab, reopen ChatGPT, and sign in again.

2) Web: Hard refresh the page (fixes cached bundle mismatch)

• Windows/Linux: Ctrl + F5 (or Ctrl + Shift + R)
• macOS: Cmd + Shift + R

If the UI is still blank, do Step 1 (site data) and then retry.

3) Web: Test in a new browser profile (best isolation step)

Incognito can still inherit DNS/VPN/proxy issues. A new profile isolates extensions and corrupted profile storage.

• Chrome: Profile icon → Add → Continue without account → open ChatGPT → sign in.
• If it works in the new profile, your main profile has an extension conflict or corrupted storage.

4) Web: Identify the exact extension that broke after the update

• Disable extensions in batches (3–5 at a time) → reload ChatGPT → narrow down.
• Common offenders after updates: uBlock/AdBlock custom rules, Ghostery, NoScript, “cookie auto-delete”, translation overlays, Grammarly-like injectors, antivirus web shields, enterprise DLP extensions.
• Once found, prefer an allow rule for ChatGPT rather than uninstalling everything.

5) Network: Remove VPN/DNS/proxy filtering (fixes stuck loading and streaming)

If ChatGPT works on mobile data but not Wi‑Fi (or vice versa), filtering is the top suspect.

• Temporarily disable: VPN, iCloud Private Relay, AdGuard, NextDNS, Pi-hole, corporate proxy/SSL inspection.
• Check your filter/proxy logs for blocked requests and allowlist what’s blocked (often auth/CDN/streaming endpoints).
• Advanced reset (non-obvious): Flush DNS cache after changing filters:
  • Windows: Command Prompt → ipconfig /flushdns
  • macOS: Terminal → sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
• For testing only, switch DNS to a non-filtering resolver (then revert): 1.1.1.1 or 8.8.8.8.

6) Fix “403”, “Access denied”, or repeated CAPTCHA after the update

• Turn off Private Relay/VPN and any “anti-tracking” network features.
• Ensure device date/time is set to automatic (bad time can break auth).
• Try a different network (mobile hotspot) to rule out IP reputation/proxy issues.
• If you’re on a managed/enterprise network, SSL inspection or policy blocks may trigger bot protection—see the escalation steps below.

7) Android app: Clear storage (not just cache)

• Settings → Apps → ChatGPT → Storage & cache → Clear storage → reopen and sign in.
• If the app crashes immediately, also reboot the phone after clearing storage.

8) Android (advanced): Repair WebView + Chrome

This is one of the most common “it broke right after update” causes on Android.

• Play Store → update Android System WebView and Google Chrome.
• If WebView is stuck or corrupted: Play Store → Android System WebView → Uninstall (removes updates) → update again.
• Optional: Settings → Apps → Android System WebView → Storage → clear cache (avoid clearing storage unless you know what you’re doing).

9) iPhone/iPad app: Offload or reinstall (forces clean assets)

• Settings → General → iPhone Storage → ChatGPT → Offload App → Reinstall App.
• If it still fails: delete the app fully → reinstall from the App Store.
• Test with Private Relay off: Settings → Apple Account → iCloud → Private Relay → Off.

10) Web: If the page loads but chat won’t send (advanced browser fixes)

• Disable “Block third-party cookies” temporarily (some sign-in flows can break depending on browser settings and identity provider).
• Turn off strict tracking protection for the site (Firefox/Safari) and retry.
• Try another browser engine: Chrome/Edge vs Firefox vs Safari. If only one fails, it’s usually a browser setting/extension issue.

11) API users: Fix post-update 401/404/429 fast

• 401 Unauthorized: regenerate the key; confirm your app reads the correct environment variable; verify the key belongs to the expected project/org; check system clock.
• 404 / model not found: pin the model explicitly in config; confirm your SDK version matches the API you’re calling; remove deprecated model names.
• 429 Too Many Requests: reduce concurrency; add exponential backoff with jitter; check usage limits and billing status; log request volume per minute to find spikes introduced by the update.

12) Quick “known-good” test to confirm it’s not your setup

• Try ChatGPT on mobile data (no Wi‑Fi) and in a clean browser profile.
• If it works there, your issue is almost certainly local (extensions, DNS/VPN, proxy, or cached site data).

Still Not Working

• Check for an outage first: If ChatGPT fails on multiple devices and networks, wait—reinstalling repeatedly won’t help during a service incident.
• Capture the real error (web): Open DevTools → Network tab → reload → look for failed requests and codes:
  • 401/403: auth/session or network policy
  • 429: rate limiting
  • 5xx: service-side issue
  • (blocked) or ERR_BLOCKED_BY_CLIENT: extension/DNS filter
• Edge case: multiple accounts/sign-in methods: If Google sign-in loops, try email/password (or Apple) once after clearing site data.
• Edge case: managed/enterprise devices: Security policies may block updated endpoints or WebSockets. Provide IT with:
  • timestamp of failure
  • blocked domain list from proxy/DNS logs
  • error codes from DevTools Network
• Escalation (web): Reset browser settings for the profile (or create a fresh profile), then reinstall the browser only if a clean profile still fails.
• Escalation (mobile): Reinstall the app; on Android, confirm WebView/Chrome are updated; on iOS, test with Private Relay off and reboot after reinstall.
• Contact support with useful evidence: Include device + OS version, browser/app version, network type (Wi‑Fi/cellular), VPN/DNS filter used, and screenshots of the exact error plus request codes from DevTools.

Fixes for iPhone

If this problem happens only on iPhone, the issue is usually tied to the app session, network restrictions, or an iOS-level change rather than a full account failure.

Why this happens

This usually happens when cached app data becomes inconsistent after an update, or when network-related features such as VPN, Private Relay, or filtered DNS interfere with requests.

How to fix it

1. Force close the app completely, then reopen it and test the same action again.
2. Switch from Wi-Fi to mobile data, then test again to rule out router or DNS filtering issues.
3. Disable VPN, iCloud Private Relay, Private DNS, or network security apps temporarily.
4. Update the app from the App Store and restart the iPhone.
5. If the issue continues, delete and reinstall the app to refresh local session data.

Important notes

• If the browser version works but the iPhone app fails, the problem is usually device-side.
• Do not keep repeating the same failed action many times in a row if login or verification is involved.

Fixes for Android

On Android, this kind of issue is often caused by corrupted cache, battery restrictions, or background network controls that affect the app.

Why this happens

Android devices often keep cached app state longer than expected, and some manufacturers add aggressive battery or security settings that interrupt normal app behavior.

How to fix it

1. Force stop the app, then reopen it and test again.
2. Clear the app cache before clearing full storage.
3. Test on Wi-Fi and then on mobile data to isolate network-specific failures.
4. Disable VPN, ad-block DNS, firewall apps, or battery saver temporarily.
5. If needed, clear app storage or reinstall the app to reset broken local data.

Important notes

• If clearing cache helps, that usually confirms the problem was local to the device.
• If the app fails only when battery saver is enabled, background restrictions may be the real cause.

Fixes for Chrome

This section covers a specific troubleshooting angle related to chatgpt not working after update fix. Use it to narrow the issue before moving to deeper fixes.

Why this happens

Problems like this often come from one of three areas: local app state, network conditions, or a recent configuration change.

How to fix it

1. Confirm the exact symptom before changing multiple settings at once.
2. Restart the app and the device before trying advanced fixes.
3. Test on a different network or device if possible.
4. Keep note of any exact error message because it often points to the real cause.

Important notes

• If the basic checks change the behavior, that usually tells you where the issue really lives.
• Move to stronger fixes only after the quick isolation steps above.

If the Problem Started After an Update

If the problem started right after an update, the timing strongly suggests a compatibility or local data issue.

Why this happens

Updates can change permissions, invalidate saved sessions, or leave behind temporary cached data that no longer matches the latest app or system version.

How to fix it

1. Restart the device first to clear temporary glitches triggered by the update.
2. Check whether a follow-up patch is already available for the app or system.
3. Sign out and sign back in if the app still opens but a specific function fails.
4. Clear cache or reinstall the app if the issue appears tied to corrupted local data.
5. Look for reports from other users to confirm whether the update introduced a wider bug.

Important notes

• If many users report the same issue after the same update, a vendor-side patch may be required.
• Do not reset the whole device too early if simpler update-related fixes have not been tested yet.

Frequently Asked Questions