ChatGPT Troubleshooting: Fixes for a Missing Conversation List, Messages Not Sending, and Page Errors

When you encounter a blank ChatGPT conversation list, endless loading after you type, or the message “Something went wrong,” in most cases it’s not that your “account is broken,” but rather an issue with the session, browser cache, extensions, or the network path. Below is a step-by-step ChatGPT troubleshooting process from easiest to hardest, aiming to locate the problem with the fewest actions.

First confirm whether it’s a server-side fluctuation: don’t rush to reinstall or change settings

The first step in ChatGPT troubleshooting is to determine whether it’s a brief official-side outage: if multiple devices at the same time can’t open it or can’t send messages, it’s very likely service congestion. You can switch networks or wait a few minutes and try again, to avoid repeatedly refreshing during peak times and triggering rate limits.

If only this device has the problem while other devices are normal, then you can basically narrow the direction down to the browser environment, login session, or local network.

Conversation list not showing / history empty: prioritize cache and extension conflicts

When the left-side conversation list doesn’t display, the page is blank, or it keeps loading, ChatGPT troubleshooting recommends first logging in once in an “incognito window” to verify. Incognito mode bypasses most cache and extension effects; if incognito works normally, the issue is usually with the cache, cookies, or plugins.

Then proceed in order: disable ad blockers, script managers, and privacy-related extensions; clear cookies and site data related to chat.openai.com; then log in again. In many “history disappeared” cases, it’s actually an expired session or corrupted site data, not that the content was deleted.

Messages not sending / endless loading: from session reset to checking your input

If sending fails, the spinner never ends, or you see “Network error,” ChatGPT troubleshooting can start with “log out → refresh → log back in,” then create a new chat to test. If it’s only abnormal in a specific chat, that chat’s context may be too long or temporarily stuck; switching to a new chat often restores things immediately.

Also check your input content: pasting an extremely long text in one go, or including unusual formatting (lots of tables/special symbols), can cause the request to fail. Send the content in segments, or first send a short sentence to verify the path is working, then gradually add back the original content.

Page errors / Failed to fetch: focus on the network and proxy path

When you see “Failed to fetch” or you’re repeatedly redirected to login, ChatGPT troubleshooting should focus on network path stability. Try switching to a mobile hotspot, and disable any potential network acceleration/proxy tools, then test again. In many cases the path is unstable, causing handshake failures or interrupted requests.

At the same time, check whether the system time is accurate (time drift can cause certificate validation errors), and switch DNS to a more stable public DNS before retrying. If a company/campus network has strict gateway policies, it may also block related requests; in that case, using another network is the best way to verify the cause.

If it’s still not resolved: how to collect information and reduce back-and-forth trial and error

If ChatGPT troubleshooting still doesn’t work after completing the steps above, it’s recommended to record three types of information: the exact error text, the scenario (login/loading the list/sending messages), and whether it still reproduces under “incognito + a different network.” If possible, check the console and failed network requests in the browser’s developer tools; you can usually tell whether it’s being blocked by an extension, a CORS failure, or a connection timeout.

Organizing this information before reporting or further self-checking will save more time than repeatedly clearing the cache, and it’s more likely to pinpoint the real root cause in one go.