Puppeteer: Navigation timeout of 30000 ms exceeded

A navigation started by page.goto(), page.waitForNavigation(), page.reload() or page.goBack() did not reach its waitUntil condition within the navigation timeout, 30 seconds by default. The default condition is load, which waits for every image, script, stylesheet and iframe on the page. networkidle0 and networkidle2 are stricter still, requiring the network to go quiet for 500 ms.

The message does not say which resource held the page open. Very often the HTML arrived quickly and the document is usable; a slow analytics script, a hanging ad request or a long-polling connection simply kept the load event from firing. A second common pattern is page.waitForNavigation() started after a click whose navigation had already completed, so it waits for a navigation that never comes.

What is not wrong: DNS and connectivity. Those fail fast with net::ERR_... errors instead.

import puppeteer from 'puppeteer';

const browser = await puppeteer.launch();
const page = await browser.newPage();
await page.goto('https://example.com/', { waitUntil: 'domcontentloaded' });
await page.waitForSelector('h1');

// Click that causes a full navigation
await Promise.all([
  page.waitForNavigation({ waitUntil: 'domcontentloaded' }),
  page.click('a.next'),
]);
await browser.close();

Separate "the document arrived" from "the content I need is ready": navigate with domcontentloaded and then wait for a concrete selector. Avoid networkidle0 on modern sites. Always arm waitForNavigation before the action that triggers it, and block heavy third-party traffic in scraping jobs where it adds nothing.