ChatGPT Not Working on iPhone? 11 Fixes (2026)

Quick answer: To fix ChatGPT not working on iPhone, turn off VPN and iCloud Private Relay, disable Safari content blockers for chat.openai.com, then clear OpenAI site data (or update/reinstall the app) and sign in again.

If it works on cellular but not Wi‑Fi (or vice versa), the problem is almost always DNS filtering, a captive portal, or a router/work profile blocking OpenAI.

Quick Fix Checklist

• Toggle Airplane Mode on for 10 seconds, then off (forces a clean network route).
• Turn off VPN (including 1.1.1.1/WARP) for 2 minutes and retry.
• Turn off iCloud Private Relay temporarily (common cause of login loops and blank screens).
• Switch networks: Wi‑Fi ⇄ cellular. If only one works, jump to Step 5 (DNS/Wi‑Fi filtering).
• Safari users: turn off content blockers for chat.openai.com and delete OpenAI website data.
• App users: update ChatGPT, then log out/in (refreshes the session token).
• Check OpenAI status if it fails on every device/network (service outage).

Causes (realistic, not generic)

• VPN / DNS filtering / ad blocking: NextDNS, AdGuard, Pi‑hole, router “security”, or corporate DNS blocks OpenAI/CDN endpoints used for login and streaming responses.
• iCloud Private Relay routing: can break authentication, Cloudflare checks, or websocket/streaming connections on certain networks.
• Safari content blockers / extensions: blocks scripts, cookies, local storage, or challenge pages needed for ChatGPT to load.
• Corrupted site data or stale tokens: causes login loops, “Unauthorized”, stuck spinner, or messages that never send.
• Captive portal / restricted Wi‑Fi: hotel/airport/office Wi‑Fi may allow basic browsing but block websockets/HTTP2 streaming.
• iOS restrictions: Screen Time web limits, managed device (MDM) profiles, or “Limit IP Address Tracking” interactions.
• App build mismatch or bad local cache: older builds or corrupted app storage after an update can prevent loading or sending.

Cause / symptom	What it looks like	Fix that usually works
Content blocker / Safari extension	Blank page, buttons don’t work, stuck spinner	Turn off content blockers for chat.openai.com; delete OpenAI website data
Private Relay or VPN interference	Login loop, Cloudflare check stuck, “Network error”	Disable Private Relay + VPN; retry; re-enable one at a time
DNS filtering / router blocking	Works on cellular but not Wi‑Fi	Set DNS to Automatic; remove DNS profiles; allowlist OpenAI in filter logs
Captive portal / restricted Wi‑Fi	Loads partially, replies never stream, errors on send	Trigger portal login; switch networks; try cellular hotspot
Stale session token / corrupted app data	App opens but won’t send, “Unauthorized”	Log out/in; update; reinstall if needed

Step-by-Step Fix

1) Confirm whether the issue is the app or Safari (30 seconds)

• If the ChatGPT app fails, test Safari: https://chat.openai.com.
• If Safari fails, test the ChatGPT app.

If one works and the other doesn’t, skip directly to the matching steps below (Safari vs app). This avoids random “try everything” troubleshooting.

2) Hard refresh your network route (fast, low-risk)

• Toggle Airplane Mode on for 10 seconds, then off.
• Restart iPhone if the issue started after switching networks or waking from sleep.

This clears a surprising number of “stuck loading” cases caused by a bad route, DNS cache, or captive portal state.

3) Disable VPN and iCloud Private Relay (most common real-world fix)

• VPN: Settings > VPN (or your VPN app) > toggle Off.
• iCloud Private Relay: Settings > [your name] > iCloud > Private Relay > toggle Off.

Retry immediately. If it works, re-enable one feature at a time to identify the exact blocker.

4) Safari fix (WebKit): disable content blockers + clear only OpenAI data

Use this for blank screens, login loops, stuck Cloudflare checks, or taps that do nothing.

• Turn off content blockers for the site: Safari > open chat.openai.com > tap aA > Turn Off Content Blockers.
• Disable extensions temporarily: Settings > Safari > Extensions > disable ad blockers/content blockers.
• Delete OpenAI website data (targeted): Settings > Safari > Advanced > Website Data > search openai > Delete.

