ChatGPT Not Sending OTP? Fix It in 5 Minutes

Quick answer: If ChatGPT OTP is not received on PC after an update, first clear site data for chatgpt.com/openai.com and unregister the service worker, then request a new code once.

If it still fails, quickly determine whether the problem is account/session, browser state, network/transport, or a service-side outage and follow the matching fix path below.

Quick Fix Checklist

Do these in order and stop as soon as OTP works.

• Note the exact symptom (don’t guess):
  • Does clicking Send code do nothing?
  • Do you see an error (403/429/“Something went wrong”)?
  • Is the code “sent” but never arrives?
  • Do you get stuck in a login loop after entering the code?
• Try Incognito/Private and request OTP once (fastest way to isolate extensions/storage).
• Try another browser (Edge/Chrome/Firefox) on the same PC.
• Try another network (mobile hotspot) on the same PC to isolate network filtering.
• Check OpenAI status if it fails on multiple devices/networks (auth/OTP can be degraded).
• Avoid rapid retries: request a code once, wait a few minutes, then retry to reduce throttling/rate limits.

Quick problem classifier (pick the closest match):

• A) “Send code” does nothing or the page spins forever → usually browser/app state or extension blocking.
• B) Code is “sent” but never arrives → could be delivery/throttling, account path mismatch, or service-side.
• C) Works in Incognito but not normal mode → almost always extensions, managed policies, or corrupted site storage.
• D) Works on phone but not PC → usually PC browser state or PC network policy.
• E) Works on hotspot but not home/office Wi‑Fi → network/transport filtering (DNS/proxy/firewall/TLS inspection).
• F) Fails on multiple devices → check OpenAI status and reduce retries.

Symptom you see	Most likely cause	Best first fix
Works in Incognito but not normal mode	Extension conflict, managed policy, or corrupted site storage	Disable extensions + clear OpenAI site data (domains only)
Works on phone but not PC	PC browser state or PC network policy	Unregister service worker + test hotspot
Works on hotspot but not home/office Wi‑Fi	DNS/proxy/firewall/TLS inspection blocking auth	DevTools Network errors + bypass proxy/VPN
“Send code” does nothing / request fails	Cached assets mismatch after update or blocked scripts	Hard reload + clear cache/storage for OpenAI domains only
Login loop after entering OTP	Cookies blocked, third-party cookie restrictions, or stale session	Allow cookies for chatgpt.com/openai.com + clear site data
Fails on multiple devices/networks	Service-side outage/degraded feature or account throttling	Check OpenAI status + wait + retry once with fresh session

Causes (realistic, not generic)

• Cached assets mismatching the new app or site version: after an update, old JS/CSS can remain while the backend expects a newer flow, causing OTP requests to fail or UI buttons to stop working.
• Service worker stuck on an old app shell: a stale service worker can keep serving outdated files even after a normal refresh.
• Browser compatibility regression: changes to cookie handling, storage access, tracking prevention, or security policies can break sign-in/OTP flows.
• Settings reset or permission changes after update: cookies blocked, “clear cookies on exit,” stricter tracking protection, wrong system time, or new security software rules.
• Plugin/extension conflict exposed by the update: ad blockers, privacy tools, script blockers, antivirus web shields, password managers, coupon injectors, or corporate security extensions can block auth endpoints.
• Network/transport filtering: DNS filtering, proxy/VPN, firewall rules, or TLS inspection can block or rewrite requests even when normal browsing works.
• Service-side outage or degraded feature: OTP/auth services can be temporarily degraded; this typically affects multiple devices or many users at once.

Step-by-Step Fix

Follow the branch that matches your scenario. Each step states what symptom it targets.

1) If you cannot sign in (prioritize session + cookie fixes)

• Hard refresh the login page (fixes cached asset mismatch):
  • Windows: press Ctrl+F5 on the ChatGPT login page.
• Clear site data only for OpenAI domains (fixes broken session/cookies without wiping your whole browser):
  • Chrome/Edge: Settings → Privacy and security → Site data (or Cookies and site data) → See all site data and permissions.
  • Remove entries for: chatgpt.com, openai.com, and auth.openai.com (if present).
  • Reload and request OTP again.
• Allow cookies for sign-in pages (fixes OTP loops and “back to login” behavior):
  • Temporarily disable strict tracking prevention for the login attempt, or add site exceptions to allow cookies for chatgpt.com and openai.com.
  • If your browser blocks third-party cookies, try allowing them just for the login flow, then revert after you’re signed in.
• Verify system time/date (uncommon but real; fixes session/OTP validation issues):
  • Windows: Settings → Time & language → Date & time → enable Set time automatically, then retry.

2) If it works in Incognito/Private but not normal mode (extensions/policies)

• Disable extensions that can block or inject scripts (fixes “Send code” doing nothing or requests being blocked):
  • Turn off ad blockers/privacy blockers, script blockers, antivirus web shields, coupon/shopping injectors, and “enhanced tracking” extensions.
  • Retry OTP after disabling, then re-enable one-by-one to find the conflict.
• Test on a clean browser profile (advanced; rules out managed policies and hidden extension injection):
  • Chrome/Edge: create a new profile (no sync), do not install extensions, then try signing in.
  • If the clean profile works, your main profile likely has a policy/extension/storage issue rather than an account problem.
• Check for managed browser policies (advanced; common on work/school PCs):
  • Chrome: open chrome://policy and look for policies affecting cookies, extensions, or proxies.
  • Edge: open edge://policy.
  • If policies enforce a security extension or proxy, you may need IT to allowlist OpenAI/ChatGPT auth traffic.

3) High-impact fix after updates: unregister the service worker + clear storage (OpenAI domains only)

This targets the common “started after update” case where a stale service worker or cached app shell breaks OTP requests.

• Chrome/Edge DevTools method:
  • Open the ChatGPT login page (on chatgpt.com).
  • Press F12 → Application tab.
  • Open Service Workers → click Unregister for entries related to ChatGPT/OpenAI.
  • Open Storage → click Clear site data (confirm you are clearing data for the OpenAI/ChatGPT origin, not all sites).
  • Close all ChatGPT/OpenAI tabs, reopen, and request OTP again.
• Alternative (no DevTools):
  • Clear site data for chatgpt.com and openai.com from browser settings, then restart the browser.

4) If the page loads but actions fail (prioritize transport, extensions, blocked requests)

• Inspect failed network requests in DevTools (advanced; separates storage issues from transport blocking):
  • Open DevTools → Network tab → enable Preserve log.
  • Click Send code again.
  • Look for requests that are blocked, canceled, 401/403, 429, or failed (DNS/TLS/CORS).
  • Common interpretations:
    • Blocked by client → extension conflict (disable/allowlist).
    • ERR_NAME_NOT_RESOLVED → DNS issue/filtering.
    • NET::ERR_CERT_* or TLS handshake failures → TLS inspection/security product/proxy.
    • 403 → blocked by policy, security layer, or suspicious traffic detection (often network/security tooling).
    • 429 → rate limit/throttling; wait and retry once.
• Disable VPN/proxy/TLS inspection temporarily (fixes OTP requests failing only on certain networks):
  • Windows: Settings → Network & Internet → Proxy → turn off manual proxy (if enabled).
  • Temporarily disable VPN and retry.
  • If you’re on a work network, ask IT whether OpenAI/ChatGPT auth endpoints are filtered or inspected.

5) If it works on one network but not another (network/transport issue)

• Confirm with a controlled test (avoids guessing):
  • Try the same PC + same browser on a mobile hotspot.
  • If hotspot works, your primary network is blocking or rewriting traffic.
• Switch DNS on the affected network (targets DNS filtering that blocks auth/OTP endpoints):
  • Set DNS to a reputable public resolver (for example, Cloudflare or Google) on the router or PC, then retry.
  • If this fixes it, your previous DNS provider likely filtered or misrouted OpenAI domains.
• Try a different network path (quick workaround):
  • Use hotspot for the sign-in step, then switch back to your normal network after you’re logged in (if allowed by your environment).

6) If the code is “sent” but not received (delivery/throttling/account path)

• Wait before retrying (targets throttling):
  • Request a code once, wait 3–10 minutes, then request again.
• Confirm you’re using the same sign-in method as before (targets account path mismatch):
  • If your account was created with Continue with Google/Microsoft/Apple, use that same provider.
  • Switching methods can make it look like OTP “isn’t arriving” when you’re actually attempting a different account path.
• Try another device for the OTP step (isolates PC-only issues):
  • If it works on your phone but not PC, return to the PC-focused fixes (service worker/site data/extensions).

7) If it fails on multiple devices (check service-side outage earlier)

• Check OpenAI status (targets service-side outage or degraded feature):
  • If auth/OTP is degraded, repeated retries can trigger rate limits; wait for recovery and try again with a fresh session.
• Retry with a fresh session (targets stuck sessions):
  • Close all ChatGPT/OpenAI tabs, reopen an Incognito window, and try again once.

Still Not Working

If the quick fixes didn’t work, use this section to avoid repeating the same steps and to gather the right evidence for escalation.

Deeper troubleshooting (what to check next)

• Confirm whether the OTP request is actually being sent:
  • In DevTools → Network, click Send code and confirm a request is made.
  • If no request appears, it’s usually UI/script blocking (extensions, stale cache, service worker) rather than delivery.
• Clear only OpenAI/ChatGPT storage again, then restart the browser:
  • Some browsers keep processes alive; a full restart can be the difference after clearing site data.
• Try a different browser engine:
  • If you’re on Chrome/Edge (Chromium), test Firefox; if you’re on Firefox, test Edge.
  • This helps identify a browser-specific regression after an update.
• Check security software web protection (edge case, but common):
  • Temporarily disable “HTTPS scanning,” “web shield,” or similar features and retry.
  • If it fixes the issue, add an allowlist exception for ChatGPT/OpenAI domains instead of leaving protection off.
• Check for captive portals or restricted networks:
  • Hotel/guest Wi‑Fi may allow browsing but block auth flows; confirm by testing hotspot.

Evidence to capture (so support/IT can act)

• Scenario matrix:
  • Works in Incognito? (Yes/No)
  • Works in another browser? (Yes/No)
  • Works on hotspot? (Yes/No)
  • Works on another device? (Yes/No)
• Exact symptom text (copy the error message if any).
• DevTools Network details:
  • Any request marked blocked by client, ERR_NAME_NOT_RESOLVED, ERR_CERT, 403, or 429.
  • Time of the attempt and your network type (home/work/VPN/hotspot).

Escalation and last-resort steps

• If this is a managed PC (work/school):
  • Share your hotspot test result and DevTools error with IT.
  • Ask whether a proxy, TLS inspection, DNS filtering, or enforced extension is blocking OpenAI/ChatGPT authentication.
• If it’s a browser-profile corruption issue:
  • Move to a new browser profile (or reinstall the browser) and sign in there.
  • Only after confirming it works, re-enable sync/extensions gradually.
• If you suspect a service-side issue:
  • Check OpenAI status, wait for recovery, then retry once from an Incognito window after clearing OpenAI site data.

Decision rule: If the issue is limited to one PC, prioritize local cache, app state, permissions, and extensions. If it affects multiple devices, check service status and network policy earlier.

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 otp not received on pc after update. 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.

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