Error reference Browser & network

How to fix ERR_EMPTY_RESPONSE

ERR_EMPTY_RESPONSE means the connection worked, your request went out, and the server hung up without sending a single byte back. Sometimes that's a crashing server or a stale keep-alive socket — but for scrapers it's frequently a silent block aimed at your IP range. Here's how to tell the difference, and how to fix both cases for good.

Try clean residential routes All error codes

ERR_EMPTY_RESPONSE

What ERR_EMPTY_RESPONSE means

ERR_EMPTY_RESPONSE (Chrome network error -324) means the TCP connection succeeded, the browser sent its request, and the server closed the connection without returning a single byte — no status line, no headers, nothing. It differs from ERR_CONNECTION_RESET, where the connection is torn down abruptly; an empty response is a clean close with zero data sent.

On the server side, the classic causes are a crashing worker process, a misconfigured virtual host with nothing to serve for that hostname, or a keep-alive connection your client reused after the server had already closed it. Local software — antivirus web filters, misbehaving browser extensions — can also swallow responses before they reach the page.

For scraping and automation traffic there's a more pointed explanation: many anti-bot layers respond to requests from flagged IP ranges by closing the connection instead of answering. Silence is cheaper than a 403 and gives your client nothing to fingerprint — so a consistent ERR_EMPTY_RESPONSE from one specific site, while everything else loads fine, is often a block rather than a bug.

ERR_EMPTY_RESPONSE

Fix ERR_EMPTY_RESPONSE step by step

Start by separating transient hiccups from deliberate drops — the first two steps settle that — then work through connection reuse, request shape, and local interference.

Retry the request once. One-off empty responses are frequently a reused keep-alive socket the server had already closed, and a fresh connection succeeds.
Load the same URL from a different network or without the proxy. If it works there but not from your usual IP or pool, the site is dropping connections from your IP range.
Disable connection reuse in your HTTP client (send Connection: close or turn off session pooling) and see if the errors stop — stale pooled sockets are the top non-block cause.
Send complete, realistic headers: User-Agent, Accept, Accept-Language, Accept-Encoding. Some servers close on requests that look like bare bots.
Test in an incognito window with extensions disabled, and clear the browser cache — a corrupted cache entry or an interfering extension can produce empty loads.
Turn off antivirus HTTPS filtering temporarily; several products intercept responses and occasionally return nothing at all.
Slow your request rate. Some sites use connection drops as a soft rate limit before escalating to hard blocks.
If it's your own server, check error logs for crashing workers and confirm the virtual host actually has a handler for that hostname and path.

ERR_EMPTY_RESPONSE

IP reputation: why targets answer some IPs and drop others

For scraping operators, the decisive factor behind ERR_EMPTY_RESPONSE is usually where you're connecting from. Datacenter IP ranges are well cataloged, and sites that don't want automated traffic often drop those connections wordlessly. The same request from a residential or mobile IP typically gets a normal response, because at the network level it looks like an ordinary subscriber connection.

The second proxy-specific trigger is rotation interacting with connection reuse: if your client pools connections while your proxy rotates exits, you can end up sending requests down tunnels tied to exits that have moved on. Pair rotation with fresh connections, or pin a sticky session for flows that need one stable IP — our tool guides under /integration/ show both patterns for Scrapy, Playwright, and Puppeteer.

Move flagged traffic to residential IPs

If a target consistently returns empty responses to your datacenter or cloud IPs, route it through residential exits. ProxyOmega's Budget Unlimited (/plan-unlimited/) draws on a 1.5M+ residential pool with country targeting, and Mobile (/plan-mobile/) provides real 4G/5G carrier IPs for the strictest targets.

Match session behavior to the site

Multi-step flows — login, add to cart, paginate — break when each request leaves from a new IP, and some sites drop mid-session IP changes without a word.

Pin an exit by adding a sticky session ID to your username (for example -session-checkout7, held for up to 24 hours) so the whole flow shares one identity.

Retry on a fresh exit, not the same one

When an exit IP has been burned for a specific site, retrying through it just reproduces the drop. Change the session ID on retry so the request leaves through a different IP, and treat repeated empty responses from one exit as a signal to rotate rather than hammer.

ERR_EMPTY_RESPONSE

Retry logic that rotates the exit IP

Python's requests library surfaces an empty response as a ConnectionError. Catch it, change the session ID so the retry leaves from a different residential IP, and send realistic headers so the request doesn't look like a bare bot.

import requests

HEADERS = {
    "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36",
    "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8",
    "Accept-Language": "en-US,en;q=0.9",
}

def fetch(url, attempt):
    username = f"USERNAME-country-us-session-job42x{attempt}"
    proxy = f"http://{username}:[email protected]:10000"
    return requests.get(
        url,
        proxies={"http": proxy, "https": proxy},
        headers=HEADERS,
        timeout=30,
    )

for attempt in range(3):
    try:
        resp = fetch("https://example.com/", attempt)
        print(resp.status_code)
        break
    except requests.exceptions.ConnectionError:
        pass  # empty response raises ConnectionError; retry on a new exit IP

FAQ

Frequently asked questions

Is ERR_EMPTY_RESPONSE a sign I'm being blocked?

Often, yes — especially if it's consistent on one site while others load fine, and the same URL works from a different network. Anti-bot systems frequently close connections from flagged IP ranges without sending any status code. But rule out the mundane causes first: a reused dead keep-alive socket and local filtering software produce the identical symptom.

What's the difference between ERR_EMPTY_RESPONSE and ERR_CONNECTION_RESET?

ERR_EMPTY_RESPONSE means the server accepted the connection and closed it cleanly with zero bytes sent. ERR_CONNECTION_RESET means the connection was torn down abruptly with a TCP reset, possibly mid-transfer. In practice both often point to the same thing for scrapers — something in the path refusing to serve your traffic — and the same diagnosis steps apply.

Why does the error happen intermittently rather than every time?

Three common reasons: connection pooling occasionally reuses a socket the server already closed; a rotating pool sends some requests through IP ranges the site tolerates and others through ranges it drops; and soft rate limiting only kicks in past a request-rate threshold. Logging which exit IP served each failed request narrows it down quickly.

Do residential proxies fix ERR_EMPTY_RESPONSE?

When the cause is IP reputation, yes — a request from a residential or mobile IP arrives looking like an ordinary subscriber, and sites that silently drop datacenter ranges will usually answer it normally. They won't help when the cause is server-side breakage or a stale keep-alive socket, which is why testing from a second network comes first.

Get responses, not silence. Start routing today.

Route through 1.5M+ residential IPs with sticky sessions, country targeting, and a 99.7% success rate across the network.

Get started