lighthouse: ☂ "Unable to load the page"

Within Lighthouse, this error comes from gatherRunner.assertPageLoaded. This is called right after we finish loading the page for a pass (there are 3 passes by default). It looks for the HTML resources’s network record (via some URL comparison).

If it fails to find a match, we error. Or if we find a match, but the network record is marked as failed, then we error.

There are a few cases in which this error shows up.

  1. Server failure with initial request URL: The HTML request was matched but determined to be failed. This happens with incorrect server configurations, when the server does not reply at all, or replies with an empty/otherwise invalid response. Examples: #2459 (redirect configuration was botched, resulting in a error page if you navigate to the HTTP regularly in chrome) #2500 (TLS handshake error) #2646 (a local server replies with an empty response) Solution: Fix your server to return valid HTML documents with successful status codes.
  2. Server doesn’t offer HTTP: The host doesn’t offer a site at the HTTP URL at all. Example: #1978 Solution: Change your server to redirect HTTP traffic to HTTPS
  3. ~HSTS: The host is using HSTS, and Chrome can’t allow the browser to attempt to navigate to HTTP. Example: #2465~
  4. about:blank: Audits was started on about:blank somehow. Canonical issue: #2362. This should be fixed on the DevTools side, and will ship in m61, but can still happen occasionally for unknown reasons. If this happens consistently on a particular URL for you, please file a separate issue specifying the URL. Solution: Restart Chrome and run Lighthouse again. If problem persists with a particular URL, file a new issue here with the title “Reproducible about:blank errors”
  5. No document request found: Lighthouse was unable to identify any network request as the main HTML resource. Example: #3496 Solution: Restart Chrome and run Lighthouse again. If problem persists with a particular URL, file a separate issue with the title “Cannot identify main document”
  6. Bad TLS/certificate interstitial. Lighthouse couldn’t load the page because Chrome couldn’t handle the security configuration of the URL. Example #1123 Solution: Fix your server to return a valid, secure TLS certificate.

About this issue

  • Original URL
  • State: open
  • Created 7 years ago
  • Reactions: 54
  • Comments: 43 (1 by maintainers)

Most upvoted comments

Hmm. it would be easier to figure out what’s going on if lighthouse could show you the failing request (if any), rather than just the status code.

Hello, there is a lot of links in google that follows to this page, that shows a lot of cases of the error but without examples of solution of the problem. Could you provide some examples to fix these issues quickly?

i want to know what happen?

Why this error.

issue 2

The HyperText Transfer Protocol (HTTP) 500 Internal Server Error reset service workers

On Fri, 19 Feb 2021 at 17:28, Samuel Bronson notifications@github.com wrote:

Hmm. it would be easier to figure out what’s going on if lighthouse could show you the failing request (if any), rather than just the status code.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/GoogleChrome/lighthouse/issues/2784#issuecomment-782220776, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD66XA2HJPXOS3PUKOUPVXDS72NTTANCNFSM4DU4WA6Q .

In my case, was checking a few urls, which to my surprise works fine on web.dev / page speed insights.

But, when I run the test via cli in a dockerised environment, lighthouse returns me the following errors (although works fine on my local docker instance)

 GatherRunner:error Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 403) https://www.magicbricks.com/prestige-lakeside-habitat-whitefield-bangalore-pdpid-4d4235303139343638

another one

GatherRunner:error Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 417) https://www.99acres.com/search/property/buy/residential-all/gurgaon?search_type=QS&refSection=GNB&search_location=CP1&lstAcn=CP_R&lstAcnId=1&src=CLUSTER&preference=S&selected_tab=1&city=8&res_com=R&property_type=R&isvoicesearch=N&keyword_suggest=gurgaon%3B&fullSelectedSuggestions=gurgaon&strEntityMap=W3sidHlwZSI6ImNpdHkifSx7IjEiOlsiZ3VyZ2FvbiIsIkNJVFlfOCwgUFJFRkVSRU5DRV9TLCBSRVNDT01fUiJdfV0%3D&texttypedtillsuggestion=gurgaon&refine_results=Y&Refine_Localities=Refine%20Localities&action=%2Fdo%2Fquicksearch%2Fsearch&suggestion=CITY_8%2C%20PREFERENCE_S%2C%20RESCOM_R&searchform=1&price_min=null&price_max=null

Could someone help identify whether the problem lies in how it is being executed, or there is something wrong with the page itself.

Environment Details Lighthouse Version: 7.0.1

Hi,

While using the Google Pagespeed v5 Lighthouse API, I generally face the HTTP 500 Error.

After some time, when I rerun for the same URL, I get the data.

Can anyone help how can I overcome this?

Thanks, Padam

The outstanding work here is to take the body of the issue and add it to an FAQ in our readme.

Same here few days back lighthouse audits were working fine. Today I checked it was not working. Getting the same error as rahul’s.

I tried switching to incognito, updated my ssl certificates. And still get the error.

Speed test url: https://web.dev/measure/ Website link: https://as2dc10.gamooga.com:456/ Error Mesage: Error: Error: Lighthouse returned error: FAILED_DOCUMENT_REQUEST. Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Details: net::ERR_FAILED)

I got this bug “#3199” because my server doesn’t offer the right HTTP URL. This is my old nginx config:

server {
    listen    80;
    server_name    *.tecposter.cn;
    return 301 https://$server_name$request_uri;
}

The value of $server_name is “*.tecposter.cn” and it need to be changed to $http_host:

server {
    listen    80;
    server_name    *.tecposter.cn;
    return 301 https://$http_host$request_uri;
}