Check the status page
Open status.openai.com. If there's an incident, it's OpenAI's side — wait and retry rather than troubleshooting locally.
ChatGPT errors, explained
"Something went wrong" is ChatGPT's catch-all error, so it doesn't tell you much on its own. It usually comes from a server hiccup, a long or stuck conversation, browser cache/cookies, an extension, or your network. This guide explains the likely causes, how to tell whether it's OpenAI's side or yours, and the fixes that clear it — and how to keep working while it's down.
What's causing it
Because it's a generic error, several different things can trigger it. Use this to narrow down which one you're dealing with before trying fixes.
| Likely cause | Whose side | What to do |
|---|---|---|
| Server hiccup / OpenAI incident | OpenAI | Check status.openai.com; if there's an incident, wait and retry. Switch models meanwhile. |
| Long or stuck conversation | Either | Start a new chat — a fresh conversation often clears it. |
| Cache / cookies | You | Try incognito, then clear ChatGPT cookies and cache and sign in again. |
| Browser extension | You | Test in incognito; if it works, disable extensions one by one. |
| Network issue / VPN | You | Switch network or turn off VPN. See the network error guide. |
Don't just sit there
If it's an OpenAI-side incident, or you can't clear the error quickly, you don't have to stop. A multi-model workspace lets you switch to another AI and finish what you were doing — then go back to ChatGPT once it recovers.
When ChatGPT throws "something went wrong", switch to Claude, Gemini or another model in the same place and keep going for free — no waiting for OpenAI to recover. Compare answers across models too.
OfficialThe first place to check: live incidents, outages and maintenance.
OfficialOpenAI's own troubleshooting and error articles.
GuideHow to confirm an outage and what to do.
Step by step
If status.openai.com is green, the problem is usually local. Work through these in order — they clear most cases of this generic error.
Open status.openai.com. If there's an incident, it's OpenAI's side — wait and retry rather than troubleshooting locally.
Reload the page, then start a fresh conversation. A long or stuck chat is a common trigger for this error.
This rules out a bad cache, cookies and browser extensions in one step. If it works in incognito, the cause is local to your normal browser profile.
Clear ChatGPT's cookies and cache, then sign in again. Stale cookies or a corrupted cache can cause the error.
Try mobile data or another Wi-Fi, and disable any VPN or proxy that may be interfering with the connection.
If the app fails, try chatgpt.com (or vice-versa). That tells you whether it's the app, your account or OpenAI.
Related guides: network error · login problems · app errors · too many requests · all error codes
All error guides
FAQ
Short answers on what this generic error means, why it keeps happening, and how to clear it.
It's a generic catch-all error, so it doesn't point to one specific cause. It usually comes from a temporary server hiccup on OpenAI's side, a long or stuck conversation, browser cache/cookies, a browser extension, or an unstable network connection. Because it's generic, the fix is to work through the common causes one by one.
If it happens repeatedly, it's often a single chat that has grown too long or got stuck, a cached/cookie issue in your browser, an extension interfering, or a flaky connection. It can also be an OpenAI-side incident. Start a new chat, try an incognito window, and check status.openai.com to see whether it's their side or yours.
It can be either, which is why you should check status.openai.com first. If OpenAI reports an incident, it's their side and you just wait. If the status page is green, it's usually local — cache, cookies, an extension or your network — and the your-side fixes above should clear it.
Refresh the page, then start a new chat to rule out a stuck conversation. If it persists, open an incognito window to bypass cache and extensions, clear ChatGPT's cookies and cache, and try a different network or turn off your VPN. If status.openai.com shows an incident, wait it out instead.
Often yes. A long or stuck conversation is a common trigger for this generic error, and starting a fresh chat sidesteps it. If a new chat also fails, the cause is more likely your browser cache/extensions, your network, or an OpenAI-side incident.
Yes. Extensions — especially ad blockers, privacy tools and ChatGPT add-ons — can interfere with the page and trigger the generic error. The quickest test is an incognito window, where extensions are usually disabled. If it works there, disable extensions one by one to find the culprit.
If the message starts generating and then fails, it's frequently a connection drop or a very long response timing out, though it can also be a server hiccup. Try again, keep the prompt shorter, check your connection, and see status.openai.com if it keeps happening.
It can. Stale cookies or a corrupted cache are a known cause of the generic error. Clearing ChatGPT's cookies and cache (or simply using an incognito window) often resolves it. You'll need to sign in again afterwards.
If the error is on OpenAI's side, or you just can't clear it quickly, use a multi-model workspace like MultipleChat to switch to Claude, Gemini or another model and keep going for free — then return to ChatGPT once it recovers.