AI AI Tools Guidebook
Troubleshooting

ChatGPT Login Fails: Email, Google SSO, OTP, and Suspicious Activity

ChatGPT login failures fall into four buckets: email-password bounce, Google/Microsoft SSO error, the new 6-digit OTP code never arriving, and a suspicious-activity lock. Find your bucket, get the shortest fix.

Published: Updated: Author: AI Productivity Guide Team 🌐 查看中文版本

ChatGPT login errors come in many shapes, but classify them and almost all fall into four buckets: email-password bounce -> SSO redirect error -> the 6-digit OTP code that never arrives -> suspicious-activity lock. Same “can’t log in,” very different root causes. Identify your bucket first, then jump to the matching fix. Trying random fixes (especially retrying over and over) usually makes a suspicious-activity lock worse.

Fastest fix for most people: open chatgpt.com in an incognito/private window with all extensions off, on your phone’s mobile data instead of office Wi-Fi or a VPN. If that logs you in, the problem is a browser extension, a blocked cookie, or a flagged IP — not your account.

One domain note up front: ChatGPT moved from chat.openai.com to chatgpt.com in May 2024, and the actual sign-in form now lives on auth.openai.com. Old chat.openai.com links still redirect, but if a fix below mentions allowing cookies, you must allow them for chatgpt.com, auth.openai.com, and (for Google SSO) accounts.google.com — not just openai.com.

Note: this article assumes the account exists, your email works, and you simply can’t sign in. If the account is explicitly suspended (a banner says so) or deactivated, use the OpenAI Help appeal flow instead — none of the fixes here will apply.

Symptoms

  • Submit email + password and bounce back to the login page (no error, but no entry)
  • Explicit Incorrect email or password
  • Google / Microsoft / Apple SSO returns Oops, something went wrong or Something went wrong while getting your SSO info
  • You reach the “Enter the code we emailed you” screen but the 6-digit code never arrives
  • A We detected suspicious activity from your account banner appears
  • Sign in succeeds, then you’re immediately bounced back to login in a loop
  • The Google sign-in popup hangs on a white screen

The four categories

Category A: Email + password bounce

Three common root causes.

A1. Email never verified at signup

OpenAI’s “Verify your email” message at signup must be clicked. If you missed it, the account stays inactive — login may bounce silently or say Email not verified. Verification emails sometimes land in spam.

How to confirm: search your inbox for OpenAI senders. Legitimate verification and code emails come from noreply@tm.openai.com or otp@tm1.openai.com (as of June 2026). No such email anywhere = never verified.

Fix: on the login page, choose “Resend verification” for the same email. If still nothing:

  • Check the spam/junk folder
  • Add @tm.openai.com and @openai.com to your safe-senders / allowlist
  • Use a mainstream provider (Gmail / Outlook deliver more reliably than some regional or corporate-filtered mailboxes)

A2. Wrong password (including “I’m sure it was right”)

ChatGPT often doesn’t explicitly say “wrong password” — it just bounces you back.

Fix: go straight to the login page at chatgpt.com, click “Forgot password?”, and run the reset. Receiving the reset email means the account is fine; follow the link to set a new password.

Important: if you originally signed up with Google, Microsoft, or Apple SSO, the account has no OpenAI password, and the reset flow will not help — go to Category B instead.

A3. Multi-device concurrent sign-in tripped a lock

Signed in on several devices with IPs jumping country to country can trip a temporary lock (typically clears in 24 hours).

Fix: pick one stable network and stay on it. Don’t keep retrying from new IPs.

Category B: Google / Microsoft / Apple SSO redirect failure

After entering credentials on Google, the redirect back to ChatGPT fails with Oops, something went wrong, Something went wrong while getting your SSO info, or hangs on a white screen.

B1. Third-party cookies blocked

The OAuth callback writes a session cookie cross-origin between accounts.google.com, auth.openai.com, and chatgpt.com. Safari’s tracking prevention, Brave Shields, Firefox strict mode, and aggressive Chrome settings can all block it.

How to confirm: open DevTools (F12) -> Application -> Cookies. After the OAuth redirect, does chatgpt.com have a session cookie? Missing = it was blocked.

