Chrome ERR_EMPTY_RESPONSE — Server Sent No Data

Fix Chrome ERR_EMPTY_RESPONSE error meaning the server accepted the connection but sent no data back, caused by server crashes, timeouts, or firewall interference. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: ERR_EMPTY_RESPONSE means Chrome connected to the server but received zero bytes in response. The TCP connection was established successfully (unlike connection refused or timeout). The server accepted the connection then either closed it or sent nothing. Different from ERR_CONNECTION_RESET where the server actively terminates the connection. Can be intermittent if the server is under heavy load. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: Server application crashed while processing the request. Server-side firewall or WAF dropping the response after accepting the connection. Proxy or reverse proxy failing to forward the response. Server-side timeout: application took too long and the web server closed the connection. SSL/TLS handshake failure after TCP connection establishment. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Refresh the page — transient server issues often resolve on retry. Clear Chrome browsing data: Settings > Privacy > Clear browsing data. Try incognito mode to rule out extension or cookie interference. Flush DNS: chrome://net-internals/#dns > Clear host cache. If the issue is only with one site: the problem is server-side, wait or contact the site owner. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our Browser Errors collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.