Then reload chat.openai.com and sign in again. This keeps other sites logged in while fixing corrupted OpenAI cookies/storage.

5) Fix “works on cellular but not Wi‑Fi” (DNS filtering / router security)

If ChatGPT works on cellular but not your Wi‑Fi, your Wi‑Fi path is blocking it.

• Set DNS to Automatic: Settings > Wi‑Fi > tap i > Configure DNS > Automatic.
• Remove DNS profiles: Settings > General > VPN & Device Management > remove DNS/ad-block profiles you don’t need.
• Check router filtering: if you use Pi‑hole/NextDNS/AdGuard Home, open its logs and allowlist the domains it shows as blocked for ChatGPT (start with chat.openai.com and any OpenAI/CDN entries in the logs).
• Try a different Wi‑Fi or a phone hotspot to confirm it’s the router/network, not the iPhone.

6) Fix captive portal / restricted Wi‑Fi (hotel, airport, office)

• Open Safari and visit http://neverssl.com to force the Wi‑Fi login page (captive portal) to appear.
• If you’re already logged in but ChatGPT still fails, the network may block streaming/websockets. Switch to cellular or a different Wi‑Fi.

7) ChatGPT app fix: update, refresh session, and check data access

• Update: App Store > ChatGPT > Update (if available).
• Refresh session: ChatGPT > Settings/Profile > Log out > fully close the app > reopen > log in.
• Allow data: Settings > ChatGPT > enable Cellular Data (if you use cellular).
• Low Data Mode check: Settings > Cellular (or Wi‑Fi > i) > ensure Low Data Mode isn’t causing issues; toggle it off to test.

8) Non-obvious iOS fix: disable “Limit IP Address Tracking” for the failing network

On some networks, Apple’s privacy routing can behave like a filter and break authentication/streaming.

• Wi‑Fi: Settings > Wi‑Fi > tap i > toggle Limit IP Address Tracking off (test).
• Cellular: Settings > Cellular > Cellular Data Options > toggle Limit IP Address Tracking off (test).

If this fixes it, you can re-enable later and keep Private Relay/VPN off only when using ChatGPT.

9) Advanced fix: reset network settings (clears hidden VPN/DNS remnants)

Use this when ChatGPT fails in both Safari and the app on the same iPhone, especially after installing VPN/DNS tools.

• Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings.

You’ll need to re-join Wi‑Fi networks afterward.

10) Advanced fix: reinstall the ChatGPT app (clears corrupted local cache)

• Delete the app: press and hold ChatGPT > Remove App > Delete App.
• Restart iPhone.
• Reinstall from the App Store and sign in again.

This is the fastest way to clear a broken app state after an iOS/app update.

11) Check Screen Time / managed device restrictions (common on family/work phones)

• Screen Time: Settings > Screen Time > Content & Privacy Restrictions > check Web Content and account sign-in restrictions.
• Managed iPhone (MDM): Settings > General > VPN & Device Management. If a management profile exists, your admin may block OpenAI domains or VPN/relay behavior.

Still Not Working

• Do a 60-second isolation test:
  • Try cellular with VPN/Private Relay off.
  • Try a different Wi‑Fi (friend’s network) with the same settings.
  • If it only fails on one network, it’s upstream filtering (router, DNS, firewall, captive portal).
• Check for an OpenAI outage: if ChatGPT fails on multiple devices and networks, wait and retry later.
• Try a clean browser environment: install Chrome and test chat.openai.com. If Chrome works but Safari doesn’t, it’s almost always Safari website data or extensions/content blockers.
• Look for blocked domains in your filter logs: if you use NextDNS/AdGuard/Pi‑hole, search logs while loading ChatGPT and allowlist what’s blocked (this is faster than guessing).
• Escalate with useful details (saves time): iOS version, ChatGPT app version, whether VPN/Private Relay is on, whether it fails on Wi‑Fi vs cellular, and the exact error text/screenshot.
• Last resort (device-level): update iOS (Settings > General > Software Update). If you’re far behind, WebKit/network fixes in newer iOS builds can resolve persistent Safari/app issues.

If you tell us the symptom (blank screen, login loop, network error, won’t send) and whether it works on cellular vs Wi‑Fi, you can usually pinpoint the cause in one step.

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.

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