I would like to use puppeteer with my current chrome (keeping my credentials) #3543

lucasteisseire · 2018-11-14T14:40:46Z

i'm actually trying to use puppeteer for scraping and i need to use my current chrome to keep all my credentials and use it instead of relogin and type password each time which is a really time lose !

is there a way to connect it ? how to do that ?
i'm actually using node v11.1.0
and puppeteer 1.10.0

let scrape = async () => {
    const browser = await log()
    const page = await browser.newPage()           
    const delayScroll = 200
// Login 
await page.goto('somesite.com');
await page.type('#login-email', '*******);
await page.type('#login-password', "******");
await page.click('#login-submit');
// Wait to login
await page.waitFor(1000);

}
and now it will be perfect if i do not need to use that and go on page (headless, i dont wan't to see the page opening i'm just using the info scraping in node) but with my current chrome who does not need to login to have information i need. (because at the end i want to use it as an extension of chrome)

thx in advance if someone knows how to do that

The text was updated successfully, but these errors were encountered:

aslushnikov · 2018-11-14T22:04:32Z

@lucasteisseire in order to run puppeteer against stable chrome, you should do the following:

Figure the version of your stable chrome installation (in your stable chrome, navigate to about:version)
Figure out matching Puppeteer version in our api.md
Install puppeteer-core
Use puppeteer-core to launch the stable chrome, passing the executablePath option:

const pptr = require('puppeteer-core');
(async () => {
  const browser = await pptr.launch({
    executablePath: '<path-to-my-chrome-exec>'
  });
  // ... go on...
})();

Hope this helps.

pratik-joshi-cactus · 2019-06-29T04:36:03Z

Not working :/ in Version 75.0.3770.100 (Official Build) (64-bit), It still opens up new instance of chrome and it has no history whatsoever, I had to open it along with my other chrome tabs.

const puppeteer = require('puppeteer');
const pptr = require('puppeteer-core');
(async () => {

	const browser = await puppeteer.launch({
	  headless: false,
	  executablePath: '/usr/bin/google-chrome'
	});

})();

Here I also tried puppeteer-core , means pptr variable await pptr.launch in above variable, still not working. The issues is not closed!
Please check :
https://drive.google.com/file/d/1WKjgPeruK9-ABeHHsumhcjs_FTlzFH4S/view

mcarneiro · 2019-07-12T20:50:13Z

Maybe this post might help:

https://medium.com/@jaredpotter1/connecting-puppeteer-to-existing-chrome-window-8a10828149e0

alex2844 · 2019-09-19T09:18:13Z

@lucasteisseire in order to run puppeteer against stable chrome, you should do the following:

Figure the version of your stable chrome installation (in your stable chrome, navigate to about:version)

Figure out matching Puppeteer version in our api.md

Install puppeteer-core

Use puppeteer-core to launch the stable chrome, passing the executablePath option:
const pptr = require('puppeteer-core');
(async () => {
  const browser = await pptr.launch({
    executablePath: '<path-to-my-chrome-exec>'
  });
  // ... go on...
})();
Hope this helps.

not working

        var browser, page;
        browser = await puppeteer.launch({
            executablePath: '/usr/bin/chromium', 
            userDataDir: '/tmp/browser'                                                                                                                
        });
        page = await browser.newPage();
        await page.goto('https://gmail.com/');
        await browser.close();
        browser = await puppeteer.launch({
            headless: false,
            executablePath: '/usr/bin/chromium',
            userDataDir: '/tmp/browser'
        });
        page = await browser.newPage();
        await page.goto('chrome://history/'); // history empty

urosran · 2019-10-09T14:08:23Z

The instructions above launch headless chrome

from chrome//about :
Google Chrome | 77.0.3865.90 (Official Build) (64-bit) (cohort: Stable)
Chromium 77.0.3803.0 should be Puppeteer v1.19.0 (per github link above)
npm list
+-- puppeteer@1.19.0
+-- puppeteer-core@1.19.0

code:
``
const pptr = require('puppeteer-core');
(async () => {
const browser = await pptr.launch({
executablePath: 'C:\Program Files (x86)\Google\Chrome\Application\chrome.exe'
});

const page = await browser.newPage();
await page.goto('https://www.airbnb.com/');
console.log(page.url())
})();

``

runs in console and logs the correct url

Ramanth · 2020-01-22T06:34:25Z

what is the minimum version of chrome required?
i have to automate a chrome v61 which is opened already in remote-debugging-mode?

ashminbhandari · 2020-04-12T04:28:39Z

Hey guys, I found a solution to this problem. So you can input the path to your userDataDir as part of the puppeteer launch parameters. Look for profile path by executing chrome://version in your browser. Doing this, puppeteer executed itself in the same chrome window that I am currently using.

pptr.launch({headless: false,
  executablePath: '[insert executable path here]',
  userDataDir: '[insert profile path or user directory path here]'}).then(async browser => {
});

ORESoftware · 2020-04-28T01:37:27Z

@ashminbhandari puppeteer-core or puppeteer?

ashminbhandari · 2020-04-28T02:11:27Z

@ORESoftware OOF, I believe it was puppeteer-core but I am not 100%

ORESoftware · 2020-04-28T03:34:03Z

@ashminbhandari yeah I am looking for an answer to #5756

eduardoewgo · 2020-05-02T21:23:48Z

Any progress on this, @ORESoftware ?

I've been trying to use my installed version for a while now :/..

The idea is to keep all my browser information/credentials while running puppeteer.

ashminbhandari · 2020-05-03T02:49:36Z

@ORESoftware Are you in a position to use something else? I switched to Selenium when I ran into this problem. And I believe it is suggested that you instead copy your profile directory and provide the path to that instead because running two instances on the same profile directory causes problems.

matheuscch · 2020-05-25T02:28:51Z

I'm using something like that.

My idea is to make the puppteer open in a url window, to be inserted into a page at run time

No answer so far

eduardoewgo · 2020-05-26T18:52:40Z

@matheuscch

Try this

create a new chrome shortcut on your desktop and add --remote-debugging-port=9222 to the target.
open it using the just created shortcut and go to http://127.0.0.1:9222/json/version

This json should give you the webSocketDebuggerUrl, which you case use to connect to the instance. If I'm not wrong it should be something like

await puppeteer.connect({browserWSEndpoint: webSocketDebuggerUrl})

imvetri · 2024-02-26T05:26:07Z

Hey guys, I found a solution to this problem. So you can input the path to your userDataDir as part of the puppeteer launch parameters. Look for profile path by executing chrome://version in your browser. Doing this, puppeteer executed itself in the same chrome window that I am currently using.
pptr.launch({headless: false,
  executablePath: '[insert executable path here]',
  userDataDir: '[insert profile path or user directory path here]'}).then(async browser => {
});

Executable path and userDataDir can be found here
chrome://version/

singladno · 2024-04-08T15:09:47Z

Hey guys, I found a solution to this problem. So you can input the path to your userDataDir as part of the puppeteer launch parameters. Look for profile path by executing chrome://version in your browser. Doing this, puppeteer executed itself in the same chrome window that I am currently using.
pptr.launch({headless: false,
  executablePath: '[insert executable path here]',
  userDataDir: '[insert profile path or user directory path here]'}).then(async browser => {
});

This works perfectly fine with one little thing:
when you take the profile path from
chrome://version/
make sure to remove "Default" from the path's end

Andriy-Kulak · 2024-04-08T20:34:55Z

@matheuscch

Try this

create a new chrome shortcut on your desktop and add --remote-debugging-port=9222 to the target.

open it using the just created shortcut and go to http://127.0.0.1:9222/json/version

This json should give you the webSocketDebuggerUrl, which you case use to connect to the instance. If I'm not wrong it should be something like

await puppeteer.connect({browserWSEndpoint: webSocketDebuggerUrl})

If anyone ever gets here, this still works but you need to replace localhost with 127.0.0.1 in webSocketDebuggerUrl when using newer versions of node.js. Reference this #8873

D210000 · 2024-05-27T06:34:20Z

@matheuscch

Try this

create a new chrome shortcut on your desktop and add --remote-debugging-port=9222 to the target.

open it using the just created shortcut and go to http://127.0.0.1:9222/json/version

This json should give you the webSocketDebuggerUrl, which you case use to connect to the instance. If I'm not wrong it should be something like

await puppeteer.connect({browserWSEndpoint: webSocketDebuggerUrl})

If anyone ever gets here, this still works but you need to replace localhost with 127.0.0.1 in webSocketDebuggerUrl when using newer versions of node.js. Reference this #8873

Hey I still not able to connect webSocketdebugger cause site not open at all

aslushnikov closed this as completed Nov 14, 2018

aslushnikov mentioned this issue Nov 14, 2018

Chrome in headless mode #3541

Closed

hjyssg mentioned this issue Oct 29, 2020

crawler hjyssg/ShiguReader#97

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

I would like to use puppeteer with my current chrome (keeping my credentials) #3543

I would like to use puppeteer with my current chrome (keeping my credentials) #3543

lucasteisseire commented Nov 14, 2018

aslushnikov commented Nov 14, 2018

pratik-joshi-cactus commented Jun 29, 2019

mcarneiro commented Jul 12, 2019

alex2844 commented Sep 19, 2019 •

edited

urosran commented Oct 9, 2019 •

edited

Ramanth commented Jan 22, 2020

ashminbhandari commented Apr 12, 2020 •

edited

ORESoftware commented Apr 28, 2020

ashminbhandari commented Apr 28, 2020

ORESoftware commented Apr 28, 2020

eduardoewgo commented May 2, 2020 •

edited

ashminbhandari commented May 3, 2020

matheuscch commented May 25, 2020 •

edited

eduardoewgo commented May 26, 2020

imvetri commented Feb 26, 2024

singladno commented Apr 8, 2024 •

edited

Andriy-Kulak commented Apr 8, 2024

D210000 commented May 27, 2024

I would like to use puppeteer with my current chrome (keeping my credentials) #3543

I would like to use puppeteer with my current chrome (keeping my credentials) #3543

Comments

lucasteisseire commented Nov 14, 2018

aslushnikov commented Nov 14, 2018

pratik-joshi-cactus commented Jun 29, 2019

mcarneiro commented Jul 12, 2019

alex2844 commented Sep 19, 2019 • edited

urosran commented Oct 9, 2019 • edited

Ramanth commented Jan 22, 2020

ashminbhandari commented Apr 12, 2020 • edited

ORESoftware commented Apr 28, 2020

ashminbhandari commented Apr 28, 2020

ORESoftware commented Apr 28, 2020

eduardoewgo commented May 2, 2020 • edited

ashminbhandari commented May 3, 2020

matheuscch commented May 25, 2020 • edited

eduardoewgo commented May 26, 2020

imvetri commented Feb 26, 2024

singladno commented Apr 8, 2024 • edited

Andriy-Kulak commented Apr 8, 2024

D210000 commented May 27, 2024

alex2844 commented Sep 19, 2019 •

edited

urosran commented Oct 9, 2019 •

edited

ashminbhandari commented Apr 12, 2020 •

edited

eduardoewgo commented May 2, 2020 •

edited

matheuscch commented May 25, 2020 •

edited

singladno commented Apr 8, 2024 •

edited