Puppeteer script suddenly stopped working after upgrading Puppeteer

I have a puppeteer script I run to reboot my modem. It has worked for I guess about a year with no problem. 5 days ago it stopped working. I was looking into it and realized that I am getting errors I didn't used to get when running it and the script fails. The thing is I didn't change anything. As far as I can see, the HTML hasn't changed either yet it is failing. So I wonder if there is a bug in chromium or puppeteer or if it handles things differently somehow?

Here's a codepen with https://codepen.io/michaelbierman/pen/qQjdYR

HTML page

puppeteer script

errors

ERROR OUTPUT

Thursday 11/15/2018 11:14:04, Login...
Unhandled Rejection at: Promise (new page) Promise
Error: No node found for selector: #id_username
at assert (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:278:11)
at Frame.type (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/FrameManager.js:771:5)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
-- ASYNC --
at Frame. (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:144:27)
at Page.type (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/Page.js:971:29)
at /Users/bierman/Documents/Applications/bin/arris/arristest.js:49:13
at
at process._tickCallback (internal/process/next_tick.js:188:7) reason: Error: No node found for selector: #id_username
at assert (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:278:11)
at Frame.type (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/FrameManager.js:771:5)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
-- ASYNC --
at Frame. (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:144:27)
at Page.type (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/Page.js:971:29)
at /Users/bierman/Documents/Applications/bin/arris/arristest.js:49:13
at
at process._tickCallback (internal/process/next_tick.js:188:7)
/Users/bierman/Documents/Applications/bin/arris/arristest.js:29
browser.close();
^

ReferenceError: browser is not defined
at process.on (/Users/bierman/Documents/Applications/bin/arris/arristest.js:29:2)
at emitTwo (events.js:126:13)
at process.emit (events.js:214:7)
at emitPendingUnhandledRejections (internal/process/promises.js:108:22)
at process._tickCallback (internal/process/next_tick.js:189:7)
BigMac:bin michael$ /usr/local/bin/node /Users/bierman/Documents/Applications/bin/arris/arristest.js
Thursday 11/15/2018 11:20:29, Login...
Thursday 11/15/2018 11:20:36, Go to home...
Unhandled Rejection at: Promise (new page) Promise
Error: No node found for selector: #alertExitButton
at assert (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:278:11)
at Frame.click (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/FrameManager.js:704:5)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
-- ASYNC --
at Frame. (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:144:27)
at Page.click (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/Page.js:932:29)
at /Users/bierman/Documents/Applications/bin/arris/arristest.js:62:13
at
at process._tickCallback (internal/process/next_tick.js:188:7) reason: Error: No node found for selector: #alertExitButton
at assert (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:278:11)
at Frame.click (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/FrameManager.js:704:5)
at
at process._tickCallback (internal/process/next_tick.js:188:7)
-- ASYNC --
at Frame. (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/helper.js:144:27)
at Page.click (/Users/bierman/Documents/Applications/bin/arris/node_modules/puppeteer/lib/Page.js:932:29)
at /Users/bierman/Documents/Applications/bin/arris/arristest.js:62:13
at
at process._tickCallback (internal/process/next_tick.js:188:7)
/Users/bierman/Documents/Applications/bin/arris/arristest.js:29
browser.close();
^

asked Nov 15 '18 at 19:36

Michael Bierman

308

Might sound a bit obvious but if you've upgraded your puppeteer version and are seeing this only after the upgrade, have you tried deleting your node_modules folder, package-lock.json file and then re-installing your project dependencies (including the updated version of puppeteer) from scratch using npm install? Can often clear up strange errors like this.

– AJC24
Nov 16 '18 at 14:59

Thanks! Excellent suggestion. I will try that and see what happens.

– Michael Bierman
Nov 16 '18 at 16:56

Let me know how you get on. Will try and work with you on this issue if it's still coming up.

– AJC24
Nov 16 '18 at 18:04

I deleted the files you specified and reinstalled. I got a few errors along the way, but things seem to be working better. I don't know if I should be concerned about these errors pastebin.com/R48Nrv44

– Michael Bierman
Nov 16 '18 at 23:16

Looks like node doesn't have some permissions that it needs. I've had this on my Mac and had to manually change the node directory to my users home directory to resolve it. EIther way the node docs can help (hopefully). You should have a look here to try and resolve your issue: docs.npmjs.com/…

– AJC24
Nov 17 '18 at 1:11

add a comment |

Here's a codepen with https://codepen.io/michaelbierman/pen/qQjdYR

HTML page

puppeteer script

errors

ERROR OUTPUT

asked Nov 15 '18 at 19:36

Michael Bierman

308

Might sound a bit obvious but if you've upgraded your puppeteer version and are seeing this only after the upgrade, have you tried deleting your node_modules folder, package-lock.json file and then re-installing your project dependencies (including the updated version of puppeteer) from scratch using npm install? Can often clear up strange errors like this.

– AJC24
Nov 16 '18 at 14:59

Thanks! Excellent suggestion. I will try that and see what happens.

