You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
C:\>nodetest_proxy.mjs<html><head></head><body><prestyle="word-wrap: break-word; white-space: pre-wrap;">x.x.x.x</pre></body></html>C:\node_modules\puppeteer\lib\cjs\puppeteer\common\Connection.js:230error: newErrors_js_1.ProtocolError(),^ProtocolError: Protocolerror(Network.getCookies): Targetclosed.atC:\node_modules\puppeteer\lib\cjs\puppeteer\common\Connection.js:230:24atnewPromise(<anonymous>)
at CDPSession.send (C:\node_modules\puppeteer\lib\cjs\puppeteer\common\Connection.js:226:16)
at next (C:\node_modules\puppeteer-extra-plugin-stealth\evasions\sourceurl\index.js:32:41)
at CDPSession.send (C:\node_modules\puppeteer-extra-plugin-stealth\evasions\sourceurl\index.js:57:18)
at Object.getCookies (C:\node_modules\puppeteer-page-proxy\src\lib\cdp.js:6:38)
at CookieHandler.getCookies (C:\node_modules\puppeteer-page-proxy\src\lib\cookies.js:84:51)
at requestHandler (C:\node_modules\puppeteer-page-proxy\src\core\proxy.js:15:40)
at $ppp_request_listener (C:\node_modules\puppeteer-page-proxy\src\core\proxy.js:82:15)
at C:\node_modules\puppeteer\lib\cjs\puppeteer\common\Page.js:219:52 {originalMessage: ''}
Node.js v17.2.0
Of course, the code works, but at the end of it, an error appears when closing the browser.
There seems to be a problem closing the browser, because when I use it and cause a delay, there is no problem:
I use
puppeteer-extra
.It don't have problem in normal use.
But when I set proxy:
await useProxy(page, 'socks5://127.0.0.1:8080');
Complete code:
I get this error:
Of course, the code works, but at the end of it, an error appears when closing the browser.
There seems to be a problem closing the browser, because when I use it and cause a delay, there is no problem:
And also, when I use this, no problem:
But I do not know if this is a principle to prevent problems or if the error does not appear due to the delay in executing the command.
The text was updated successfully, but these errors were encountered: