When using ChatGPT, if you encounter “Something went wrong,” 403/429, or messages won’t send, it’s usually not because you did something wrong—it’s more often caused by your network, browser cache, or rate limiting. Below, we’ll troubleshoot the most common ChatGPT issues by error type, aiming to restore normal conversation via the shortest path possible.
Start with three general checks—most problems go away
First, check whether the ChatGPT service status page shows an outage; if the platform is unstable, refreshing will only make it laggier. Second, switch networks or disable your proxy/accelerator and try again—many “Network error” cases are actually due to an unstable or blocked connection. Third, log in to ChatGPT in an incognito window to temporarily bypass conflicts caused by extensions, cache, and abnormal cookies.
403/401: How to fix an expired login session or access being denied
A 401 error in ChatGPT is most commonly due to an expired login session: sign out and sign back in, and if needed, clear site data (cookies and cache) before entering again. A 403 typically means the request was denied; common causes include your network egress, browser extension blocking, or security policy triggers. First disable ad blockers, script managers, and privacy-protection extensions, then test with a mainstream browser. If your company or campus network has gateway filtering, switching to a mobile hotspot often immediately verifies the root cause.
429 / “Too many requests”: Don’t keep hammering refresh when you’re rate-limited
A 429 error in ChatGPT indicates too many requests in a short time or resource contention; repeatedly clicking Send will only prolong recovery. Pause for a few minutes and try again, and reduce high-frequency retries. Splitting a long question into two or three messages is more stable than stuffing an ultra-long context in one go. If you’re using ChatGPT on multiple devices at the same time, close extra pages to avoid triggering rate limits via concurrency.
500/502/503 and “Something went wrong”: Service instability and browser-side checks
500/502/503 are mostly server-side fluctuations or routing/link errors; prioritize waiting and refreshing the page rather than repeatedly logging in again. If only your machine errors out, focus on the browser: clear cache, disable extensions, update the browser version, and try again. If the message gets stuck after you send it, copy the text from the input box locally, refresh, then paste and send again to avoid losing content.
Session issues: Chats won’t open, “not found” prompts, or output interruptions
If ChatGPT chats won’t open or you see “Conversation not found,” it’s often because page cache and session sync are out of sync; if refreshing doesn’t work, sign out and back in, or open the same chat in an incognito window. When output is interrupted, don’t immediately resend the same large block—first ask ChatGPT to continue from the previous sentence, or request “continue from point X,” reducing the one-time generation load. If it keeps happening, record a screenshot of the error and the steps to reproduce it, then submit it via the official help entry for faster handling.
