How to Fix 'Network Error. Please try again' in Claude

How to Resolve "Network Error. Please try again" in Claude

When Claude suddenly stops generating mid-sentence and displays a red banner saying "Network Error. Please try again," it indicates that the active connection between your browser and Anthropic's servers has dropped. Because Claude streams responses in real-time using continuous connections, even a momentary packet drop can break the session and force an error.

Use these structured steps to diagnose the connection failure and prevent it from interrupting your workflows.

1. Verify WebSocket and Port Permissions Claude.ai relies on WebSockets (wss://) to stream real-time text. If your network blocks persistent connections, Claude will throw network errors shortly after starting a generation.

1. Test your WebSocket connection: Open a WebSocket testing tool online to ensure your browser and network allow persistent connections.
2. Disable security software: Aggressive firewalls, antivirus suites, or parental control software can flag long-lived WebSocket connections as suspicious and terminate them. Temporarily pause them to test.
3. Bypass corporate proxies: If you are on an enterprise network, IT departments often block non-standard ports or kill idle connections. Switch to a guest network or a personal mobile hotspot to see if the error clears.

2. Turn Off VPNs and Custom DNS Virtual Private Networks (VPNs) and secure DNS configurations (like DNS over HTTPS) often drop active streams when they perform automated IP switching or route optimization.

1. Disconnect your VPN: Turn off your VPN completely. Many VPN nodes are shared by thousands of users, triggering Cloudflare rate-limiting on Anthropic's edge nodes, which looks like a network drop.
2. Reset to Default DNS: If you are using custom DNS servers (e.g., custom Pi-holes or privacy DNS), switch your computer's network adapter settings to use automatic DNS or public DNS (such as Google's 8.8.8.8 or Cloudflare's 1.1.1.1).

3. Clear Local Browser State and Site Data Corrupted service workers or cached scripts can interfere with how your browser handles the streaming data chunks sent by Claude.

1. Open your browser's Developer Tools (F12 or Ctrl+Shift+I / Cmd+Opt+I).
2. Navigate to the Application or Storage tab.
3. Select Clear Site Data or navigate to Cookies and Site Data and delete everything under claude.ai.
4. Close the tab, open a fresh window, sign back in, and try the prompt again.

4. Reduce Your Context Window Extremely long conversations or heavy document uploads require a massive amount of processing time before Claude can even begin sending the first packet. If this delay exceeds your browser's or network gateway's timeout limit (usually 30 to 60 seconds), the connection is terminated prematurely.

1. Copy your last prompt.
2. Click "New Chat" to open a completely fresh session.
3. Paste the prompt without attaching large files or referencing massive past threads. If it works, your previous chat was triggering a gateway timeout error.

When to Escalate If you have verified that your network fully supports WebSockets, disabled all extensions, and still get network errors on every single prompt (even in fresh chats), the issue may be a localized regional outage on Anthropic's content delivery network (CDN). Check the official status page (status.anthropic.com). If no active outage is declared, reach out to Anthropic Support with your browser console logs (open F12, go to the Console tab, and take a screenshot of any red error messages).