How Do I Fix ChatGPT Messages Not Sending But Internet Works?

Issue type: AI access — ChatGPT text input accepted but messages fail to send or receive a response, despite working internet

SEO focus: If you are looking for chatgpt messages not sending but internet works, this guide starts with the fastest diagnosis, then moves to the exact fix that matches the symptom.

Short answer: When internet works but ChatGPT won’t send messages, the problem is almost never the network connection itself — it’s a broken browser session, a cached version of ChatGPT’s JavaScript that loaded incorrectly, or a browser extension blocking the API request. A hard refresh or incognito test resolves this in most cases without touching your account or cookies.

ChatGPT Messages Not Sending but Internet Works: Quick Diagnosis

First, establish exactly what “not sending” looks like in your case. There are two distinct failure modes that require different fixes:

The send button does nothing at all — clicking it or pressing Enter produces zero response, no spinner, no movement. This is almost always a JavaScript loading failure. ChatGPT’s interface relies on a JavaScript bundle that loads fresh from OpenAI’s servers. If a cached version of this bundle loaded incorrectly (common after a ChatGPT update), the send function silently breaks. A hard refresh that forces a full JavaScript reload fixes it.

The send button shows a loading spinner that never resolves — the message appears to send, the spinner starts, but no response arrives and it spins indefinitely. This is a session or API connection issue. The interface sent the request but the response stream never arrived or was blocked. A stale authentication token, a browser extension intercepting the API call, or a temporary server-side issue causes this pattern.

Before doing anything else, check status.openai.com. If OpenAI lists a current API or ChatGPT incident, no local fix will help until they resolve it on their end.

What to do first

1. Try a hard refresh immediately. Press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac). Unlike a regular F5 refresh, this bypasses the browser cache and forces the page to re-download all JavaScript and assets from scratch. If the send button was broken due to a stale cached script, it starts working immediately after this. Test by typing a message and pressing Enter.
2. Test in an Incognito or Private window. Press Ctrl + Shift + N (Chrome/Edge) or Ctrl + Shift + P (Firefox) to open a private window, then go to chat.openai.com and try sending a message. Incognito runs with no extensions and no stored session data. If it works there, a browser extension is blocking the request in your normal window.
3. If Incognito works, find the conflicting extension. In your normal browser window, click the Extensions icon (puzzle piece in Chrome/Edge) and disable all extensions. Reload chat.openai.com and test. If sending works now, re-enable extensions one at a time, reloading and testing after each, until it breaks — the last extension you enabled is the one causing the conflict. Common culprits: ad blockers (uBlock Origin, AdGuard), VPN extensions, and privacy tools that block certain API domains.
4. Clear the session cookies for OpenAI specifically — not your entire browser history. In Chrome: Settings > Privacy and security > Third-party cookies (or Site Settings) > See all site data > search openai > delete all entries for openai.com and chat.openai.com. In Firefox: Settings > Privacy & Security > Cookies and Site Data > Manage Data > search openai > Remove Selected. This forces a fresh login and new session token without affecting any other site.
5. Try a completely different browser. If Chrome has the issue, test in Edge, Firefox, or Brave. If one browser sends messages and another doesn’t, the problem is browser-specific (extension, profile, or setting in that browser) rather than account or network related.
6. Check if a browser or system-level VPN or proxy is active. Some VPNs route traffic through endpoints that OpenAI rate-limits or blocks. Disable the VPN temporarily and test. If messages send without the VPN, reconnect to a different VPN server or add chat.openai.com to your VPN’s split-tunnel exclusion list.

Common mistake

Clearing all browser history, cookies, and cached files across every site when only the OpenAI session is broken. This logs you out of every website, loses autofill data, and removes bookmarks stored in sync — all to fix a problem that requires clearing only the cookies for openai.com specifically. Target the fix: clear only the OpenAI site data using the Site Settings method described above. It’s faster, less disruptive, and solves the same problem.

Best next step

If messages still won’t send after clearing cookies, trying incognito, disabling extensions, and testing multiple browsers, try the ChatGPT mobile app on your phone (iOS or Android). The mobile app uses a separate authentication path and doesn’t share browser session data or extensions. If the mobile app sends messages without issue, the problem is isolated to your desktop browser environment — and a full browser reinstall (uninstall > manually delete the profile folder > reinstall fresh) is the cleanest resolution. If the mobile app also fails to send messages, the issue is account-level or network-level, and checking status.openai.com and waiting for OpenAI to resolve it is the appropriate next step.

Official reference: If the issue appears across devices or networks, check the official OpenAI Status page before reinstalling the app or changing account settings.

Quick Q&A

ChatGPT sends the first message fine but stops responding on the second or third message. What causes that?

That’s a session expiration issue. Your login token is valid enough to start a conversation but expires mid-session, causing subsequent requests to fail silently. Clear the OpenAI cookies using the method above to force a fresh authentication token, then log back in. If it keeps happening in the same session, check whether your browser’s cookie settings are set to clear cookies on close or after a short time period — that setting prevents ChatGPT from maintaining a persistent session.

The send button is greyed out and I can’t click it at all. Is that the same problem?

No — a greyed-out send button means ChatGPT is still processing a previous response or the text input hasn’t been detected correctly. If it’s greyed out on a fresh page with nothing in the chat, the JavaScript hasn’t initialized properly. Do a hard refresh (Ctrl + Shift + R) and wait 10–15 seconds for the full page to load before typing. If the send button is greyed out because you’re at a usage limit (free tier hourly limit), you’ll see a message in the interface indicating you need to wait or upgrade.

This started happening after my company installed new network monitoring software. Is that related?

Very likely. Corporate network monitoring tools, DLP (Data Loss Prevention) software, and SSL inspection proxies intercept HTTPS traffic and re-sign it with a corporate certificate. Some of these tools block requests to AI services by policy, or their SSL interception breaks ChatGPT’s WebSocket connection that’s used for response streaming. Check with your IT department whether ChatGPT is allowed on the corporate network, and whether the monitoring software has an exception list where chat.openai.com can be added.