[Bug] Stealth is not working properly

[cyeibs]

• So, my point is to sign-in into PSN account.
• `const puppeteer = require("puppeteer-extra");
  const StealthPlugin = require("puppeteer-extra-plugin-stealth");
  const proxyRouter = require("@extra/proxy-router");
  puppeteer.use(StealthPlugin());
  puppeteer.use(require("puppeteer-extra-plugin-anonymize-ua")());

puppeteer.use(
proxyRouter({
proxies: { DEFAULT: "http://EwUbB71R:[email protected]:64402" },
})
);

const psnSignInPage = "https://store.playstation.com/en-tr/pages/latest";

const browserConfig = {
headless: false,
executablePath:
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome",
ignoreHTTPSErrors: true,
ignoreDefaultArgs: ["--enable-automation"],
slowMo: 0,
args: [
"--window-size=1400,900",
"--disable-gpu",
"--no-sandbox",
"--enable-webgl",
],
};`

so, I open page of store, go to sign-in page, using page.type(selector, "value") insert email and than password, click on sign-in and get error "Can't connect to the server".
But manually in main browser (not run by puppeteer-extra) it sign-in properly.

I tried headless: true - did not help

[dannyokec]

Loll. This could be either CDP or or you were caught spoofing navigator. Best hack around this would be to use an extension bypass. I had similar experience way back, the bypass did the trick for me

[dannyokec]

Loll. This could be either CDP or or you were caught spoofing navigator. Best hack around this would be to use an extension bypass. I had similar experience way back, the bypass did the trick for me

Can you please clarify what you mean by extension bypass? I'm having this same issue

I would ask you a couple question to enable me help you bypass the issue.

Firstly are you using puppeteer stealth in recent times? if you are they there would be an issue because stealth modifies the navigator in a way that show the navigator is not to be trusted. visit browserscan.net to see if the navigator was not trusted.

[Instantgrow]

Loll. This could be either CDP or or you were caught spoofing navigator. Best hack around this would be to use an extension bypass. I had similar experience way back, the bypass did the trick for me

Can you please clarify what you mean by extension bypass? I'm having this same issue

I would ask you a couple question to enable me help you bypass the issue.

Firstly are you using puppeteer stealth in recent times? if you are they there would be an issue because stealth modifies the navigator in a way that show the navigator is not to be trusted. visit browserscan.net to see if the navigator was not trusted.

hlo denny Sir, i have solution for it... to bypass anykind of detection..
contact me: [email protected]
You Know me Very Well By the Way...

[treyvanes]

Loll. This could be either CDP or or you were caught spoofing navigator. Best hack around this would be to use an extension bypass. I had similar experience way back, the bypass did the trick for me

Can you please clarify what you mean by extension bypass? I'm having this same issue

I would ask you a couple question to enable me help you bypass the issue.
Firstly are you using puppeteer stealth in recent times? if you are they there would be an issue because stealth modifies the navigator in a way that show the navigator is not to be trusted. visit browserscan.net to see if the navigator was not trusted.

hlo denny Sir, i have solution for it... to bypass anykind of detection.. contact me: [email protected] You Know me Very Well By the Way...

Can you tell us a little about your detection evasion?

[nwebson]

I made a patch for this issue, it disables Runtime.enable that causes a leak and which is used by many major anti-bot systems.
You can check it out here: https://github.com/rebrowser/rebrowser-patches