Most issues come from outages, logins, networks, or browser quirks—start with a status check, a fresh sign-in, and a clean cache.
If the chat window spins, returns a blank reply, or throws a vague error, you’re not alone. Break the problem into four buckets: service status, account access, device or browser setup, and network limits. Work through the fast checks first, then move to deeper fixes. This guide walks you step-by-step, with plain actions that tend to solve the most common blockers.
Fast Checks Before You Try Anything Else
These take a minute or two and solve many hiccups. Run through them in order and retest after each step.
| Symptom | Likely Cause | Quick Fix |
|---|---|---|
| “Something went wrong.” or a blank screen | Temporary service blip or cached script | Refresh, open a new chat, then try an incognito window |
| Endless loading spinner | Stuck session or heavy extension | Log out and back in; disable ad-blockers/privacy tools for a test |
| “At capacity” or rate errors | Traffic spike or request burst | Wait a few minutes; reduce rapid submits; shorten messages |
| Can’t sign in on phone | Default browser not supported for login | Set Chrome or another supported browser as default, then retry |
| Mobile app shows 401 or date/time warning | Clock drift or token mismatch | Set automatic date/time, restart the app, try Wi-Fi then data |
| Works on one network, fails on another | Restricted DNS, VPN, or firewall | Turn off VPN/secure DNS; try a different Wi-Fi or mobile data |
Check The Service First
Outages and partial incidents do happen. If replies fail across devices or accounts, the platform may be in a degraded state. Open the official system page in a separate tab and scan the Chat interface and related components. If an incident is active, you’ll save time by pausing deeper troubleshooting and trying again once the status returns to green. Link included below in the resources section of this guide.
Sign-In And Account Fixes That Pay Off
Many “it worked yesterday” problems trace back to sessions. Tokens expire, cookies collide, and third-party logins add another hop. A clean sign-in sequence clears a lot of sludge.
Do A Clean Session
- Fully log out on web and mobile.
- Close all tabs tied to the chat interface.
- Open a private/incognito window and sign in there first.
- If you use Google, Apple, or Microsoft to authenticate, confirm you’re selecting the same identity as before.
Reset Your Browser Footprint
- Clear cookies and cached files for the site only, not your whole browser, to avoid wiping unrelated logins.
- Disable content blockers and privacy extensions for a short test. If the chat loads with blockers off, add an allow-list rule.
- Try a second browser. If it works there, the first browser likely has a stale extension rule or an old cache.
Network Causes: DNS, VPNs, And Firewalls
Security layers are great until they clip the connection. Rate shapers, DNS filters, and strict firewalls can break sign-in or streaming replies.
Quick Network Tests
- Turn off VPN and secure DNS tools, then retry a prompt.
- Switch from office Wi-Fi to mobile data for a minute. If it works on mobile, your work network is likely filtering traffic.
- Flush DNS and restart your router if home internet feels stale.
- On corporate networks, ask IT if the domains for the chat interface and auth endpoints are allowed.
Device And App Quirks You Can Fix Fast
Small setup details can block the login flow on phones or tablets. A default browser change or clock tweak often clears it.
Android/iOS Tips
- Set a supported browser as default for the mobile app’s login handoff.
- Enable automatic date and time. Token checks fail when the clock drifts.
- Update to the latest app build. Old versions can hang during auth.
Desktop Tips
- Update your browser to the latest stable release.
- Turn off hardware acceleration if video drivers are buggy.
- Create a fresh browser profile for testing. If that profile works, migrate your bookmarks and extensions slowly.
Common Error Messages And What They Mean
Messages vary, yet they point to a small set of roots. Map the text to a next step and you’ll move faster.
| Error Text | What It Usually Means | What To Do Next |
|---|---|---|
| “Something went wrong.” | General failure: temporary outage or local cache conflict | Refresh, new chat, then incognito; if still broken, check system status |
| “At capacity right now.” | Traffic spike; service is throttling new sessions | Wait 5–15 minutes; try a lighter prompt; retry during a low-traffic window |
| “Network error” mid-reply | Connection dropped or proxy cut the stream | Switch networks or turn off VPN; shorten the message and resend |
| 401/403 on mobile login | Auth token mismatch or clock skew | Set automatic time, restart the app, set a supported default browser |
| Rate limit exceeded | Too many requests or very large messages in a short window | Slow down, reduce message size, wait for the window to reset |
Why Chatgpt Might Not Work Today: Quick Wins
When replies stall, aim for small wins that restore a clean state. Start with an incognito sign-in, then strip away blockers until the chat loads. If the issue tracks across devices and networks, the platform may be throttled. If it works on one setup but not another, you’ve found your culprit: browser add-ons, cached assets, or a security layer.
Fix Rate Limits And Heavy Prompts
Short bursts of many messages can trigger a limit. Long messages can do the same. Keep the pace steady and trim the prompt when you can. If you paste long documents, split them into parts. Wait a minute after a batch to clear the rolling window. When you see a rate message, avoid rapid retries; they extend the lockout window.
Clear Cache The Smart Way
Wiping the full browser often causes more pain than it solves. Target the site data instead. Remove cookies and cached files only for the chat domain, then reload. If you use a password manager, make sure it doesn’t inject helper scripts into the chat page. Some managers offer a site ignore list, which helps during testing.
Trim Extensions And Test
Extensions rewrite pages on the fly. Privacy shields, script blockers, and aggressive ad filters can break the streaming reply and even the login screen. Create a quick test by turning them off for a single session. If the site loads cleanly, bring back tools one by one until the problem returns. Keep the allow-list rule and move on.
Mobile App Playbook
When the app loops on login, the handoff through your default browser is often the snag. Set a supported browser as default, then retry. If you still get an error, delete and reinstall the app, set automatic time, and test both Wi-Fi and mobile data. Keep your OS current. Old WebView builds cause strange rendering glitches that look like service errors.
Browser And Platform Fit
Stick with a current, mainstream browser. Nightly builds and heavily tweaked forks can break WebAuth without warning. On desktop, a second profile gives you a clean slate without uninstalling anything. On mobile, clear the app’s cache before a reinstall to force a fresh token and a clean webview.
When It’s Clearly A Service Problem
If multiple users around you report the same symptoms at the same time, it’s likely an upstream issue. During an incident window, retries help less than patience. Keep a small test prompt handy and try every few minutes. Once the system status page shows a fix, fully sign out, close your tabs, and start a new session.
Two Links You’ll Use Again
Check the official system status when replies stall, and keep the help article on troubleshooting error messages bookmarked. Both save time during a rough patch.
Make Your Messages Easier To Process
Large, dense prompts take longer to stream and fail more often on weak connections. Keep them lean. Use clear headings in your message, add short lists, and trim screenshots or pasted logs unless they are needed. When you need to share long content, split it into parts with labels and send one piece at a time.
Privacy And Security Layers That Interfere
DNS filters that block tracking domains sometimes overreach and clip needed endpoints. The same goes for company proxies with deep packet inspection. During testing, move to a simpler path: a home connection or mobile data, VPN off, secure DNS off. If the chat works there, capture that detail for your IT ticket so they can allow the domains cleanly.
Account Safety Checks
Unrecognized activity warnings, unexpected logouts, or frequent 2FA prompts may signal a security event. Reset your password, review active sessions, and lock down third-party logins. If something looks off, change the password on the identity provider as well and revoke old tokens. Keep 2FA on for long-term peace of mind.
When Nothing Works: A Clean Rebuild
If you’ve tried status checks, clean sessions, network swaps, and extension trims, a more complete reset helps:
- Create a new browser profile with no add-ons.
- Sign in through that profile only.
- Test on a second device and a second network.
- If both fresh paths fail, bookmark the status page and pause. It points to an upstream fix window.
Pro Tips That Save Time
- Keep one short “canary” prompt, such as “Say hello.” If that fails, the issue is general, not prompt-specific.
- When the site works in private mode but not normal mode, cookies or extensions are at fault.
- If big uploads stall, send a compact summary and attach the file after the session stabilizes.
- Set a reminder to update your browsers and apps monthly. Fresh builds avoid edge bugs.
What To Tell IT Or Support
Clear notes speed the fix. Include the exact error text, time window, device and OS, browser and version, network used, and steps tried. Mention whether it worked on another network or device. Screenshots of the error banner and the console log (if you’re comfortable grabbing it) help a lot.
When You Rely On It For Work
Have a fallback plan. Keep a second browser ready, note the mobile app steps above, and keep the two links in this guide within reach. Most outages are short. With a clean setup and a calm retry rhythm, you’ll be back on track without burning an hour chasing ghosts.