“Internal server error” in ChatGPT means the failure is on OpenAI’s side, not yours. The message is generic by design — the server hit a problem it could not describe.
Which means the first thing to do is check whether it is only you.
Checked August 2026. Applies to ChatGPT on the web, desktop and mobile.
1. Check the status page
Thirty seconds, and it settles whether anything you do next is worth doing.
Open status.openai.com. If an incident is listed, nothing on your machine is wrong — subscribe to updates and come back later.
Also worth checking: Downdetector, which often shows a spike before the official status page updates.
2. Regenerate, or start a new chat
- Select the regenerate option on the failed response.
- If it fails again, start a new conversation and paste the prompt.
A very long conversation is a common trigger. Each message resends the accumulated context, and eventually the request becomes too large or too slow. If a thread starts failing consistently while new ones work, that thread has simply grown too long — carry the important part into a fresh one.
3. Clear cookies for the site
An expired session token produces errors that look server-side because, technically, they are.
- With ChatGPT open, select the padlock or tune icon in the address bar.
- Choose Cookies and site data → Manage on-device site data.
- Delete the entries for the site, then reload and sign in again.
This clears only that site, so you stay signed in everywhere else.
4. Rule out your extensions
Open a private window — extensions are disabled there by default. If ChatGPT works, an extension is interfering.
The usual suspects are ad blockers, script blockers, VPN extensions and, ironically, ChatGPT-related extensions. Turn them off one at a time to find it. See choosing a ChatGPT extension.
5. Check the network path
- Disconnect any VPN. Shared VPN exit addresses get rate-limited, and some are blocked outright.
- Try mobile data with wi-fi off. If it works there, the problem is your network — a filtered DNS or a corporate proxy.
- Try a different DNS, such as 1.1.1.1 or 8.8.8.8. See how to change DNS servers.
6. Try another client
The web app, the desktop app and the mobile app are separate. If one fails, try another — that tells you whether the problem is the client or the account.
7. Check the clock
A system clock that is wrong by more than a few minutes breaks the certificate validation behind HTTPS, which surfaces as connection and server errors.
Settings → Time & language → Date & time → Sync now.
Related errors and what they mean
| Message | Meaning |
|---|---|
| Internal server error | Server-side fault. Retry, then wait. |
| Too many requests / rate limited | You hit a usage limit. Wait for the window to reset. |
| Conversation not found | Session or sync problem. Reload and sign in again. |
| Network error mid-answer | Usually a long response timing out. Ask for a shorter one, or ask it to continue. |
| Something went wrong | Generic. Same steps as above. |
| At capacity | Demand exceeds available capacity. Only waiting helps. |
What does not help
Advice that circulates for this error and does nothing: reinstalling your browser, flushing your DNS cache, disabling your firewall, or running a “PC repair” tool. This is a server-side error. Check the status page, retry, start a new chat, and clear the site cookies — that covers essentially every case you can actually fix.
Frequently asked questions
Is it my fault?
Usually not. Check the status page first. The client-side causes worth ruling out are a stale session, an extension, and a very long conversation.
Why does one conversation keep failing?
It has grown too long. Every message resends the whole thread, and past a point the request becomes too large. Start a new one and carry over what matters.
Does a paid plan avoid this?
Paid tiers get priority during heavy demand, so “at capacity” is rarer. A genuine server fault affects everyone.
Should I clear all my browser data?
No — clear cookies for that site only. Clearing everything signs you out of every site for no additional benefit.
Could my VPN be causing it?
Frequently. Shared exit addresses get rate-limited, and some ranges are blocked. Disconnect and retry before anything else.
