Question related Puppeteer-real-browser

[Biswajit96]

1. FingerPrint
   which one is best ?
   "fingerprint-generator": "^2.1.30",
   "fingerprint-injector": "^2.1.30",
   or
   puppeteer-afp

2. Extra-plugins
   dose Puppeteer-real-browser need puppeteer-extra & puppeteer-extra-plugin-stealth or its can mask all parameters its self without extra plugins ?

3. Puppeteer Version and Cluster tool
   my bot using "puppeteer": "^21.5.0" with Puppeteer Cluster Puppeteer-real-browser work fine with any version or need any specific version ?

thank you in advance :)

[zfcsoftware]

Hello,
puppeteer-real-browser creates a real browser and does not need any fingerprint plugin. You can go through bot detection tools without using any plugins.
https://fingerprint.com/demo/
Fingerprint plugins are to avoid getting caught by sites like this that detect if it is the same browser. I recommend using puppeteer-afp.
I haven't checked Puppeteer Cluster, sorry. I will check it out. Thank you

[Biswajit96]

Hello, puppeteer-real-browser creates a real browser and does not need any fingerprint plugin. You can go through bot detection tools without using any plugins. https://fingerprint.com/demo/ Fingerprint plugins are to avoid getting caught by sites like this that detect if it is the same browser. I recommend using puppeteer-afp. I haven't checked Puppeteer Cluster, sorry. I will check it out. Thank you

thank you so much for your attention. i really appreciated your help.

[Biswajit96]

Good evening sir,
when my developer try to implement real browser in our project.
my developer say puppeteer real browser uses deprecated option for puppeteer so we can't use args , but without args can't changing proxy and other settings. (browserWSEndpoint, is no longer supported)
Please advice.
thanks in advance.

[zfcsoftware]

Good evening sir, when my developer try to implement real browser in our project. my developer say puppeteer real browser uses deprecated option for puppeteer so we can't use args , but without args can't changing proxy and other settings. (browserWSEndpoint, is no longer supported) Please advice. thanks in advance.

Hi, I just tested it and I didn't have any problem using a proxy. The problem may be caused by your code. You can check the video below. Please provide video about the problem you are having.

2024-02-07.21-10-08.mp4

[mubaidr]

Thanks for this awesome library, here is related error:

[zfcsoftware]

Thanks for this awesome library, here is related error:

This error seems to be Typescript specific. Can you try the Typescript version @CrispyyBaconx created? I didn't encounter an error when using Commanjs. Thank you for using the library.
https://github.com/zfcsoftware/puppeteer-real-browser/tree/Type-Script

[CrispyyBaconx]

Thanks for this awesome library, here is related error:

The puppeteer.launch function doesn't take browserWSEndpoint as an arg according to their docs (https://pptr.dev/api/puppeteer.puppeteerlaunchoptions)

The way you are currently using it by launching it is creating two browser instances since you are launching Chrome with the library and also launching a puppeteer instance of Chrome. The Websocket Endpoint is used to control an already launched instance of Chrome. Use puppeteer.connect in that case.

[mubaidr]

Thanks for this awesome library, here is related error:

The puppeteer.launch function doesn't take browserWSEndpoint as an arg according to their docs (https://pptr.dev/api/puppeteer.puppeteerlaunchoptions)

The way you are currently using it by launching it is creating two browser instances since you are launching Chrome with the library and also launching a puppeteer instance of Chrome. The Websocket Endpoint is used to control an already launched instance of Chrome. Use puppeteer.connect in that case.

Exactly, but in that case, we cannot pass args when using connect option.

[marcusdiy]

Hello. Did you manage to make browser.newPage work again? Can you share a snippet? Thanks

[mubaidr]

Hello. Did you manage to make browser.newPage work again? Can you share a snippet? Thanks

You may use my fork of this repo. Which allows passing args, potentially solving this issue.

[marcusdiy]

@mubaidr yes, i tried. Same problem. await browser.newPage() never resolves

console.log('Try to open new tab');
let page2 = await browser.newPage();
console.log('New page opened, try an alert!');
await page2.evaluate(() => { alert(33) })
await page2.goto('https://nopecha.com/demo/cloudflare#1');

[zfcsoftware]

This issue has been resolved please try the latest version of the library. If the problem persists you can start a new discussion.