ChatGPT Troubleshooting Checklist: Request Failures, Blank Pages, and Upload Issues

If you encounter “Something went wrong,” a blank page, or files that won’t upload when using ChatGPT, it’s usually not some mysterious problem—it’s typically your browser cache, network path, or account status causing trouble. Below, we break down common ChatGPT issues by symptom and troubleshoot them step by step, aiming to restore usability with the fewest actions possible.

Start with three quick checks to pinpoint the cause: service, network, or account

First, check the OpenAI Status page. If ChatGPT itself is degraded or down, don’t keep refreshing and wasting effort. Second, switch networks (Wi‑Fi/mobile hotspot) and browsers (Chrome/Edge/Safari) to cross-check—this quickly tells you whether it’s a local environment issue or a network egress problem. Third, log in to ChatGPT in an incognito window: incognito bypasses extensions and old cache, making it ideal for a “control experiment.”

Recommended order for dealing with a blank page, endless loading spinner, or repeated login loops

The most common causes of a blank ChatGPT page are corrupted cache/site data or blocked scripts: first clear site data (only for chat.openai.com), then log in again. If it’s still abnormal, temporarily disable ad blockers, privacy protection tools, and script-management extensions, and change the browser setting “block third-party cookies” to allow them for the ChatGPT site.

If you’re redirected back to the login page immediately after logging in, it usually means session cookies aren’t being written or are being blocked by security software; switching to an incognito window or a clean browser profile often fixes it immediately. In corporate networks, an HTTPS-decrypting gateway may also be involved—try again on a personal network.

How to troubleshoot failed message sends, request errors, and frequent retries

When ChatGPT shows “request failed/network error,” don’t keep clicking Send: refreshing the page re-establishes the connection and often restores functionality. Next, check whether you have a proxy/VPN enabled—some nodes make WebSocket connections unstable; try switching nodes, changing protocols, or turning it off and testing again.

If failures only happen in a specific conversation, copy the last prompt into a new chat and resend, to rule out interruptions caused by overly long context or content triggering safety policies. Rapid, high-frequency sending can also trigger rate limits; the safest approach is to wait a few dozen seconds between messages and reduce extremely long text pasted in one go.

File upload failures, unreadable files, and permission-related issues

For ChatGPT file upload issues, check two things first: whether the file is too large and whether the format is common (PDF/PNG/JPG/TXT, etc., tend to be more reliable). Special characters in the filename, overly deep paths, or the file being in use by another program can also cause uploads to hang; rename the file using English letters and move/copy it to the desktop before uploading for a higher success rate.

If you see “unable to read/parse,” first export to a more universal format (e.g., regenerate a scanned PDF as a text-based PDF, or save a spreadsheet as CSV). If it still fails, try a different browser and network to avoid a locally blocked upload path; if the same file behaves the same across different environments, it’s more likely an issue with the file itself.

When contacting support, what information is most useful

If ChatGPT remains unusable for an extended period and you’ve already done the incognito window / network switch / disable extensions trio, prepare: the exact error message, the time window when it occurred, your browser version, whether you used a proxy, and whether 4xx/5xx responses appear in the console/network requests. The more specific the info, the faster the diagnosis—and it helps avoid back-and-forth follow-up questions.