ChatGPT “Something Went Wrong” — How to Fix It
“Something went wrong” is the generic error ChatGPT shows whenever a request fails — it does not tell you why. This guide shows how to tell an OpenAI outage from a browser or session problem, and walks through the fixes in the order most likely to work.
What does “something went wrong” mean?
It is a catch-all, client-side message the ChatGPT web app (chat.openai.com / chatgpt.com) shows when a request fails for any reason. Because it is generic, the same text can point to several very different causes:
- An OpenAI outage or overload: the backend is down or at capacity — nothing on your end will fix it.
- A browser or session issue: stale cookies/cache or an expired auth token — the most common cause of the transient version.
- A conversation that is too long: the thread exceeds the model's context window and new messages fail.
- A network, VPN, or firewall block: a proxy or corporate firewall interrupts the connection to OpenAI.
- A browser extension interfering: ad-blockers and privacy extensions can break ChatGPT's streaming response.
Before you troubleshoot, it helps to know which of three situations you are actually in — the fix is different for each:
| What you see | What it means | What to do |
|---|---|---|
| “Something went wrong” | A single request failed — often local (session, cache, extension) | Refresh / clear cookies / new chat |
| “ChatGPT is at capacity” | OpenAI is throttling free traffic during peak load | Wait a few minutes and retry |
| Blank page / repeated failures | A platform-wide outage or incident | Check status, then wait |
The key distinction: a one-off “something went wrong” is usually fixed by a refresh or a fresh session, while “at capacity” and hard outages are OpenAI-side and only resolve with time. Confirm which you are facing at prismix.dev/service/openai.
5 steps to fix “something went wrong”
Check whether it is an OpenAI outage first
Do not waste time clearing your cache if ChatGPT is down for everyone. Before anything else, confirm whether OpenAI is having an incident. If it is, no local fix will help — you just wait for the fix to land.
Diagnosis checklist
- Open prismix.dev/service/openai — active incidents appear at the top, updated every 5 minutes.
- Cross-check status.openai.com for OpenAI's own incident page.
- Status all green but the error continues? The problem is local — move on to Step 2.
Hard-refresh, clear cookies, and re-login
This is the single most effective fix for the transient error. An expired or corrupted session token is the number-one cause — a fresh login forces a new, valid token.
Do this in order
- Hard-refresh the page:
Ctrl+Shift+R(Windows/Linux) orCmd+Shift+R(Mac). - Still failing? Clear cookies and site data for
chat.openai.comandchatgpt.com(browser Settings → Privacy → Site data). - Reload ChatGPT and sign in again. Your chats and settings are stored server-side — clearing cookies does not delete them.
Start a new chat or shorten a long conversation
If the error only appears in one long-running thread — but a brand-new chat works fine — you have hit the model's context limit. A conversation keeps everything in context, and once the thread is too large, every new message fails.
- Click New chat and paste in only the context you still need — this resets the token count instantly.
- For a thread you want to keep, delete or edit out the earliest large messages to bring it back under the limit.
- Rule of thumb: if a fresh chat works and the old one does not, the old thread is the problem, not your account.
Disable VPN, proxy, and browser extensions
ChatGPT streams responses over a long-lived connection. VPNs, corporate proxies, ad-blockers, and privacy extensions can interrupt that stream and surface as “something went wrong,” often partway through a reply.
- Turn off any VPN or proxy and retry — some VPN exit nodes are rate-limited or blocked by OpenAI.
- Open ChatGPT in an incognito/private window, which loads with extensions disabled and a clean cache. If it works there, an extension is the culprit — re-enable them one at a time to find it.
- Common offenders: ad-blockers (uBlock, AdGuard), privacy tools (Privacy Badger, Ghostery), and script blockers (NoScript).
Try a different browser, network, or the mobile app
If the error follows you across new chats and incognito, isolate whether it is your browser profile, your network, or your region.
- Different browser: if ChatGPT works in Firefox but not Chrome, your original browser profile is corrupted — reset it or use a fresh profile.
- Different network: switch from office Wi-Fi to a phone hotspot. If it starts working, a firewall or network filter was blocking OpenAI.
- Regional block: ChatGPT is not available in every country. The official mobile app on cellular data is a quick way to confirm access from your location.
Get an email the next time OpenAI goes down
Outage alerts for OpenAI, straight to your inbox. No account needed, unsubscribe in every email.
Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.
FAQ
Is “something went wrong” an OpenAI outage or my browser?
It can be either — the message is generic and does not name a cause. Split the two by checking prismix.dev/service/openai and status.openai.com. An active incident means it is a platform outage; green status means the problem is local (session, cache, extension, or VPN). If it is local, hard-refresh, clear ChatGPT cookies, and re-login.
Why does ChatGPT say “something went wrong” mid-conversation?
Usually one of two things. A very long thread can exceed the model's context window, so new messages fail — start a new chat to fix it. Or your session auth token expired while the tab sat open for hours, so the next message fails until you refresh and re-login. An ad-blocker or privacy extension breaking the streaming response can also trigger it partway through a reply.
Does clearing ChatGPT cookies log me out of everything?
No. If you clear cookies only for chat.openai.com and chatgpt.com, you are logged out of ChatGPT only, not other sites. You will sign in again (and re-do 2FA if enabled), but your account, chat history, and settings live server-side and are not deleted. This is the most effective fix for the transient error because it forces a fresh, valid session token.
Does the “something went wrong” error affect the OpenAI API too?
No — that text comes from the ChatGPT web app. The OpenAI API returns structured HTTP errors instead, such as 429 (rate limit) or 500 (server error). Both the web app and the API share OpenAI's backend, so a major outage can hit them together — confirm at prismix.dev/service/openai.
How do I fix ChatGPT “something went wrong” fastest?
In order of speed: hard-refresh (Ctrl+Shift+R / Cmd+Shift+R); start a new chat if the error is in a long thread; open an incognito window to rule out extensions and cache; clear cookies for chat.openai.com and re-login; then disable VPN and privacy extensions. If none work, it is likely an OpenAI-side outage — check prismix.dev/service/openai and wait.