Page.goto: net::err_aborted; maybe frame was detached?


The error message “net::err_aborted; maybe frame was detached?” usually occurs when a page attempts to navigate to another URL using the page.goto() method, but the frame being navigated has been detached or closed. This can happen in scenarios where the target frame was opened in a separate window or tab and then closed, or when there are issues with the frame’s existence or accessibility.

To better understand this error, let’s consider an example. Suppose we have a Puppeteer script in Node.js where we create a new page, perform some actions on it, and then try to navigate to a different URL using page.goto():

const puppeteer = require('puppeteer');
async function run() {
  try {
    const browser = await puppeteer.launch();
    const page = await browser.newPage();
    // Do some actions on the page
    await page.goto('');
    // Continue with other operations
    await browser.close();
  } catch (error) {


In this example, if an error occurs with the navigation, and the error message includes “net::err_aborted; maybe frame was detached?”, it means that the specified URL cannot be reached from the current page because the frame has been detached or closed. This commonly happens if the page was opened in a new tab or window, but that tab or window was then closed before the navigation.

To resolve this issue, you can modify your script to handle such cases gracefully by wrapping the page.goto() method in a try-catch block and checking for any related errors. Depending on your specific requirements, you can choose to ignore such errors and continue with the script’s execution, or you can take appropriate action, such as logging the error, retrying the navigation, or terminating the script.

Leave a comment