AI AI Tools Guidebook
Troubleshooting

ChatGPT Login Works in One Browser but Not Another

Chrome works, Safari fails (or any other pair). The account is fine — the difference lives in cookie policy, extensions, stale SSO state, or browser version.

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

When the same account logs in on Browser A but fails on Browser B, your account is fine — that is a strong signal you do not need to chase. The difference lives in only four places: cookie policy, extension stack, stale SSO state, and browser version. Align Browser B to A on those four and login works.

Fastest fix (works for ~80% of cases): open Browser B’s private window and try to log in. If that works, the culprit is your normal profile (a blocking extension or a stale cookie) — delete the OpenAI cookies and disable privacy extensions. If private mode also fails, it is Browser B’s native cookie policy or an out-of-date version — allow third-party cookies for openai.com and update the browser.

OpenAI’s own login requirement (confirmed in their Help Center, June 2026): cookies and JavaScript must be allowed for chatgpt.com, openai.com, and auth.openai.com. Sign-in runs through an Auth0 handshake that hops across those subdomains, so any policy that blocks cross-site cookies breaks it.

Which bucket are you in?

Run this one test first, then jump to the matching fix.

Private window in Browser BMost likely causeGo to
Logs in fineStale cookie or blocking extension in your normal profileSteps 1–4
Still failsNative cookie policy (Safari/Firefox/Brave) or outdated browserSteps 5–6
Wrong account loads after “Continue with Google”Cached SSO default accountStep 4

Common causes

Safari blocks cross-site cookies by default (“Prevent cross-site tracking”), Firefox ETP Strict does the same, and Brave Shields blocks them aggressively. All three are stricter than Chrome or Edge — and stricter than the Auth0 cross-subdomain handshake OpenAI needs. (Note: Chrome did not deprecate third-party cookies — Google reversed that plan in 2024, so Chrome still allows them by default under a user-choice model. That is why Chrome usually “just works” while Safari/Firefox/Brave do not.)

How to tell: open a private window in Browser B (most extensions are disabled there). Still fails = native browser policy. Works = extensions or a main-profile cookie.

2. An extension only on Browser B blocks the auth callback

uBlock Origin with EasyPrivacy, Privacy Badger, and Decentraleyes sometimes classify the Auth0 callback as a tracker and block it.

How to tell: open DevTools → Network, retry login, and look for a request to auth.openai.com or auth0.openai.com showing (blocked:other) or a red net::ERR_BLOCKED_BY_CLIENT.

You logged into a different ChatGPT account on Browser B once; that cookie is still present but expired. A fresh login writes a new cookie, but the app sometimes reads the stale one first. The ChatGPT session cookie lasts roughly one month, so an old one can linger long after you forgot about it.

How to tell: DevTools → Application → Cookies → https://chatgpt.com. Look for the __Secure-next-auth.session-token entry. If there are duplicates, or one with an Expires date in the past, that is your stale cookie.

4. A different cached SSO default account

Browser A signs into Google as personal@gmail.com; Browser B’s default at accounts.google.com is work@company.com. The same “Continue with Google” button lands you in a different identity — which may have no ChatGPT access, or a different plan.

How to tell: in Browser B, open accounts.google.com and check the default account. Or click “Continue with Google” from the OpenAI login and note which account is suggested first.

Roughly: Safari before 16, Chrome before 110, and Firefox before 102 lack CHIPS (partitioned cookies), the Storage Access API, or a modern SameSite=None implementation that OpenAI’s auth flow relies on.

How to tell: check chrome://version, edge://settings/help, Firefox → “About Firefox”, or Safari → “About Safari”.

Shortest path to fix

Align Browser B to A in order. Stop as soon as login succeeds.

Step 1: Try a private window in Browser B

Chrome / Edge: Cmd/Ctrl + Shift + N
Safari:        Cmd + Shift + N (macOS)
Firefox:       Cmd/Ctrl + Shift + P
Brave:         Cmd/Ctrl + Shift + N

Works = cookies or extensions in your normal profile (do Steps 2–4). Still fails = native policy or version (jump to Steps 5–6).

Step 2: Clear Browser B’s OpenAI / Auth0 cookies

DevTools → Application → Cookies →
  chatgpt.com  openai.com  auth.openai.com  auth0.openai.com
→ delete all entries under each
→ close every chatgpt.com tab → reopen → log in

If you cannot find DevTools, the same thing works from settings: Chrome chrome://settings/content/all → search openai → delete; Safari → Settings → Privacy → Manage Website Data → search openai → Remove.

