ERR_EMPTY_RESPONSE / empty reply from server
The connection opened and then closed with zero bytes of response. In scraping this is very often a deliberate drop: closing silently costs the target less than rendering a block page, and it tells you less.
A proxy fixes part of this. A better pool fixes the flaky-exit version. The deliberate-drop version needs the same work a 403 needs, and the silence is what makes it expensive to diagnose.
Why it happens
A deliberate drop by an anti-bot layer that decided not to answer at all.
A TLS mismatch where the server hangs up rather than sending an alert.
HTTP sent to an HTTPS port, or the reverse.
An exit node that died between the connection and the response.
How to fix it
- Repeat it. Consistent for one target and never for others means a block; occasional means a flaky exit.
- Check the scheme and port — an empty reply is what plain HTTP to port 443 looks like.
- If it is consistent, treat it as a 403 and change the fingerprint as well as the address.
FAQ
What does ERR_EMPTY_RESPONSE mean?›
Why am I getting ERR_EMPTY_RESPONSE?›
How do I fix ERR_EMPTY_RESPONSE?›
Will a proxy fix ERR_EMPTY_RESPONSE?›
Other errors
Stop getting ERR_EMPTY_RESPONSE
Residential IPs across 199 countries, from $7.35/GB — no commitment, no monthly plan.
Get residential IPs →