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 — differences live in cookie policy, extensions, and version.

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

When the same account logs in on Browser A but fails on Browser B, the account is definitely fine — a strong signal you don’t have to chase. Differences only live in three places: cookie policy, extension stack, stored SSO state. Align Browser B to A on these three and login works. A small minority of cases are Browser B being too old to support modern cookie features — then upgrade or just switch to a mainstream browser.

Common causes

Safari ITP strict by default, Firefox ETP “Strict” by default, Brave Shields strict by default. All three block cross-subdomain cookies more aggressively than Chrome / Edge — exactly what OpenAI’s Auth0 handshake needs.

How to judge: Open Incognito in Browser B (most extensions disabled). Still fails = native browser policy; OK in Incognito = extensions or main-profile cookies.

2. Extension installed only on Browser B blocks auth callback

uBlock + EasyPrivacy, Privacy Badger, Decentraleyes will sometimes block auth.openai.com/u/login/callback requests they classify as tracking.

How to judge: DevTools → Network → re-login → look for requests showing (blocked:other) or red ERR_BLOCKED_BY_CLIENT.

You logged into a different ChatGPT account on B once; the cookie is still present but expired. New login writes a fresh cookie but the UI prefers the stale one.

How to judge: DevTools → Application → Cookies → chatgpt.com — look for duplicate __Secure-next-auth.session-token entries or one with an ancient timestamp.

4. Browser B has a different cached SSO account

Browser A logs into Google as personal@gmail.com. Browser B’s default at accounts.google.com is work@company.com. Same “Continue with Google” button lands in different accounts.

How to judge: In Browser B, visit accounts.google.com first and check the default account. Or click “Continue with Google” from OpenAI login and see which account is suggested first.

5. Browser version too old for modern cookie / crypto features

Safari < 16, Chrome < 110, Firefox < 102 lack CHIPS (Partitioned cookies), Storage Access API, or modern SameSite=None implementation. OpenAI’s newer auth flow needs them.

How to judge: Visit chrome://version or Safari → About Safari for the version.

Shortest path to fix

Align Browser B to A in order.

Step 1: Try Incognito in Browser B

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

Works = cookies / extensions in your normal profile (continue Steps 2-4). Still fails = native browser 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
→ close all chatgpt.com tabs → reopen → log in

Step 3: Disable Browser B’s extensions

chrome://extensions or about:addons — turn off one at a time. Usual suspects: uBlock Origin, Privacy Badger, Brave Shields, NoScript, Decentraleyes, any “Cookie AutoDelete” variant.

Step 4: Check default SSO account

If using SSO:

Google:    accounts.google.com → top-right avatar → switch to the account → set default
Apple:     iOS Settings → your name → Sign in with Apple → OpenAI entry
Microsoft: microsoft.com → top-right → "Sign out all other accounts" → re-login to the right one

Or at the OpenAI login page, after clicking “Continue with Google”, choose “Use another account” instead of the default avatar.

By browser:

BrowserAction
SafariSettings → Privacy → uncheck “Prevent cross-site tracking”
Firefoxabout:preferences#privacy → ETP → Custom → uncheck “Cookies”
BraveShields icon → “Allow all cookies” for this site
Chromechrome://settings/cookies → add [*.]openai.com to Allow

Step 6: Upgrade Browser B to latest

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

Clear cache after upgrading, then retry.

Step 7: Last resort — switch primary browser

Some niche forks (old Vivaldi 1.x, custom Chromium builds) lag too far behind web standards. Debugging them costs more time than just installing Chrome / Firefox.

Prevention

  • Settle on one primary browser per account; if you must test multiple browsers, use dedicated browser profiles.
  • Upgrade browsers monthly; don’t let them fall multiple major versions behind.
  • Match the extension stack across browsers — avoid silent A-has-uBlock-B-doesn’t drift.
  • At signup, record which SSO method (Google/Apple/MS) you used; save the method alongside the account in your password manager.
  • Keep work and personal accounts on separate browser profiles to avoid SSO default confusion.

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

Related Articles