When using ChatGPT, if you see “Something went wrong,” the page keeps spinning, or your chat history won’t load, it’s usually not a broken account—it’s more often your network, browser cache, or requests being restricted. Below is a practical troubleshooting order by symptom to help you get back to normal conversations as quickly as possible.
First, confirm whether it’s a server-side issue: avoid wasted effort
If ChatGPT suddenly shows widespread errors, messages won’t send, or the page keeps refreshing, open the status page at status.openai.com first to see whether there’s an outage or degraded performance. If the status page shows an incident, the most effective approach is to wait a bit and try again, rather than repeatedly refreshing and potentially triggering more restrictions. You can also reduce the number of ChatGPT tabs you have open to avoid stacking requests.
Login errors and redirect loops: start with your browser environment
If ChatGPT logs you in and then kicks you back to the login page, keeps loading endlessly, or shows verification failures, a common cause is blocked browser cache or third-party cookies. First, test ChatGPT in an incognito/private window; if it works there, clear site data (cookies and cache) in your regular browser and allow third-party cookies. Then check extensions such as ad blockers, privacy tools, or script managers—temporarily disable them and try logging in again.
Conversation loading failures and blank history: fix cache and sync issues
If the ChatGPT sidebar history doesn’t appear or you get “Conversation not found” after clicking a chat, start with a hard refresh and log out/in once. If it still fails, clear cache related to “chat.openai.com,” or switch to another browser/device to confirm whether it’s specific to your current setup. If you frequently switch accounts across multiple devices, you may also hit short-term sync delays—waiting briefly is often more effective than repeatedly clicking.
Message send failures, Network error, 429: reduce the chance of triggering limits
If ChatGPT shows Network error, fails to send, or returns 429 (too many requests), it’s usually due to unstable connectivity, requests being blocked by an intermediate device, or sending too many requests in a short time. Switch networks (for example, from Wi‑Fi to a mobile hotspot) to see if it’s a connection path issue, and copy your text locally before resending to avoid losing drafts. For sending pace, try combining questions and reducing rapid follow-ups; also split very long text into several parts, which can noticeably reduce the chance of ChatGPT disconnecting mid-request.
Still not working: reproduce with a minimal setup and submit support details
If ChatGPT keeps failing for you but the status page is normal and incognito mode doesn’t help, try a “minimal reproduction”: keep only one tab open, disable extensions, and test with a single short sentence. Record the error message, time of occurrence, browser version, and network environment, and note whether the console shows key signals like 403/401. Save screenshots and then submit them via the Help Center—this is much easier to diagnose than only reporting “ChatGPT doesn’t work.”
