If you’ve ever opened ChatGPT and been hit with a vague “Something went wrong” message right when you needed it most, you’re not alone. This error shows up without warning, gives you almost no useful information, and can block access to the entire app. I ran into this myself after a browser update and spent way longer than I’d like to admit trying random fixes before finding what actually worked.
Quick Answer — Most Common Fixes
- Clear your browser cache and cookies (not just history)
- Disable browser extensions, especially ad blockers and VPNs
- Log out completely, then log back in from an incognito window
- Check if OpenAI’s servers are down at status.openai.com
- Try a different browser or device to isolate the issue
Why ChatGPT Shows “Something Went Wrong”
The error message itself is essentially a catch-all. ChatGPT uses it for a wide range of failures, which makes diagnosis harder than it should be. Here are the real causes worth knowing about.
1. Corrupted Session Token
When you log into ChatGPT, your browser stores a session token. If that token gets corrupted — by a browser update, a power outage mid-session, or a failed sync — ChatGPT can’t authenticate you properly. It doesn’t tell you this. It just says “Something went wrong.”
2. Browser Extension Interference
Ad blockers, privacy shields, and VPN extensions are the most common culprits here. Some extensions intercept API calls and modify headers or block certain requests. ChatGPT’s frontend relies on specific API responses, and if those get filtered or delayed, the app breaks silently.
I’ve seen uBlock Origin block a WebSocket connection that ChatGPT uses for streaming responses. The result looks exactly like this error.
3. OpenAI Server-Side Issues
Sometimes it’s not your machine at all. OpenAI has had several partial outages where only certain regions or account types were affected. During these periods, users see “Something went wrong” with no indication that the problem is on OpenAI’s end. Always check status.openai.com before digging into local fixes.
4. Stale or Conflicting Cookies
Old cookies from a previous login session can conflict with a new one. This is especially common if you’re logged into multiple Google or Microsoft accounts that are linked to ChatGPT, or if you recently changed your OpenAI password.
5. Account or Subscription Issues
Less obvious, but worth checking: if your ChatGPT Plus subscription had a payment failure or your free trial expired, some parts of the UI can break in odd ways. The error may appear mid-conversation rather than at login.
Common Scenarios Where This Happens
The error doesn’t always behave the same way. Context matters.
- On first load — Usually a session or server issue
- After typing a message — Often a streaming/WebSocket failure caused by extensions or network filtering
- After browser update — Cookie or storage conflicts are the most likely cause
- On mobile (iOS/Android app) — Usually requires a full app cache clear or reinstall
- After account password change — Session tokens are invalidated; logging out and back in usually fixes it
- In corporate networks — Firewall or proxy rules may be blocking OpenAI’s API endpoints
Technical Comparison: Common Causes vs. What Actually Fixes Them
| Cause | Symptom | Commonly Suggested Fix | Actually Works? |
|---|---|---|---|
| Corrupted session token | Error on load or mid-session | Refresh the page | Rarely |
| Browser extension blocking | Error after sending message | Disable all extensions | Usually yes |
| Stale cookies | Error after password change | Clear cookies for openai.com | Yes |
| OpenAI server issue | Error across all browsers | Wait it out | Only option |
| VPN geo-blocking | Consistent error in one region | Switch VPN server/disable it | Often yes |
| Corporate proxy | Error on work network only | Use mobile data or home network | Yes |
| Expired subscription | Mid-conversation error | Check billing at platform.openai.com | Yes |
Step-by-Step Fixes
Step 1: Check OpenAI’s Server Status
Before touching anything on your end, open a new tab and go to status.openai.com. If there’s an active incident, no local fix will help — you just have to wait.
[Image: Screenshot of status.openai.com showing all systems operational vs. a partial outage notice]
Step 2: Try an Incognito Window First
Open an incognito or private browsing window and go to chat.openai.com. This disables extensions and uses a fresh cookie jar. If ChatGPT works in incognito, you’ve confirmed the issue is either an extension or a corrupted cookie — not a server problem.
Step 3: Clear Cookies Specifically for OpenAI
Don’t just clear all browser history. Target the OpenAI cookies directly.
In Chrome:
- Go to
chrome://settings/cookies - Search for
openai.com - Click the trash icon next to each entry
- Reload ChatGPT and log back in
In Firefox:
- Open DevTools → Storage tab → Cookies
- Right-click on
chat.openai.comentries and delete
In Safari:
- Settings → Privacy → Manage Website Data
- Search for
openaiand remove
Step 4: Disable Extensions One by One
If you can’t use incognito mode, disable your extensions individually rather than all at once. This helps you identify exactly which one is causing the problem. Ad blockers and VPN extensions are the most likely offenders.
[Image: Chrome extensions management page showing a list of extensions with toggle switches to disable them]
Start with:
- uBlock Origin / AdBlock Plus
- Privacy Badger
- VPN extensions (NordVPN, ExpressVPN browser plug-ins)
- Any “cookie manager” extensions
Step 5: Log Out Completely and Back In
This forces a fresh session token. Don’t just close the tab — use the account menu to explicitly log out, then log back in.
If you use Google or Microsoft SSO, also try logging out of those accounts and back in before returning to ChatGPT.
Step 6: Try a Different Browser or Device
If nothing works in your primary browser, try Chrome, Firefox, or Edge. If ChatGPT works in a different browser, the issue is isolated to your primary browser’s profile or stored data.
On mobile, go to your phone’s app settings, clear the ChatGPT app cache (not uninstall — just cache), then reopen.
Step 7: Check Your Subscription and Account Status
Log in at platform.openai.com and check:
- Billing → Is there a failed payment?
- Usage → Are you near a usage limit?
If your Plus subscription lapsed, the ChatGPT interface can behave inconsistently before fully reverting to the free tier.
What Actually Worked For Me
I was getting the “Something went wrong” error every time I tried to send a message. The page would load fine, I’d type a prompt, hit enter — and then the error would appear. No message sent, no response.
I tried the obvious stuff first: refreshing the page (didn’t help), opening a new tab (same error), even restarting the browser.
Then I tried incognito. ChatGPT worked fine. So I knew it was an extension.
I started disabling them one by one. Chrome’s password manager — fine. A tab grouping extension — fine. Then I disabled Privacy Badger, and ChatGPT immediately started working in my normal window.
Turned out Privacy Badger had learned to block a specific tracking domain that OpenAI’s streaming API uses. When it blocked that domain, the streaming connection couldn’t establish, and ChatGPT showed the generic error. I whitelisted chat.openai.com and api.openai.com in Privacy Badger’s settings and haven’t had the issue since.
The lesson: the culprit is rarely the most obvious extension.
Advanced Fixes and Edge Cases
Diagnosing with Browser DevTools
If basic fixes don’t work, open DevTools (F12) and check the Console and Network tabs while reproducing the error.
Look for:
- Failed requests to
api.openai.com— especially 401, 403, or 429 status codes - WebSocket connection errors in the Console — these usually appear as
WebSocket is closed before the connection is established - CORS errors — these can appear when a browser extension modifies request headers
A 401 error means your session token is invalid. A 429 means you’ve hit a rate limit. CORS errors almost always point to an extension.
Corporate Network and Proxy Issues
Some company networks route all HTTPS traffic through a proxy that performs SSL inspection. This breaks the WebSocket connection ChatGPT uses for streaming.
Signs this is happening:
- The error only occurs on your work network
- ChatGPT works fine on your phone’s data connection
- Other AI tools with streaming responses also fail
The fix usually requires IT to whitelist *.openai.com and *.oaiusercontent.com at the proxy level. This isn’t something you can resolve on your own without admin access.
You can verify this by running a quick curl command from a terminal on your work machine:
curl -I https://chat.openai.comIf you see unexpected proxy headers in the response, or the command times out, you’ve found the issue.
Prevention Tips
- Don’t use VPN browser extensions with ChatGPT — use a system-level VPN instead, which is less likely to interfere
- Whitelist openai.com in your ad blocker — privacy extensions are the most common source of these errors
- Keep your browser updated — outdated browsers can have issues with modern WebSocket implementations
- Use a dedicated browser profile for AI tools if you work with heavy extension setups
- Check status.openai.com first — it saves time and rules out the most frustrating cause immediately
FAQ
Why does ChatGPT say “Something went wrong” but work fine in incognito? This almost always means a browser extension is interfering. Incognito mode disables extensions by default. Try disabling them one by one in your normal browser window to find the culprit.
The error only happens when I send a message, not when the page loads. Why? Page loading and message sending use different processes. The error on send usually points to a failed API call — either a WebSocket issue, a rate limit (HTTP 429), or a session problem that only shows up when you try to interact.
I cleared my cookies and it still doesn’t work. What else can I try? If cookie clearing didn’t help, try a completely different browser. If that works, your primary browser’s profile may be corrupted. You can try creating a new browser profile and importing just your bookmarks — don’t import cookies or extensions initially.
ChatGPT works on my phone but not my laptop. What does that mean? The issue is local to your laptop — either a browser configuration, extension, or network setting. Your phone likely bypasses whatever is interfering. Start with extensions and cached data.
Can this error mean my account is banned? Unlikely to show as this generic error. Account bans usually come with a specific notice. If you’re worried, try logging in at platform.openai.com — if you can access your account dashboard, you’re not banned.
Does this happen more with ChatGPT Plus than the free tier? The error itself isn’t more common on Plus, but Plus users sometimes see it mid-conversation when the GPT-4 model endpoint has a temporary issue while the free tier routes fine. It’s rare but documented.
Editor’s Opinion
Honestly this error drove me crazy the first time. I wasted like 20 minutes refreshing and clearing history before I even thought to check my extensions. The incognito trick is the thing I’d tell everyone to try first — it literally takes 10 seconds and tells you immediately if it’s an extension problem. The status page check should probably be step one too, because if OpenAI’s having a bad day, nothing you do locally matters. Most of the “try this fix” articles skip both of those and send you down long troubleshooting rabbit holes for no reason.