Step 3: Disable Browser B’s privacy extensions

Open chrome://extensions, edge://extensions, or Firefox about:addons and turn extensions off one at a time. Usual suspects: uBlock Origin, Privacy Badger, Brave Shields, NoScript, Decentraleyes, and any “Cookie AutoDelete” variant. Re-test after each.

Step 4: Check the default SSO account

If you sign in with Google, Apple, or Microsoft:

Google:     accounts.google.com → top-right avatar → switch to the right account → set as default
Apple:      iOS/macOS Settings → [your name] → Sign in with Apple → OpenAI entry
Microsoft:  account.microsoft.com → top-right avatar → sign out of other accounts → sign in to the right one

Or, on the OpenAI login page, after clicking “Continue with Google” pick “Use another account” instead of the suggested avatar.

Menu paths verified June 2026. Where you can, allow cookies for just openai.com instead of disabling protection globally.

BrowserAction
Safari (macOS)Safari → Settings → Privacy → uncheck “Prevent cross-site tracking”
Safari (iOS/iPadOS)Settings app → Apps → Safari → turn off “Prevent Cross-Site Tracking”
Firefoxabout:preferences#privacy → Enhanced Tracking Protection → Custom → uncheck “Cookies” (or set ETP to Standard)
Braveclick the Shields (lion) icon on the page → set Shields to “Down” for this site, or allow all cookies
Chrome / Edgechrome://settings/cookies → under “Third-party cookies” add [*.]openai.com to the Allow list

In Chrome, the section may read “Tracking Protection” instead of “Third-party cookies” depending on your rollout — the Allow exception works the same way.

Step 6: Update Browser B to the latest version

Chrome:  chrome://settings/help → auto-update → Relaunch
Edge:    edge://settings/help → auto-update → Restart
Firefox: Help → About Firefox → auto-update → Restart
Safari:  Apple menu → System Settings → General → Software Update (Safari updates with macOS)

Clear the cache after updating, then retry.

Step 7: Last resort — switch your primary browser

Some niche forks (old Vivaldi 1.x, custom Chromium builds) lag too far behind web standards to support the modern auth flow. Debugging those costs more time than installing current Chrome or Firefox.

How to confirm it’s fixed

  1. Log in on Browser B. You should land on the chat screen, not the login page.
  2. Visit https://chatgpt.com/api/auth/session in Browser B. A valid login returns a JSON object containing your user email and an expires date in the future. An empty {} means you are not actually signed in.
  3. Refresh the page once. If the session holds (no bounce back to login), the cookie is being stored correctly.

Prevention

  • Settle on one primary browser per account; if you must test in several, use dedicated browser profiles instead of mixing accounts in one.
  • Update browsers monthly; do not let them fall several major versions behind.
  • Match the extension stack across browsers so you avoid silent “A has uBlock, B doesn’t” drift.
  • At signup, record which SSO method (Google / Apple / Microsoft) you used and store it next to the account in your password manager.
  • Keep work and personal accounts on separate browser profiles to avoid SSO default confusion.

FAQ

Why does ChatGPT work in Chrome but not Safari with the same account? Chrome still allows third-party cookies by default (Google reversed its deprecation plan in 2024), while Safari blocks cross-site cookies by default via “Prevent cross-site tracking”. OpenAI’s Auth0 login needs cross-subdomain cookies, so Safari’s stricter default breaks the handshake. Uncheck “Prevent cross-site tracking” or allow cookies for openai.com (Step 5).

Is my account banned or broken if only one browser fails? No. A ban or account problem fails in every browser and usually shows a specific error. If even one browser logs in, the account is fine and the issue is purely local to the failing browser.

Private mode logs in fine — what does that tell me? Private windows disable most extensions and start with no stored cookies. If private mode works but your normal window doesn’t, the culprit is a blocking extension or a stale cookie in your normal profile — do Steps 2 and 3.

I cleared cookies and it still fails. What now? Move to Step 3 (disable privacy extensions) and Step 5 (loosen the cookie policy). If a privacy extension keeps re-blocking the Auth0 callback, you will see (blocked:other) in DevTools → Network on every attempt; allowlist openai.com in that extension.

Why does “Continue with Google” log me into the wrong account? Your browser has a different default Google account cached. Click “Use another account” on the Google chooser, or set the correct account as default at accounts.google.com (Step 4).

Tags: #ChatGPT #ChatGPT account #Troubleshooting #Debug #Browser-specific

Related Articles