Skip to content

[Bug]: No way to tell what triggers a net::ERR_ABORTED response #8246

@rmzg

Description

@rmzg

Bug description

Under a number of different circumstances, such as calling page.goto, puppeteer will throw Error: net::ERR_ABORTED, as far as I can tell, this is an internally generated error message not based on the server response and as such there is no way to determine why chrome has decided to throw this error.

Is there any kind of tracing/logging/debugging that can determine why chrome/puppeteer has decided to generate this error?

Puppeteer version

13.5.2

Node.js version

17.8.0

npm version

8.5.5

What operating system are you seeing the problem on?

Linux

Relevant log output

Error: net::ERR_ABORTED at https://www.totaljobs.com/job/net-software-developer-programmer/reflex-computer-recruitment-job97238730

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions