Why Is ChatGPT Not Working? 10 Common Problems and How to Fix Them
chatgpt not working? Step-by-step fixes for errors, device-specific solutions, status checks, and when to contact support.
Oluwaseun Odeniyi/6 Nov 2026/9 min read

When ChatGPT not working is the problem, the fix depends on the symptom, not on how many things you try.
A stalled chatbot can derail an afternoon because plenty of people now use AI much like email. When it breaks, you need a fast, useful answer, not 30 random tips.
This guide is organised by symptom. First work out whether you're dealing with a service, connection, browser or account issue. Then use the fix that fits. No fluff. Just the stuff.
Is ChatGPT down right now?
Check the status page before changing a single setting. OpenAI's status page is at status.openai.com. If ChatGPT down is the actual problem, nothing you change locally will fix it.
Read the page carefully:
- Look at the named feature. A snapshot of the dashboard from November 6, 2026 said "We're currently experiencing issues" and listed "ChatGPT Work and Dots Errors" as Monitoring (OpenAI Status). That points to a partial issue, not "everything is off."
- "Monitoring" does not mean "fixed." The linked incident moved from investigating, to identified elevated errors, to mitigation (OpenAI incident). Check the updates, not just the headline.
- A green dashboard does not settle it. OpenAI reports availability in aggregate, so your model, tier or feature can still fail while the totals look fine. The page showed 99.70% ChatGPT uptime for August–November 2026 (OpenAI Status). That's a reporting-period average, not a guarantee for your session.
If the incident matches what is failing, wait and follow the updates. If it doesn't, move on.
Why is ChatGPT not working?
"Not working" is a symptom category, not a diagnosis. OpenAI lists network configuration, browser extensions and temporary server problems as possible causes. Its error guide also gives different messages different meanings (OpenAI Help Center). Think of it like a car that won't start: a dead battery, no fuel and a flat tyre can all look like "it won't go."
Here is the quick diagnostic table for ChatGPT error messages:
What you see | Likely meaning | First test
"Something went wrong" | Temporary server issue or local setup | Check status, then isolate your local setup
"A network error occurred" / WebSocket error | Your device can't hold a reliable connection | Compare networks; turn off personal VPN/proxy
"There was a problem preparing your chat" | Usually an extension or URL blocker | Disable blockers or try a clean browser
"There was an error generating a response" | ChatGPT failed to produce the answer | Regenerate
"Unusual Activity Detected" | Traffic looks automated or unusual | Check VPN/proxy and account security
"Wrong authentication method" | Sign-in method isn't enabled for the account | Check how you originally signed up
The honest truth: a generic error will not tell you which side is at fault. The table narrows the search. It cannot guarantee a diagnosis.
One testing habit helps. I've personally used Fathom and Granola the most for meeting notes, and the lesson from comparing tools carries over: change one variable at a time while keeping the scenario the same. Use the same prompt and account, then change only the browser, network or device. That is how you find the cause.
How do I fix ChatGPT when it won't load?
A blank screen, frozen page or endless spinner means the interface itself is not loading. That differs from a visible chat that is slow to answer. Start here:
- Hard-refresh with Cmd/Ctrl + Shift + R, or force-reload the desktop app.
- Sign out and back in.
- Clear ChatGPT site data and cookies. Clear this site only, not your entire browser.
- Disable extensions and content blockers, or try a private window, fresh profile or another browser.
- Isolate the connection. Turn off a personal VPN, secure DNS or security filter, then try another network or device.
If you're seeing ChatGPT not working on Chrome, clear Chrome's cache and cookies for the site, then disable extensions, especially site blockers and privacy extensions. Test in an Incognito window or a fresh Chrome profile. If it works there, the issue is in your Chrome setup. Turn extensions back on one at a time to find the culprit.
On a work network, OpenAI specifically recommends comparing company Wi-Fi with a cellular hotspot (OpenAI network guidance). If it works on cellular but not office Wi-Fi, that points to the network. It won't tell you which firewall or DNS rule is responsible, so pass that part to IT. OpenAI's guidance covers allowlisting domains such as *.chatgpt.com and *.oaistatic.com, and warns that a reachable homepage does not prove every resource is reachable.
Why is ChatGPT not responding to my prompts?
Separate a failed answer from a failed page.
- "There was an error generating a response" may be a one-off. Hit Regenerate before doing anything more disruptive.
- Answer started but stalled? Wait 30–60 seconds, then choose Stop generating and Regenerate (OpenAI Help Center). That is a troubleshooting window, not a promised completion time.
- One long conversation misbehaving? Start a new chat. That tests a different boundary than changing browser or network.
- Failing repeatedly? Restart the browser or device, turn off VPN/proxy or security filters, then try another browser, network or device.
For chatgpt slow responses, rather than silence, OpenAI suggests switching models and starting a new chat to see whether the problem is model-specific or account-wide (OpenAI Help Center). It also lists peak hours, company policies, VPNs and weaker mobile bandwidth as contributors. Slow output alone does not prove the servers are overloaded.
Why does ChatGPT freeze or keep loading?
There are two main branches, with different fixes:
- Page empty or unresponsive: use the won't-load steps above. Waiting is not the only remedy OpenAI offers.
- Response hangs mid-way: wait 30–60 seconds, stop, regenerate, then use a new chat if the old one is long.
There is also a sneakier cause: a connection that fails after the page opens. Some features use secure WebSocket connections, and OpenAI tells network admins to allow WebSocket traffic over TCP port 443. TLS inspection, SSL decryption and proxies can block or close that handshake. Ordinary web pages loading does not test that path, so a work network can show you the site while still stalling your chats (OpenAI network guidance).
If it is simply sluggish, disable script- or ad-blocking extensions and close unneeded tabs and programs. That can reduce local resource pressure. It does not mean every freeze is a memory problem.
Why isn't ChatGPT working on my phone?
For ChatGPT not working on iPhone or Android, start with the basics:
- Check the publisher. The iOS listing names OpenAI OpCo, LLC as developer; the Android listing names OpenAI (OpenAI Help Center). The app name alone is not enough.
- Android sign-in fails but the app opens? The app uses Chrome or Brave to complete login. If neither is installed or set as default, sign-in can fail. Try Settings > Apps > Default apps > Browser app > Chrome. Labels vary by Android version (OpenAI Help Center).
- iPhone "Unusual activity"? OpenAI lists signing out and in, updating or reinstalling the app, and turning off a VPN. That guidance fits that symptom, not every issue.
- Connection or app? Compare Wi-Fi and cellular, then another device if you have one. Switching between them is a quick test for chatgpt connection issues.
Note your app version before escalating. On iOS, it is in your profile's Settings area. On Android, open your profile, then About.
Can browser extensions or VPNs cause ChatGPT problems?
Yes, but match the fix to the symptom.
- Extensions and blockers: "There was a problem preparing your chat" usually means an extension or URL blocker is interfering. Script and ad blockers can also slow things down.
- VPNs and proxies: OpenAI recommends turning them off for network errors. For "Unusual Activity," VPN traffic may route through flagged IP addresses.
Test first, don't purge everything. If a private window works, you have narrowed the issue to your browser environment. You have not yet identified the extension causing it. Disable them one at a time.
You will also see advice to turn on a VPN for a Cloudflare-style Error 1020 access-denied message (Tech.co). That is a different diagnosis from OpenAI's advice. "Always use a VPN" and "the VPN is always the culprit" are both too broad.
On a managed work network, toggling a personal VPN is a fair test. Changing enterprise filtering is an admin job. The fix should target the specific mechanism, not strip out security controls.
What should I do if ChatGPT stops generating images?
First, work out which stage failed:
- Never finishes: wait 30–60 seconds, stop, regenerate. That is general response troubleshooting, not an image-specific service target.
- Error shown, or page breaks: use the blank-page or network-error steps rather than rewriting your prompt again and again.
- Image exists but won't download: note the exact "Download failed" or "File Not Found" message. They are separate categories in OpenAI's guide.
Check the status history too. Image generation has appeared there as an affected service on its own (OpenAI Status history), so working text chat does not rule out an image incident.
I can't give you a reliable daily image quota or reset time here. Those details are not something I can verify, so check your plan's limits in the app.
How do I fix ChatGPT login problems?
For ChatGPT login problems, the issue is often the account or sign-in method, not the password.
- Use the account email. It may differ from the address that receives invoices.
- Match the sign-in method. "Wrong authentication method" can mean that method is not enabled for the account. Try a clean incognito attempt.
- Apple Hide My Email: if you registered with Continue with Apple, your account may sit under an
@privaterelay.appleid.comaddress. Use Continue with Apple with the same Apple account. Repeated password resets will not fix it. - Browser verification loops: pause your VPN/proxy, allow cookies (including third-party) and JavaScript for
chatgpt.com,openai.comandauth.openai.com, then try another browser or network. Keep that scope limited to those domains. - Suspicious-login lockout: wait up to one hour before trying again. Repeated failures can trigger temporary restrictions (OpenAI Help Center).
- Business/Enterprise SSO: ask your administrator to check the invite address, provisioning and identity-provider settings.
- Deactivated or suspended: check OpenAI's account emails and contact support if it looks mistaken. Clearing your cache will not help.
When should I contact OpenAI support?
Contact support when the problem persists across browsers, devices and networks. Before that, you are still in the self-fix stage. OpenAI's own guidance is to gather evidence first, not wait a fixed number of hours.
Build a support packet:
- The exact message and what you did before it appeared
- Timestamps and console errors
- A HAR file
- The model you used and the conversation URL or ID
- Your app version, if on mobile
- What you've already tried
To reach support, open the chat bubble at the bottom-right of help.openai.com. A new chat starts with a virtual assistant. A disputed suspension goes to OpenAI; an SSO provisioning issue starts with your IT admin.
One more thing: if you paste other people's messages or meeting transcripts into ChatGPT to debug something, consent and notice are your responsibility, not the tool's. Once the problem is fixed, keep an eye on how you use it. Set sensible controls first, then keep watching.
Quick checklist, fixes to try right now
Try these in order:
- Refresh the page
- Open a new chat
- Sign out and sign in
- Restart your device
- Try an incognito/private window
- Switch browser or device
- Toggle Wi-Fi/cellular
- Turn off VPN/proxy
- Disable adblocker/extensions
- Clear cache and cookies
How long to wait. For a hung answer, give it 30–60 seconds, then stop and regenerate. A couple of quick retries are reasonable for a one-off error. If the same error returns after you have changed something real, such as browser, network or device, stop retrying. Either the status page shows a matching incident, in which case wait for updates, or you have enough evidence for support. For login lockouts, wait up to an hour.
Hammering Regenerate twenty times is the wrong move. It tests nothing new. It does not have to be this way: change one thing, check the result, then move on.
Still stuck and need work done today? Keep a few other free AI writing assistants you can try as a backup.