How to Fix ChatGPT ‘Something Went Wrong’ Error

There it is, the most unhelpful error message in AI: “Something went wrong.” What went wrong? It won’t say. How to fix ChatGPT “something went wrong” error? After encountering this more times than I’d like to admit, I’ve developed a troubleshooting sequence that resolves it in the vast majority of cases. Work through it in order — don’t skip steps. The question we answer here: how to fix chatgpt something went wrong error.

How to fix ChatGPT something went wrong error

Step 1: Check if it’s actually you (1 minute)

First, the OpenAI status page. If there’s an active incident, the error is server-side and no amount of cache-clearing will help — wait or switch to a backup AI. Second, try the same prompt in a fresh chat. If the new chat works, the problem is specific to the old conversation (corrupted context, a problematic message) — not your setup. This single test eliminates half the diagnostic tree.

Step 2: The browser fixes (in order)

1. Hard refresh: Ctrl+Shift+R (Cmd+Shift+R on Mac). Fixes stale frontend state — surprisingly effective.
2. Clear site data: Clear cache and cookies specifically for chatgpt.com / chat.openai.com. Corrupted local state is a top cause of persistent errors.
3. Incognito/private window: If it works here, an extension or cached state is the culprit. Then disable extensions one by one (start with ad-blockers, privacy tools, and script managers).
4. Different browser: Rules out browser-specific issues entirely. If Chrome fails but Firefox works, you know where the problem lives.
5. Log out and back in: Refreshes your session tokens. Simple, often effective, inexplicably under-tried.

Step 3: The network fixes

1. Check your connection: Can you load other sites normally? If everything’s slow, it’s your network, not ChatGPT.
2. Disable VPN/proxy temporarily: VPNs are a frequent cause — some endpoints get blocked or rate-limited. Test without it.
3. Switch networks: Phone hotspot or mobile data. If it works on a different network, your ISP or local network is interfering (DNS issues, firewall rules, ISP-level blocking in some regions).
4. Try the mobile app: Uses different infrastructure paths; often works when web fails.
5. Flush DNS: On the off chance it’s DNS weirdness (rare but real).

Step 4: The conversation fixes

Sometimes the error is content-triggered: overlong conversations — start fresh (summarize and continue in a new chat if needed). Problematic uploads — a corrupted file attachment can break the chat; remove it and retry. Specific prompts — if one particular message always errors, rephrase it; occasionally content filters or processing edge cases trip on specific inputs. Regenerate — sometimes it’s transient; waiting 60 seconds and retrying just works.

Step 5: The account fixes

• Check your limits: Free-tier users hitting rate limits see errors rather than friendly messages sometimes. Wait for the reset or check OpenAI help center for current limit policies.
• Payment issues (paid users): Failed billing can restrict access oddly. Check your subscription status.
• Try a different account: Isolates account-specific issues (rare, but they happen).

When nothing works

If you’ve done all of the above across devices and networks: it’s almost certainly server-side or account-side. Contact support with specifics (when it started, what you’ve tried, error details from browser console if you’re technical). Meanwhile, use a backup AI service — ChatGPT slow or down has the outage playbook, and fix ChatGPT network errors covers the related error family. For ongoing slowness rather than errors, why ChatGPT is slow is the companion guide.

Prevention

Decoding the unhelpful: what “something” usually is

Since the error won’t tell you, here’s what’s usually behind it, from most to least common in my experience: stale frontend state (the app’s local data got out of sync — hard refresh territory, ~30% of cases). Corrupted conversation context (something in the chat history breaks processing — new chat fixes it, ~25%). Extension interference (ad-blockers and privacy tools vs. the app’s requests, ~20%). Network/VPN issues (~15%). Actual server problems (~10% — check status page first and save yourself the troubleshooting). These are rough estimates, not science — but they tell you where to spend your effort: refresh, new chat, incognito, network, status page. In that order. The error message is generic because the causes are many; the fix sequence works because it walks the probability ranking.

Mobile app specific fixes

If you’re on the mobile app: force-close and reopen (not just backgrounding — actually swipe it away). Check for app updates (stale versions develop weird errors). Clear app cache (in app settings or OS app settings — the mobile equivalent of clearing browser cache). Reinstall as last resort (your chats live server-side, so you won’t lose them — but you’ll need to log back in). Toggle between WiFi and mobile data (isolates network-specific issues fast). Mobile errors skew toward app-state and network causes rather than extension causes (no extensions on mobile), so weight your troubleshooting accordingly.

Keep chats reasonably scoped (new chat per topic), keep your browser updated, don’t run seventeen privacy extensions simultaneously, and maintain that backup AI bookmark. The “something went wrong” error is ChatGPT’s check-engine light — uninformative by design, usually fixable with systematic elimination. Work the sequence; don’t just refresh angrily. (Though we’ve all been there.)