Step-by-Step Fix
Follow this order to avoid repeatedly retrying the same broken session state.
1. Do the 30-Second Isolation Test (Incognito)
- Open an incognito/private window
- Visit:
https://chat.openai.com/ - Try to sign in
If incognito works: your issue is almost certainly cookies, extensions, or browser settings in your normal browser. Continue with steps 2–4. If incognito also loops: the issue is your network or account — jump to step 5 or 6.
2. Clear the Relevant Site Data (Not Everything)
Don't wipe your entire browser history — only clear OpenAI's specific cookies. ChatGPT's authentication spans multiple domains.
In your normal browser, clear site data for all of these:
chat.openai.comopenai.comauth0.com
Then:
- Close all ChatGPT tabs (not just the loop tab)
- Wait 10 seconds
- Open a fresh tab and sign in again
This resolves most login loops caused by stale tokens within 60 seconds.
3. Disable Extensions That Commonly Break Auth
Temporarily disable (then retry once):
- Ad blockers (uBlock Origin, AdBlock Plus)
- Privacy/script blockers (Privacy Badger, Ghostery, NoScript)
- Cookie management tools (Cookie AutoDelete)
- VPN/proxy browser extensions
If the loop stops after disabling one extension, you've found the culprit. Add openai.com and auth0.com to that extension's allowlist rather than disabling it permanently.
4. Check Cookie Settings (Especially Third-Party Cookies)
ChatGPT's auth callback flows through auth0.com, which is a third-party domain relative to chat.openai.com. Strict privacy modes that block all third-party cookies break this flow.
Verify and fix:
- Chrome:
chrome://settings/cookies→ set to "Allow all cookies" or add[*.]auth0.comand[*.]openai.comto the always-allow list - Firefox: Settings → Privacy & Security → Enhanced Tracking Protection → change from Strict to Standard
- Safari: Settings → Privacy → uncheck Prevent cross-site tracking (temporary test)
- Brave: go to Settings → Privacy → Shields → and configure cookie handling to allow
openai.com
Then retry signing in.
5. Rule Out Network / VPN / Proxy Issues
VPN IP changes between login and callback cause the server to reject the session:
- Turn off VPN/proxy completely
- Switch to a phone hotspot to rule out your home or corporate network
- Switch DNS if your network is heavily filtered (try 8.8.8.8 or 1.1.1.1)
If hotspot works but Wi-Fi doesn't: there's a network filtering or routing issue on your local network.
6. Confirm Account and Workspace Context (SSO Mismatch)
Login loops happen when an account is half-authenticated but denied workspace access:
- Confirm you're using the correct email address — check which email is registered at platform.openai.com
- If you have Team or Enterprise access, confirm the workspace is still active and your access hasn't been revoked
- If you belong to multiple workspaces, try logging into a different workspace or your personal account
7. If It Fails Everywhere, Assume a Platform-Side Issue
If the same loop occurs on multiple browsers, multiple devices, and multiple networks (including mobile hotspot):
- Stop repeated retries — they won't help and can trigger security flags
- Check status.openai.com for active incidents
- Wait 30–60 minutes and test once more
- If the loop persists, submit a support report
8. Collect Evidence for Support
Prepare a clear support report:
- The exact URL in the address bar at the end of the loop (copy it — it contains diagnostic info)
- Any error text shown on screen
- Your browser name and version, OS
- Whether incognito reproduces the loop
- Whether it happens on a second device or different network
- Submit at help.openai.com
Why This Happens
ChatGPT authenticates via Auth0, which uses a multi-step OAuth 2.0 redirect flow:
- chat.openai.com redirects you to auth0.openai.com to authenticate
- Auth0 validates credentials and redirects back to chat.openai.com with a signed session token
- chat.openai.com sets a session cookie and loads the chat interface
A login loop occurs when step 3 fails. The most common reasons: the browser can't set the session cookie (because of cookie restrictions or a conflicting stale token), an extension blocks the callback request, or a VPN IP change causes auth0 to reject the session token as a security measure. Each failed step 3 sends you back to step 1, creating the loop. The fix is almost always to clear the state that's preventing the cookie from being set.
Common Root Causes
- Stale or invalid session cookies from openai.com or auth0.com
- Browser extensions blocking auth callback requests
- Strict third-party cookie or privacy settings blocking auth0.com
- VPN or proxy IP changes mid-authentication
- SSO/workspace mismatch (wrong account or revoked access)
- Platform-side login or auth incident
Prevention Tips
- Keep one clean browser profile for ChatGPT with no conflicting extensions
- Avoid stacking multiple request-blocking extensions — each adds a new potential failure point
- Don't keep ChatGPT tabs open for days without refresh — sessions expire naturally after 30+ days, so periodic refreshes keep the session alive
- When issues start, test incognito immediately before changing multiple settings simultaneously
- If you use Cookie AutoDelete, add openai.com and auth0.com to its protected list