If ChatGPT won’t open, keeps spinning, fails to send, or shows “Something went wrong,” don’t rush to refresh repeatedly. Most issues can be pinpointed with a stable ChatGPT troubleshooting sequence: first confirm whether there’s server-side turbulence, then check the browser session, network, and account status. Follow the path below from easiest to hardest.
First determine whether it’s a server outage or a local environment issue
The first step in ChatGPT troubleshooting is to see whether “everyone is down.” Open the official OpenAI status page (status.openai.com) to confirm whether ChatGPT-related components have an Incident or are Degraded. If the status page looks normal, continue troubleshooting locally: with the same account, switching devices or switching browsers to see whether it works is the fastest dividing line.
Blank page or endless loading: most likely cache, cookies, or extension blocking
If it’s stuck loading or shows a blank page, try opening it in an incognito/private window first—this can directly rule out most extension-related issues. If it still doesn’t work, clear this site’s cookies and cache, and make sure the browser allows third-party cookies (some login flows rely on them). Ad blockers, script blockers, and content filtering by corporate gateways also often cause loading failures—these are the most common “hidden culprits” in ChatGPT troubleshooting.
Messages won’t send / network errors: stabilize the network first, then reduce concurrency
If you see “Network error,” “Something went wrong,” or the send spinner keeps going, first switch networks (toggle between Wi‑Fi and a mobile hotspot), then disable the VPN/proxy or change nodes—often the route is unstable. Next, avoid sending frequently from multiple tabs at the same time; high-frequency requests in a short period may trigger “Too many requests.” The key points for this kind of ChatGPT troubleshooting are: make the connection stable first, then slow down the request cadence.
Session expired or repeated logins: address clock settings, cookies, and account risk-control prompts
If you’re prompted with “Your session has expired” or keep getting bounced back to the login page, it’s usually because cookies can’t be written or the system time is inaccurate, causing signature validation to fail. Set the device time to “automatic,” and disable privacy-related plugins that may isolate cookies. If you see security prompts like “Access denied” or “suspicious activity,” stop frequently switching IPs and devices; keep things stable for a while before logging in again—an easily overlooked step in ChatGPT troubleshooting.
Still not resolved: use minimal reproduction info to pinpoint the issue quickly
Once you’ve confirmed it’s not a server-side outage, it’s recommended to record the exact error message, the steps to reproduce, browser version, network environment (corporate network/home network/mobile data), and whether a proxy is used, and keep screenshots. Then, with the same account, do a “minimal reproduction” once in another browser—the result often points directly to the root cause. Bringing this information when you submit feedback is more likely to make ChatGPT troubleshooting effective in one pass than simply saying “it doesn’t work.”
