Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PROD Lighthouse test: Something went wrong. Error: ERRORED_DOCUMENT_REQUEST #15629

Closed
kenshanta opened this issue Nov 23, 2023 · 3 comments
Closed
Assignees

Comments

@kenshanta
Copy link

kenshanta commented Nov 23, 2023

Summary

In my basic next.js portfolio website all reports return a score of 0/100 and printing out the error: **Something went wrong. Error: ERRORED_DOCUMENT_REQUEST
**

Tried reproducing the issue locally but to no avail. The tests pass even on an incognito tab.

Repo Link

Any help is much appreciated!

Screenshot 2023-11-23 at 2 31 40 PM Screenshot 2023-11-23 at 2 34 38 PM
@adamraine
Copy link
Member

I can reproduce on PageSpeed insights: https://pagespeed.web.dev/analysis/https-kovlekjian-com/7dsfxvsh36?form_factor=mobile

And with Lighthouse CLI using headless Chrome: https://googlechrome.github.io/lighthouse/viewer/?gist=db700e67657846899e0af4ff0900a724

Lighthouse is accurately reporting that the server is issuing a 401 response when it tries to load the page. If I had to guess, I would say that the server is doing this because the user agent contains HeadlessChrome instead of Chrome. Regardless, this doesn't appear to be an issue in Lighthouse.

@adamraine adamraine closed this as not planned Won't fix, can't repro, duplicate, stale Nov 27, 2023
@kenshanta
Copy link
Author

kenshanta commented Nov 28, 2023

@adamraine I understand that the issue isn't from lighthouse on the basis that the error is handled, what i don't understand is closing this thread based on a guess.

I've been trying to figure out the right steps for this, and opening an issue was my last hope.
What should i do? or where should this question be asked?

@adamraine
Copy link
Member

I closed the issue because Lighthouse is working as expected regardless of if my guess about headless chrome was correct or not.

I was only trying to point you in the right direction based on the conditions that would reproduce this error. The issue probably lies somewhere in your server configuration so I would suggest starting there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants