Error guide / ERR_EMPTY_RESPONSE
ERR_EMPTY_RESPONSE error
ERR_EMPTY_RESPONSE means the browser connected to the server but got zero bytes back: the connection opened and then closed empty. In plain terms, the server accepted the request but sent nothing instead of a page. It is not a timeout, where nothing answers at all, and not a refusal: here the connection worked, but the response is blank.
Check your site
What causes it
On shared cPanel/LiteSpeed hosting the usual reason is a process that died mid-response: PHP hit a fatal error after output had already started, or the worker was killed by a CPU or memory limit (CloudLinux LVE) before it finished. Less often it is a server crash or restart, or a protocol mismatch, with the browser speaking HTTPS to a plain-HTTP port or the reverse.
How to fix it
- Reload the page and open it in an incognito window or another browser to rule out a one-off glitch and the cache.
- Check whether it is only you: open the site over mobile data or use the availability checker below. If it answers there, the problem is local.
- Temporarily disable any VPN, proxy, and blocking extensions, since they sometimes cut the response short.
- If the site is yours, open the error log in cPanel (or the LiteSpeed log) and look for a PHP fatal error or a Killed line at the moment of the request - that points to the code or a limit.
- Raise PHP memory_limit and max_execution_time (php.ini or MultiPHP) and compare CPU and memory usage against your LVE limits in cPanel, since the worker is likely hitting a cap on a heavy page.
- Make sure you use the right protocol (https:// with a valid certificate), and if it just started, restart the web server (LiteSpeed/Apache) or contact hosting support with the exact time and URL.