ERR_EMPTY_RESPONSE and ERR_CONNECTION_RESET: When the Connection Closes With Nothing
ERR_EMPTY_RESPONSE means Chrome opened a connection and the other side closed it without sending a single byte — the page reads “didn't send any data”. ERR_CONNECTION_RESET means the connection was forcibly cut mid-way with a TCP reset. Both happen after the connection was established, so DNS and routing are fine. The usual causes are a protocol mismatch on the port, a firewall or filter that kills the connection, a proxy that drops it, or a server that rejects the client without explaining why.
- troubleshooting
- chrome
- proxy errors
- network
Table of contents
What each error means
| Error | Code | What the other side did | Typical cause |
|---|---|---|---|
ERR_EMPTY_RESPONSE | −324 | Closed cleanly without replying | Wrong protocol for the port, server dropping unwanted clients |
ERR_CONNECTION_RESET | −101 | Sent a TCP reset | Firewall, antivirus, DPI filter, overloaded server |
ERR_CONNECTION_CLOSED | −100 | Closed unexpectedly | Similar to reset, less abrupt |
ERR_CONNECTION_REFUSED | −102 | Nothing listening | Wrong port — before any connection existed |
Proxy-specific causes
- Protocol mismatch. Pointing an HTTP client at a SOCKS5 port — or the reverse — opens the TCP connection and then gets nothing useful back. Check that the scheme in your config matches the port you were given.
- `https://` proxy scheme on a plain HTTP proxy. The client starts a TLS handshake the proxy does not expect, and the proxy closes the connection.
- Idle connections cut by the proxy. Long-held keep-alive connections are closed after a period; the next request on that socket fails. Good clients retry on a new connection automatically.
- Exit went offline mid-request. Residential exits are real devices. A reset in the middle of a transfer is usually one of them disconnecting.
- Target silently rejecting the exit. Some servers close connections from networks they do not like rather than answering 403.
# Does the proxy answer at all, and in which protocol?
curl -v -x http://USERNAME:PASSWORD@PROXY_HOST:PROXY_PORT https://example.com -o /dev/null
curl -v -x socks5h://USERNAME:PASSWORD@PROXY_HOST:PROXY_PORT https://example.com -o /dev/nullFixes when you are not using a proxy on purpose
- 1Try another network. If mobile data works and Wi-Fi does not, the router, ISP filter or office firewall is resetting the connection.
- 2Pause antivirus web protection and VPN software. Both inspect traffic and are frequent sources of resets.
- 3Disable extensions in a private window test, then re-enable one by one.
- 4Check for a stale system proxy under Windows Settings → Network & internet → Proxy, or macOS Network → Details → Proxies.
- 5Reset the network stack on Windows with
netsh winsock resetandipconfig /flushdns, then reboot. - 6Clear the site's cookies. Oversized or corrupted cookies make some servers drop the request without answering.
If the error hits one site only and every network, the site is rejecting the request. That is often a bot filter closing connections it considers automated — a cleaner exit or a real browser changes the outcome where a retry does not.
HTTP and SOCKS5 on the same credentials
Residential from €1.20/GB and ISP from €1.80/IP. Each protocol has its own port in the dashboard, so a mismatch is easy to spot.
In scripts and scrapers
Treat an empty response or a reset as a transport failure: retry once on a new connection, and if it recurs, on a new exit. Libraries surface them differently — RemoteDisconnected or ConnectionResetError in Python, ECONNRESET in Node — but they are the same event. If resets cluster on one target and not others, reduce concurrency first; many servers reset connections from clients that open too many at once.
For the related case where the proxy is never reached at all, see ERR_PROXY_CONNECTION_FAILED.
Sources
Frequently asked questions
What does ERR_EMPTY_RESPONSE mean?
Chrome connected to the server or proxy, but the connection was closed before any data was sent back. It usually points to a protocol mismatch on the port, a server that silently drops certain clients, or security software interfering with the connection.
What causes ERR_CONNECTION_RESET?
The connection was forcibly closed with a TCP reset by something on the path: a firewall, antivirus web shield, network filter, overloaded server or a proxy exit going offline mid-request.
Can a proxy cause ERR_EMPTY_RESPONSE?
Yes. Using an HTTP proxy address on a SOCKS5 port, or the reverse, or using an https:// proxy scheme on a plain HTTP proxy, commonly produces an empty response.
How do I fix ERR_EMPTY_RESPONSE in Chrome?
Try a different network, disable VPN and antivirus web protection, test in a private window without extensions, check for a stale system proxy setting, clear the site's cookies and, on Windows, reset the network stack with netsh winsock reset.
What is the cURL equivalent of ERR_EMPTY_RESPONSE?
cURL exit code 52, Empty reply from server. It means the same thing: the connection opened and closed without a response.
The seamless team runs residential, ISP and datacenter proxy infrastructure and writes these guides from day-to-day operational experience.
Ready to try seamless proxies?
Residential, ISP and datacenter proxies with no data expiry.
Browse PlansKeep reading
ERR_PROXY_CONNECTION_FAILED and ERR_TUNNEL_CONNECTION_FAILED: What Each Means and How to Fix It
One error means the proxy never answered; the other means it answered and said no. Checking the host and port again only fixes the first one.
TroubleshootingcURL Proxy Errors Explained: Exit Codes 5, 7, 28, 35, 56 and 97
cURL is the fastest way to prove whether a proxy works — once you can read what it is telling you. Every exit code maps to one leg of the connection.
Troubleshooting502 Bad Gateway and 504 Gateway Timeout Through a Proxy: Who Failed, and How to Tell
Two or three gateways can sit between you and the page, and any of them can send a 502. The fix depends entirely on which one did.