Step-by-Step Fix
1. Check OpenAI's status page first
Visit status.openai.com. If there is an active incident, no local fix will help. Wait for OpenAI to resolve it, which usually takes under an hour for minor issues. Checking this first saves significant troubleshooting time.
2. Refresh your session
A stale or corrupted session token is the most common cause of persistent "something went wrong" errors:
- Click your profile picture in ChatGPT
- Select Log out
- Close all ChatGPT tabs
- Wait 60 seconds
- Go to chat.openai.com and sign in again
Send a test message immediately after signing in.
3. Open an incognito window
Open a private or incognito window and go to chat.openai.com. Sign in and start a new conversation.
- Works in incognito → the problem is a browser extension or corrupted cache in your regular browser
- Still fails in incognito → the problem is your network, account, or OpenAI's servers
4. Clear cache and cookies fully
- Browser settings → Privacy → Clear browsing data
- Select All time as the time range
- Check Cookies and other site data and Cached images and files
- Click Delete
- Reopen the browser, sign into ChatGPT, retry
For a more targeted approach: Settings → Privacy → Site settings → View stored data → search openai.com → delete only those cookies.
5. Disable all extensions
Type chrome://extensions in Chrome's address bar. Toggle off every extension. Reload ChatGPT and retry. If the error disappears, re-enable extensions one at a time to find the problematic one. Ad blockers, privacy tools, and VPN plugins are the most common offenders.
6. Start a new conversation
If the error only happens in one specific chat:
- Open a new chat from the sidebar
- Copy and paste the relevant context from your old conversation
- Continue the work from there
The original conversation remains in your history even if you cannot add new messages to it.
7. Switch to a different network
Connect to a phone hotspot or a different Wi-Fi network. If ChatGPT works on a different network, your main connection is filtering or throttling the requests. Check whether VPN is enabled and disable it — VPN endpoints are frequently throttled for OpenAI traffic.
8. Collect evidence and escalate
If the error persists across two browsers, two networks, and after clearing all browser state:
- Screenshot the exact error text with timestamp
- Note any error codes alongside the message (401, 429, 500, 503)
- Contact support at help.openai.com with account email, start date, and whether the error appears in the mobile app
Why This Happens
"Something went wrong" is ChatGPT's catch-all error displayed when the specific underlying error is not surfaced to the user interface. It can represent a broken authentication token, a failed network request, a server-side processing error, or an infrastructure issue — all displayed identically from the user's perspective. This is intentional design to prevent exposing internal error details, but it makes diagnosis harder because the same message covers dozens of different root causes. The systematic isolation approach — incognito, then network, then extensions — works because it eliminates possible causes one at a time without requiring knowledge of which specific error is occurring.
Common Mistakes to Avoid
- Refreshing the page without clearing cache — Refreshing does not clear session data; you must explicitly delete cookies for the fix to take effect
- Only trying incognito without disabling extensions — Some extensions remain active in incognito mode by default; check chrome://extensions to confirm
- Retrying the same message repeatedly — If a specific message triggers a server-side error, sending the same content repeatedly produces the same result; try a shorter test message first
- Not checking the mobile app — The mobile app on a different network is the fastest way to determine whether the issue is account-side or device/browser-side
Related Issues
- ChatGPT network error fixes
- ChatGPT error in message stream
- ChatGPT access denied or account blocked
Prevention Tips
- Keep a shortcut to status.openai.com in your browser bookmarks — during any ChatGPT error, checking this first takes 10 seconds and immediately tells you if the issue is platform-wide
- Use a dedicated browser profile for ChatGPT work with only essential extensions installed; this reduces the chance of extension conflicts causing random errors
- Periodically clear cookies for chat.openai.com (monthly) to prevent session token corruption from accumulating
- Avoid using public Wi-Fi for long ChatGPT sessions — unstable connections that repeatedly disconnect and reconnect are common triggers for "something went wrong" errors during streaming
Additional FAQ
Q: Can the "something went wrong" error cause me to lose conversation content? If the error occurs during a response, the in-progress response text may not be saved to the conversation. Your previous messages are preserved — only the interrupted response is lost. Reload the page and check your conversation history; if the last response is missing, ask the question again. Starting from a fresh conversation also helps if the specific thread has become corrupted on the backend.
Q: Why does the error happen more often at certain times of day? ChatGPT experiences higher error rates during peak usage hours — typically 9 AM to 6 PM US Eastern time, which coincides with US business hours. During these periods, server load increases and streaming connections are more likely to encounter timeouts. If you experience frequent errors during these windows, scheduling intensive ChatGPT work for off-peak hours (early morning or late evening US time) can significantly reduce error frequency.
Q: Does using the mobile app avoid the "something went wrong" error? The mobile app uses the same backend as the web browser but bypasses browser-specific issues like extension conflicts and cached JavaScript corruption. If you experience this error exclusively on the web, the mobile app is a reliable alternative while you troubleshoot the browser issue. The mobile app also maintains a more stable streaming connection on cellular data than some browser environments do, reducing connection-drop-related errors.
Q: Is there a way to see what the actual underlying error is? Press F12 to open browser developer tools before triggering the error. In the Network tab, look for failed requests (shown in red) when the error appears. The request URL and HTTP status code reveal the actual cause: a 401 means authentication expired, a 429 means you hit a rate limit, a 500 means a server-side error, and a 503 means the service is temporarily unavailable. This information is also useful to include in a support ticket as it bypasses the generic error message.
Q: Could a ChatGPT browser extension or plugin be causing the error? Yes — third-party ChatGPT extensions that enhance the interface (saving prompts, adding features, modifying the UI) frequently conflict with ChatGPT's own JavaScript. These extensions intercept or modify requests in ways that trigger errors. To test this, temporarily disable all ChatGPT-specific extensions in your browser and retry. If the error disappears, re-enable them one by one to identify the conflicting one.
Additional FAQ
Q: How do I know if the problem is on my end or the platform's side? Check the platform's official status page first — most services maintain a public status page that shows current incidents and outages. If no incident is posted and the problem only affects your account (not reported widely on Reddit or Twitter), it is likely a local issue. Testing in incognito mode and on a different network also helps isolate whether the problem is browser-specific, network-specific, or account-specific.
Related Articles
- ChatGPT billing history and receipts
- ChatGPT login not working
- ChatGPT something went wrong error
- ChatGPT network error fix
Additional FAQ
Q: How do I know if the problem is on my end or the platform's side? Check the platform's official status page first — most services maintain a public status page that shows current incidents and outages. If no incident is posted and the problem only affects your account (not reported widely on Reddit or Twitter), it is likely a local issue. Testing in incognito mode and on a different network also helps isolate whether the problem is browser-specific, network-specific, or account-specific.