same problem here.

node-v: 9.7.1

goPage: async function (url) {
        let page = await this.page;

        await page.goto(url);
        await page.setViewport({width: 1366, height: 768});

        try {
            const waitNavigationPromise = page.waitForNavigation({timeout: 10000, waitUntil: "load"});

            await waitNavigationPromise;

            return await page;
        }
        catch(e) {
            this.catchError(e, page);

            return false;
        }
    },

Error: Navigation Timeout Exceeded: 10000ms exceeded
    at Promise.then (/var/www/crawler/node_modules/puppeteer/lib/NavigatorWatcher.js:73:21)
    at <anonymous>

@hkhan-lumatax can you please provide a reproducible example? It should be a script that I'll be able to run locally to see the issue.

We won't be able to help otherwise.

@aslushnikov I seem to have ran into the same issue. Here's a reproducible example:

const puppeteer = require('puppeteer');

const getData = async () => {
  const browser = await puppeteer.launch({
    executablePath: '/usr/bin/chromium',
    headless: false
  });

  const page = await browser.newPage();
  page.goto('https://discordbots.org');

  await page.waitFor('.bot-list-section')

  const data = await page.$$eval('.bot-card', divs => Array.from(divs).map(bot => ({
    id: bot.querySelector('.info a').href.split('/').pop(),
    name: bot.querySelector('.bot-name').innerHTML,
    status: bot.querySelector('.status').innerHTML
  })))

  browser.close();
  return data;
};

getData()
  .then(data => {
    console.log(data.length);
  });

The browser opens, the result gets logged and the browser closes. The process idles for 30 seconds. The error gets logged, and then the process exits.

The error does not occur if you await the page.goto(...) call. It should also be noted that the issue only occurs with websites that "load slowly" (referring to the spinner at the top of the tab), possibly because browser.close() is called before the promise from page.goto(...) resolves?

My environment information:

• Puppeteer version: 1.4.0
• Platform / OS version: Arch Linux 4.14.15-1
• Node.js version: 10.1.0

@aetheryx Thanks, I see what's going on here. That's somewhat related to #1454; as a workaround, I'd recommend navigating until domcontentloaded event:

await page.goto('https://discordbots.org', {waitUntil: 'domcontentloaded'});

'load' worked for me:

await page.goto('http://example.com', {waitUntil: 'load'});

im seeing neither works
domcontentloaded relieves the exception but produces no query data
load produces query data and an exception
there is a race condition between the latter when data sometimes queries

same problem here.

node-v: 9.7.1

goPage: async function (url) {
        let page = await this.page;

        await page.goto(url);
        await page.setViewport({width: 1366, height: 768});

        try {
            const waitNavigationPromise = page.waitForNavigation({timeout: 10000, waitUntil: "load"});

            await waitNavigationPromise;

            return await page;
        }
        catch(e) {
            this.catchError(e, page);

            return false;
        }
    },

Error: Navigation Timeout Exceeded: 10000ms exceeded
    at Promise.then (/var/www/crawler/node_modules/puppeteer/lib/NavigatorWatcher.js:73:21)
    at <anonymous>

I believe you were doing it the wrong way.

You shall define waiter promise at first, call the URL change and then await waiter promise to complete.

const waiter = page.waitForNavigation({
  waitUntil: 'networkidle0',
});

await page.goto(url);

await waiter;

Of course, you can add waitUntil option into goto call directly as well.

We're marking this issue as unconfirmed because it has not had recent activity and we weren't able to confirm it yet. It will be closed if no further activity occurs within the next 30 days.

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!