If ChatGPT won’t open, keeps spinning, or shows an error, it’s usually due to your network, browser cache, rate limiting, or abnormal session data. The following ChatGPT troubleshooting checklist follows a “fast first, slow later” order, and can generally pinpoint common issues and restore normal use.
Start with three quick checks (time-saving)
When troubleshooting ChatGPT, first check whether there are server-side fluctuations: open status.openai.com to confirm whether there’s an outage or degradation. Next, log in once using an incognito window to avoid interference from extensions and old cache—this is the most common “instant fix.” Finally, switch networks (toggle between Wi‑Fi and mobile data); many “Network error” cases are actually due to an unstable connection.
Endless loading spinner, blank page, and conversation list not loading
For this type of issue, focus on browser data: clear the site cache and cookies and log in again, especially if you’ve kept the tab open for a long time. Then check ad blockers, script managers, and privacy/anti-tracking extensions—pause them all and test once. If it’s still blank, try switching to a different browser engine or disabling tools like “force HTTPS/proxy rewriting,” to prevent resources from being blocked.
Send failed, “Something went wrong,” and blank replies
When troubleshooting ChatGPT, if messages won’t send or you get a blank response, first shorten your input: ask in segments, reduce large blocks of pasted text, and avoid uploading multiple attachments at the same time. Then refresh the page and try again; if needed, start a new chat—older conversations can occasionally respond abnormally due to overly long context. If “Something went wrong” appears frequently, prioritize ruling out local packet loss and DNS resolution issues; you can temporarily switch to a public DNS to verify.
429 rate limiting, 403 blocking, and account anomaly prompts
If you hit 429, the troubleshooting conclusion is usually straightforward: too many requests or too many retries in a short time. Wait a while before sending again, and reduce continuous refreshes and simultaneous logins across multiple devices. A 403 is often related to your network egress, corporate gateway, or proxy rules—switch networks or disable proxies/plugins that rewrite traffic and test again. If you see an account anomaly prompt or are asked to re-verify repeatedly, first make sure your system time and time zone are correct, then log out, clear cookies, and re-verify to avoid old tokens repeatedly expiring.
Following the steps above for ChatGPT troubleshooting generally covers these high-frequency scenarios: not loading, send failures, blank replies, rate limiting, and blocking. If the problem reproduces consistently, it’s recommended to record the error message, how often it occurs, and the network environment you’re using, then compare with the status page and help center to pinpoint the cause faster.
