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.

TimeoutError: Navigation Timeout Exceeded: 30000ms exceeded

See original GitHub issue

client@0.1.0 postbuild D:\OfficiaL\blog\client react-snap

?? error at / TimeoutError: Navigation Timeout Exceeded: 30000ms exceeded at D:\OfficiaL\blog\client\node_modules\puppeteer\lib\LifecycleWatcher.js:142:21 – ASYNC – at Frame.<anonymous> (D:\OfficiaL\blog\client\node_modules\puppeteer\lib\helper.js:111:15) at Page.goto (D:\OfficiaL\blog\client\node_modules\puppeteer\lib\Page.js:674:49) at Page.<anonymous> (D:\OfficiaL\blog\client\node_modules\puppeteer\lib\helper.js:112:23) at fetchPage (D:\OfficiaL\blog\client\node_modules\react-snap\src\puppeteer_utils.js:232:22) at processTicksAndRejections (internal/process/task_queues.js:95:5)

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! client@0.1.0 postbuild: react-snap npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the client@0.1.0 postbuild script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\Admin\AppData\Roaming\npm-cache_logs\2021-08-21T21_02_16_602Z-debug.log

this one is updated version still not working

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:6
  • Comments:6

github_iconTop GitHub Comments

1reaction
harrymelkacommented, Mar 9, 2022
Screenshot 2022-03-09 at 18 03 15

Go to LifecycleWatcher.js inside node modules, _createTimeoutPromise functions line 137 and just add

return new Promise(() => {});

With that you are removing the timeout.

it should work, it’s going to take more time to do it but it’s working.

0reactions
dominiczycommented, Mar 5, 2022

I was able to fix this by setting Puppeteer options to “waitUntil”: “networkidle2”

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to solve Puppeteer TimeoutError: Navigation timeout of ...
How to solve Puppeteer TimeoutError: Navigation timeout of 30000 ms exceeded ... (specifically the TimeoutError) after a page takes more than 30000ms (30 ......
Read more >
Webscraping TimeoutError: Navigation timeout of 30000 ms ...
the timeout is exceeded during navigation. the remote server does not respond or is unreachable. the main resource failed to load. By default, ......
Read more >
Navigation timeout of 30000 ms exceeded with Puppeteer ...
Works fine in emulator, as soon as I deploy to the cloud it gives "Navigation timeout of 30000 ms exceeded" error 90% of...
Read more >
Fix: navigation timeout of 30000 ms exceeded in puppeteer?
In this video, I am going to show you how we can fix navigation timeout of 30000 ms exceeded in puppeteer.You will generally...
Read more >
Dealing with timeouts in Puppeteer 🐢️
The Problem: "TimeoutError: Navigation Timeout Exceeded: 30000ms exceeded" # · Solution 1: Set or disable the timeout for a navigation/request #.
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