– Michael Bierman
Nov 16 '18 at 16:56

Let me know how you get on. Will try and work with you on this issue if it's still coming up.

– AJC24
Nov 16 '18 at 18:04

I deleted the files you specified and reinstalled. I got a few errors along the way, but things seem to be working better. I don't know if I should be concerned about these errors pastebin.com/R48Nrv44

– Michael Bierman
Nov 16 '18 at 23:16

Looks like node doesn't have some permissions that it needs. I've had this on my Mac and had to manually change the node directory to my users home directory to resolve it. EIther way the node docs can help (hopefully). You should have a look here to try and resolve your issue: docs.npmjs.com/…

– AJC24
Nov 17 '18 at 1:11

add a comment |

Here's a codepen with https://codepen.io/michaelbierman/pen/qQjdYR

HTML page

puppeteer script

errors

ERROR OUTPUT

asked Nov 15 '18 at 19:36

Michael Bierman

308

Here's a codepen with https://codepen.io/michaelbierman/pen/qQjdYR

HTML page

puppeteer script

errors

ERROR OUTPUT

chromium puppeteer

asked Nov 15 '18 at 19:36

Michael Bierman

308

asked Nov 15 '18 at 19:36

Michael Bierman

308

asked Nov 15 '18 at 19:36

Michael Bierman

308

asked Nov 15 '18 at 19:36

Michael Bierman

308

asked Nov 15 '18 at 19:36

Michael Bierman

308

Might sound a bit obvious but if you've upgraded your puppeteer version and are seeing this only after the upgrade, have you tried deleting your node_modules folder, package-lock.json file and then re-installing your project dependencies (including the updated version of puppeteer) from scratch using npm install? Can often clear up strange errors like this.

– AJC24
Nov 16 '18 at 14:59

Thanks! Excellent suggestion. I will try that and see what happens.

– Michael Bierman
Nov 16 '18 at 16:56

Let me know how you get on. Will try and work with you on this issue if it's still coming up.

– AJC24
Nov 16 '18 at 18:04

I deleted the files you specified and reinstalled. I got a few errors along the way, but things seem to be working better. I don't know if I should be concerned about these errors pastebin.com/R48Nrv44

– Michael Bierman
Nov 16 '18 at 23:16

Looks like node doesn't have some permissions that it needs. I've had this on my Mac and had to manually change the node directory to my users home directory to resolve it. EIther way the node docs can help (hopefully). You should have a look here to try and resolve your issue: docs.npmjs.com/…

– AJC24
Nov 17 '18 at 1:11

add a comment |

Might sound a bit obvious but if you've upgraded your puppeteer version and are seeing this only after the upgrade, have you tried deleting your node_modules folder, package-lock.json file and then re-installing your project dependencies (including the updated version of puppeteer) from scratch using npm install? Can often clear up strange errors like this.

– AJC24
Nov 16 '18 at 14:59

Thanks! Excellent suggestion. I will try that and see what happens.

– Michael Bierman
Nov 16 '18 at 16:56

Let me know how you get on. Will try and work with you on this issue if it's still coming up.

– AJC24
Nov 16 '18 at 18:04

I deleted the files you specified and reinstalled. I got a few errors along the way, but things seem to be working better. I don't know if I should be concerned about these errors pastebin.com/R48Nrv44

– Michael Bierman
Nov 16 '18 at 23:16

Looks like node doesn't have some permissions that it needs. I've had this on my Mac and had to manually change the node directory to my users home directory to resolve it. EIther way the node docs can help (hopefully). You should have a look here to try and resolve your issue: docs.npmjs.com/…

– AJC24
Nov 17 '18 at 1:11

Might sound a bit obvious but if you've upgraded your puppeteer version and are seeing this only after the upgrade, have you tried deleting your node_modules folder, package-lock.json file and then re-installing your project dependencies (including the updated version of puppeteer) from scratch using npm install? Can often clear up strange errors like this.

– AJC24
Nov 16 '18 at 14:59

Thanks! Excellent suggestion. I will try that and see what happens.

– Michael Bierman
Nov 16 '18 at 16:56

Let me know how you get on. Will try and work with you on this issue if it's still coming up.

– AJC24
Nov 16 '18 at 18:04

I deleted the files you specified and reinstalled. I got a few errors along the way, but things seem to be working better. I don't know if I should be concerned about these errors pastebin.com/R48Nrv44

– Michael Bierman
Nov 16 '18 at 23:16

Looks like node doesn't have some permissions that it needs. I've had this on my Mac and had to manually change the node directory to my users home directory to resolve it. EIther way the node docs can help (hopefully). You should have a look here to try and resolve your issue: docs.npmjs.com/…

– AJC24
Nov 17 '18 at 1:11

add a comment |

0

active

oldest

votes

Your Answer

StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53326770%2fpuppeteer-script-suddenly-stopped-working-after-upgrading-puppeteer%23new-answer', 'question_page');

);

Post as a guest

Name

Required, but never shown

0

active

oldest

votes

0

active

oldest

votes

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Myujth