question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Timeout trying to navigate to a site

See original GitHub issue

Steps to reproduce

const puppeteer = require(‘puppeteer’); (async () => { const browser = await puppeteer.launch(); const page = await browser.newPage(); await page.goto(‘https://www.ronyohananov.com/’, {waitUntil: ‘networkidle2’, timeout: 200000}); console.log(“done ok”); await browser.close(); })(); Tell us about your environment:

const puppeteer = require(‘puppeteer’); (async () => { const browser = await puppeteer.launch(); const page = await browser.newPage(); await page.goto(‘https://www.ronyohananov.com/’, {waitUntil: ‘networkidle2’, timeout: 200000}); console.log(“done ok”); await browser.close(); })();

What is the expected result? Navigation to finish

What happens instead? (node:24491) UnhandledPromiseRejectionWarning: TimeoutError: Navigation timeout of 200000 ms exceeded …/node_modules/puppeteer/lib/cjs/puppeteer/common/LifecycleWatcher.js:106:111 (node:24491) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:24491) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Even with a large timeout the issue persist.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:10

github_iconTop GitHub Comments

1reaction
saideepesh000commented, Dec 11, 2020

@uriya2, (I think) try using timeout 0

0reactions
stale[bot]commented, Jul 25, 2022

We are closing this issue. If the issue still persists in the latest version of Puppeteer, please reopen the issue and update the description. We will try our best to accomodate it!

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to Fix the ERR_CONNECTION_TIMED_OUT Error - Kinsta
When you visit a website and it doesn't load, your browser will try for around 30 seconds or so until it terminates the...
Read more >
11 Ways to Fix the ERR_CONNECTION_TIMED_OUT Error
When your internet connection times out and you can't access a specific webpage, it's one of the most annoying errors.
Read more >
Timeout error occurs when I try to navigate to certain url ...
Issue: Timeout error occurs when I try to navigate to certain URL immediately after opening the browser. But when I try to navigate...
Read more >
How to Fix the ERR_CONNECTION_TIMED_OUT Error
ERR_CONNECTION_TIMED_OUT, also called the timeout error, means a website took too long to respond to the browser's request. Generally, a site ...
Read more >
How to solve Puppeteer TimeoutError: Navigation timeout of ...
In this article, i'll explain you briefly 2 ways to bypass this limitation. A. Globally on the tab. The option that i prefer,...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found