Fix — allow cookies for all three domains:

  • Chrome / Edge: Settings -> Privacy and security -> Third-party cookies -> “Allowed to use third-party cookies”, add [*.]openai.com and [*.]google.com
  • Safari: Settings -> Privacy -> uncheck “Prevent cross-site tracking”
  • Firefox: Enhanced Tracking Protection -> Custom -> uncheck “Cookies”, or set the site to Standard

B2. Privacy / ad-blocker extension breaks the OAuth callback

uBlock Origin, Privacy Badger, and Ghostery sometimes block OAuth redirect URLs.

Fix: whitelist accounts.google.com, auth.openai.com, and chatgpt.com in the extension; or sign in via an incognito/private window (extensions are disabled there by default).

B3. Chrome QUIC protocol breaks the SSO handshake

A known cause of the white-screen / Oops, something went wrong hang specifically in Chrome is the experimental QUIC transport.

Fix: paste chrome://flags/#enable-quic into the address bar, set “Experimental QUIC protocol” to Disabled, restart Chrome, and retry SSO.

B4. Same email registered as both SSO and email/password

ChatGPT occasionally bounces a Google SSO redirect because the email already exists as a password account, without saying so clearly.

Fix: sign in with email/password instead (use “Forgot password?” to set one). If you genuinely only ever used SSO, the account has no password — keep using the SSO button and fix the cookie/extension issue above.

Category C: OTP login code never arrives

Since 2025, OpenAI frequently asks for an extra step: it emails a 6-digit one-time code and shows “Enter the code we emailed you.” If that email never lands, you’re stuck on this screen even with the correct password.

How to confirm: the screen explicitly asks for a code, not a password. The code email comes from otp@tm1.openai.com (or noreply@tm.openai.com).

Fix:

  1. Check the spam/junk and “Promotions” folders; codes are time-limited, so request a fresh one if more than a few minutes have passed
  2. Click “Resend code” once, then wait — don’t spam it (rapid resends can rate-limit you)
  3. Allowlist @tm1.openai.com and @tm.openai.com
  4. If your mailbox is a corporate or regional account that filters aggressively, the code may be silently dropped — sign in with a Gmail/Outlook-based account instead, or ask your IT admin to allowlist those senders

Category D: Suspicious activity lock

Common triggers:

  • Rapid IP / VPN switching (country hops)
  • Free / shared VPN
  • Tor exit nodes
  • Was working, then suddenly stopped one day

Detailed handling: ChatGPT suspicious activity. Short version:

  1. Switch to a clean IP (phone mobile data is usually the cleanest)
  2. Wait 30 minutes — do not keep retrying
  3. Sign in once
  4. Use normally for 24 hours without changing network

Shortest path to fix

Step 1: Identify the bucket

What you seeCategory
Bounce to login / Incorrect email or passwordA (email-password)
No verification email at allA1
You only ever used the Google/Apple/Microsoft buttonB (SSO)
SSO redirect returns to an error or white screenB (SSO)
Screen asks for a 6-digit code that never arrivesC (OTP)
We detected suspicious activity bannerD (lock)
Sign in, then immediately signed out in a loopA3, D, or corrupt cookies (Step 5)

Step 2 (Category A): Email-password path

  1. On chatgpt.com, click “Forgot password?” and run the reset
  2. Reset email received = account is fine; follow the email to set a new password
  3. Reset email not received = check spam, wait 5 minutes, resend once
  4. After resetting, sign in from a stable network — don’t hop IPs mid-first-login
  5. If you signed up with SSO, skip this — there is no password to reset (go to Step 3)

Step 3 (Category B): SSO path

  1. Try the SSO flow in an incognito/private window (extensions off). Works = it was extensions or cookies — re-allow them in your normal browser
  2. In Chrome, disable QUIC: chrome://flags/#enable-quic -> Disabled -> restart
  3. Allow third-party cookies for [*.]openai.com and [*.]google.com (Chrome: Settings -> Privacy and security -> Third-party cookies)
  4. Retry SSO. If it still fails on every browser and device, the account itself may need OpenAI Help (Step 7)

Step 4 (Category C): OTP path

  1. Confirm the screen is asking for a 6-digit code, not a password
  2. “Resend code” once, then wait; check spam and “Promotions”
  3. Allowlist otp@tm1.openai.com and noreply@tm.openai.com
  4. Still nothing after two tries from a normal Gmail/Outlook inbox = open a ticket (Step 7); from a corporate/regional inbox = the filter is likely dropping it, so try a different mailbox

Step 5 (Category D): Lock path

  1. Stop retrying immediately — every failure deepens the lock
  2. Switch to a clean IP (phone mobile data), wait 30 minutes
  3. Sign in once from the clean IP
  4. Don’t switch nodes or log into more devices for 24 hours
  5. See the suspicious activity article for detail

Step 6: Clear browser state

If you’ve tried the above and still get a login / logout loop (corrupt cookies are the single most common browser-side cause):

  1. DevTools -> Application -> Storage -> “Clear site data” (wipes chatgpt.com and auth.openai.com cookies)
  2. Or in Chrome: Settings -> Privacy and security -> Site settings -> search chatgpt.com -> delete its data
  3. Disable every extension (not just privacy ones)
  4. Restart the browser, then sign back in

Step 7: Cross-check browser / device

If one client (web Chrome) fails, try:

  • The official ChatGPT app with the same account
  • A different browser (Edge / Firefox)
  • A different device

If any one works, the issue is on the failing client, not the account.

Step 8: Last resort — Help center

help.openai.com -> submit a ticket. Template:

Subject: Unable to log in to my account [email]

I've been unable to log into [email] for [X] hours.
Steps taken:
- Confirmed the email receives mail (password reset / OTP email status: ____)
- Tested incognito + multiple browsers
- Tested on a clean residential / mobile-data network
- Cleared all chatgpt.com and auth.openai.com cookies
- Disabled QUIC in Chrome (SSO cases)

Current behavior: [precise description, including the exact error string]

Could you investigate?

How to confirm it’s fixed

You’re done when, from your normal browser and network, you reach the chat composer at chatgpt.com and a fresh page reload keeps you signed in (no bounce back to login). If it only works in incognito, the cause was a browser extension or a blocked cookie — fix that in your main profile so it sticks.

When this guide applies

For “the account exists and you can read mail but can’t get in.” If the account is already suspended or deactivated (a banner says so), that needs the OpenAI Help appeal flow instead.

Prevention

  • Stick to one egress IP — don’t node-hop between countries
  • Don’t spread one account across many concurrent sessions
  • Keep the browser lean on privacy extensions — 1-2 essentials only
  • Pick one sign-in method (SSO OR password) and stick with it
  • Use a mainstream email provider (Gmail / Outlook) so verification and OTP codes actually arrive
  • Allowlist otp@tm1.openai.com and noreply@tm.openai.com before you need them
  • Keep personal and work accounts in separate browser profiles to avoid mistaken sign-ins that trip the suspicious-activity lock

FAQ

Why does ChatGPT keep sending me back to the login page with no error? That silent bounce is almost always a wrong/unset password, a blocked session cookie, or corrupt site data. Run “Forgot password?” first; if email arrives but the loop continues, clear chatgpt.com site data (Step 6).

I signed up with Google — how do I reset my ChatGPT password? You can’t. SSO accounts (Google / Microsoft / Apple) have no OpenAI password, so “Forgot password?” won’t help. Keep using the same SSO button and fix the cookie/extension/QUIC issue in Category B.

The login screen wants a 6-digit code I never received. What now? The code comes from otp@tm1.openai.com. Check spam and “Promotions,” resend once, and allowlist that sender. Corporate and some regional mailboxes silently drop it — sign in with a Gmail/Outlook account or ask IT to allowlist the sender.

Why do I get “Oops, something went wrong” on Google sign-in? Cross-site cookies are blocked or a privacy extension is breaking the OAuth callback. Allow third-party cookies for [*.]openai.com and [*.]google.com, disable extensions (or use incognito), and in Chrome set chrome://flags/#enable-quic to Disabled.

Is chat.openai.com still the right address? It redirects, but the current home is chatgpt.com, and the sign-in form is served from auth.openai.com. Allow cookies for both when troubleshooting.

Login works in incognito but not my normal browser — why? Incognito disables extensions and starts with clean cookies. That points to an ad/privacy blocker or corrupt cookies in your main profile. Whitelist the OpenAI/Google domains in the extension and clear chatgpt.com site data.

Tags: #ChatGPT #Debug #Troubleshooting

Related Articles