Lighthouse: ERR_ACCESS_DENIED via lighthouse API and Website

[jmartinezpoq]

Hi,
Our lighthouse executions started to fail with the following error.
This is happening in the most of the executions:
{ "error": { "errors": [ { "domain": "lighthouse", "reason": "lighthouseError", "message": "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_ACCESS_DENIED)" } ], "code": 500, "message": "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_ACCESS_DENIED)" } }

We are sure that the website is available, that the total load time is less than 60 seconds and that the lighthouse bot is not black listed.

Steps to reproduce

1. Run LH on via API
   https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=https://lolahome.es/puff-trenzado-fibra-beige-28573.html&key=YOURKEY&strategy=mobile&category=accessibility&category=performance&category=pwa&category=best-practices&category=seo

Environment Information

• Affected Channels: API
• Lighthouse version: v5

[devtools-bot]

Thanks chief! Appreciate you filing this bug. :clap:

This is a known issue, most well described in #2784. So, we'll automatically close this as a duplicate.

_However_, if you believe your bug is different than the cases described there, please comment here with "necessarily-wide-alpaca" and I'll reopen this bug. :robot: Beep beep boop.

[jmartinezpoq]

necessarily-wide-alpaca

[patrickhulce]

Thanks for filing @jmartinezpoq! I'm not able to reproduce this on PSI. Does it happen every time for you? Where are you making the request from and is it possible that site responds differently based on geo?

[jmartinezpoq]

Hi @patrickhulce this happens to us the 95% of the executions.
We are making the request from postman.
And the site doesnt has a different response based on geoip.
We are only detecting this behaviour via API thays why i opened the issue

[jmartinezpoq]

This is still failing to us. We are sure that the website is available.
We are seeing this in other projects like for the next request:
https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=https://www.lladro.com/es_es&key=YOURKEY&strategy=mobile&category=accessibility&category=performance&category=pwa&category=best-practices&category=seo
Response:
{ "error": { "errors": [ { "domain": "lighthouse", "reason": "lighthouseError", "message": "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_ACCESS_DENIED)" } ], "code": 500, "message": "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_ACCESS_DENIED)" } }

[rootman]

We have experienced the same using the pagespeed insights website.

https://developers.google.com/speed/pagespeed/insights/?hl=de&url=https%3A%2F%2Fwww.movingimage.com%2F&tab=desktop

The error is not present on every run, but it may show up on both mobile and desktop tabs.

[jmartinezpoq]

I was able to replicate the @rootman error from the pagespeed insights website.

For the URL: https://www.toyplanet.com/
Console Error:

Failed to load resource: the server responded with a status of 500 () https://www.googleapis.com/pagespeedonline/v5/runPagespeed?key=AIzaSyAwlPiPJIkTejgqqH01v9DmtPoPeOPXDUQ&locale=en_US&url=https%3A%2F%2Fwww.toyplanet.com%2F&strategy=mobile

cc @patrickhulce

[darxide-pl]

There are huge amount of api errors since 2019-10-25

[exterkamp]

This is resolved now :tada:

Read the summary post mortem in https://github.com/GoogleChrome/lighthouse/issues/9902#issuecomment-556414195