LightAtom

ERR_HTTP_RESPONSE_CODE_FAILURE: What It Means

The server replied with an HTTP error status (such as 403 or 500) and no page Chrome could show, so Chrome shows its own error instead.

ERR_HTTP_RESPONSE_CODE_FAILURE

The server answered with an error code instead of the page, without content Chrome could display. The real code (403, 404, 500…) is in the response.

Quick checks

  • Reload, and try a private window.
  • Open DevTools › Network to see the real status code.

Fixes on Mac

  1. Find the real status

    1. DevTools (⌥⌘I) › Network, reload, click the failed request and read Status.
    2. Then follow the guide for that code: 403, 404, 500 and so on.

  2. Clear cookies for the site

    1. Sessions that expired can produce 401/403 responses; delete the site's cookies and sign in again.

Fixes on Windows

  1. Same steps

    1. DevTools (F12) › Network to read the status, then fix that error.

Other devices

  1. Video and downloads

    1. Media and download links often expire; go back to the page and start again.

Still not working?

Site owners: this often appears for media, downloads or framed content when the server returns an error with an empty body. Check your logs for the request and return a body with a useful message.

See what’s happening

LightAtom's connections view shows which server answered, helpful when content comes from a separate CDN host.

Frequently asked questions

What causes ERR_HTTP_RESPONSE_CODE_FAILURE?

A response with an error status (4xx or 5xx) and nothing displayable, commonly for expired download links, blocked media or framed pages.

How do I see the actual error code?

Open DevTools › Network, reload, and select the red request; the Status column shows the server's code.

Is this my fault?

Sometimes, if a link expired or your session ended. Usually it's the server refusing or failing the request.

Related errors and tools

Related

LightAtom team

The people who build LightAtom, a network monitor for macOS.