☂ "Unable to load the page"

[paulirish]

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: Unable to load the page: timeout reached - Server misconfigured #2459 (redirect configuration was botched, resulting in a error page if you navigate to the HTTP regularly in chrome) DevTools Error: Unable to load the page: net::ERR_CONNECTION_RESET #2500 (TLS handshake error) DevTools Error: Unable to load the page: net::ERR_EMPTY_RESPONSE #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: Site Redirects HTTP Traffic to HTTPS shouldn't stop the execution if failling #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: Unable to load the page: timeout reached - HSTS #2465
4. about:blank: Audits was started on about:blank somehow. Canonical issue: DevTools Error: Unable to load the page: timeout reached (about:blank) #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: Extension Error: Unable to load page: no document request found #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 Doesn't detect that page doesn't load due to bad SSL interstitial #1123
   Solution: Fix your server to return a valid, secure TLS certificate.

[padam2403]

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

[Bryze]

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

[pattarika]

Same issue with Brzye. Keeping getting 503 inside docker.
"userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/90.0.4414.0 Safari/537.36",
"environment": {
"networkUserAgent": "Mozilla/5.0 (Linux; Android 7.0; Moto G (4)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4143.7 Mobile Safari/537.36 Chrome-Lighthouse",
"hostUserAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/90.0.4414.0 Safari/537.36",
}
},
"lighthouseVersion": "7.1.0",
"runWarnings": [
"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: 503)"
],

[SamB]

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.

[clubclick]

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

…

On Fri, 19 Feb 2021 at 17:28, Samuel Bronson ***@***.***> 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 <#2784 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD66XA2HJPXOS3PUKOUPVXDS72NTTANCNFSM4DU4WA6Q> .

[pattarika]

@SamB I call this command inside docker

#!/bin/bash

while IFS= read -r line
do
echo $( date +%X ) 'Creating report for ' $line
lighthouse --quiet --no-enable-error-reporting --skip-audits redirects-http
--chrome-flags="--headless --disable-gpu --no-sandbox --disable-dev-shm-usage --ignore-certificate-errors"
$line --output html --output json
done < 'urls.txt'

[zqbe]

My ticket has been closed automatically. but I'm still having the below issue.

When using PageSpeed for testing the site below, we got an error.

https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwww.qbe.com%2Fau

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_CONNECTION_FAILED)

But the site is accessible. The wired thing is if we use PageSpeed from US region then it works fine. However, it's not working in Australia region.

[mreduar]

@zqbe how do you change the region?

[Mbellsudteen]

ในวันที่ ศ. 1 ต.ค. 2021 07:33 น. Eduar Bastidas ***@***.***> เขียนว่า:

…

@zqbe <https://github.com/zqbe> how do you change the region? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2784 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APZGLURACL7FUPWQW7GOW73UET6UNANCNFSM4DU4WA6Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[PachVerb]

i just run
lighthouse --help

tips Error:

ighthouse --help                                ✔  10030  22:17:37
internal/process/esm_loader.js:74
    internalBinding('errors').triggerUncaughtException(
                              ^

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. Received protocol 'node:'
    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:751:11)
    at Loader.resolve (internal/modules/esm/loader.js:85:40)
    at Loader.getModuleJob (internal/modules/esm/loader.js:229:28)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:51:40)
    at link (internal/modules/esm/module_job.js:50:36) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}

who can help me?

[PachVerb]

i want to know what happen?

[jigneshbhavani]

@PachVerb Updating my node version to 16.0 resolved the same issue.

i just run lighthouse --help

tips Error:

ighthouse --help                                ✔  10030  22:17:37
internal/process/esm_loader.js:74
    internalBinding('errors').triggerUncaughtException(
                              ^

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. Received protocol 'node:'
    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:751:11)
    at Loader.resolve (internal/modules/esm/loader.js:85:40)
    at Loader.getModuleJob (internal/modules/esm/loader.js:229:28)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:51:40)
    at link (internal/modules/esm/module_job.js:50:36) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}

who can help me?

@PachVerb Updating my node version to 16.0 resolved the same issue.

[PachVerb]

@PachVerb Updating my node version to 16.0 resolved the same issue.

i just run lighthouse --help
tips Error:

ighthouse --help                                ✔  10030  22:17:37
internal/process/esm_loader.js:74
    internalBinding('errors').triggerUncaughtException(
                              ^

Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader. Received protocol 'node:'
    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:751:11)
    at Loader.resolve (internal/modules/esm/loader.js:85:40)
    at Loader.getModuleJob (internal/modules/esm/loader.js:229:28)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:51:40)
    at link (internal/modules/esm/module_job.js:50:36) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}

who can help me?

@PachVerb Updating my node version to 16.0 resolved the same issue.

ok, work for me. thanks guys

[adamraine]

I dug through the history of this issue and it does seem obsolete. However the last triage was this comment #2784 (comment) indicating we should create some permanent FAQ for this. So there is still work to do, but no bugs to fix and at this point there are few enough issues related to main document errors that we can handle them on a case-by-case basis.