Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

This browser or app may not be secure [Login in Gmail] #880

Open
signaldev1 opened this issue Mar 12, 2024 · 6 comments
Open

This browser or app may not be secure [Login in Gmail] #880

signaldev1 opened this issue Mar 12, 2024 · 6 comments
Labels
issue: bug report A bug has been reported needs triage

Comments

@signaldev1
Copy link

I am encountering a security warning message when i try to Login in Gmail , "This browser or app may not be secure," when attempting to launch the browser using Puppeteer-extra. This issue persists even when I test the application locally or in the server I have tested the application both in headless mode and with the default configuration ('new'), but the security warning persists when i try to login in gmail. Any insights or guidance on resolving this issue would be greatly appreciated.

Couldn't sign you in

@signaldev1 signaldev1 added issue: bug report A bug has been reported needs triage labels Mar 12, 2024
@IqBroly
Copy link

IqBroly commented Mar 15, 2024

DId you test if stealth is working?

@signaldev1
Copy link
Author

@IqBroly yes working

@mihalichzh
Copy link

Hi! Any chance this issue to be fixed soon? We're having the same issue when attempting to login into Google Accounts.

@vladtreny
Copy link

Send your code to reproduce. Better compile everything in one file.

@zfcsoftware
Copy link

@vladtreny @mihalichzh @signaldev1 @IqBroly @peterblazejewicz
There are 2 ways I know to get around this. The first one can be passed only in windows operating system by using the following code. you are not caught thanks to targetFilter. The 2nd solution is to use puppeteer-real-browser.

First Solution:

const puppeteer = require('puppeteer-extra');
const StealthPlugin = require('puppeteer-extra-plugin-stealth');
puppeteer.use(StealthPlugin());

(async () => {
    const browser = await puppeteer.launch({
        headless: false,
        targetFilter: target => !!target.url(),
        args: ["--no-sandbox", "--disable-setuid-sandbox"]
    });
    var page = await browser.pages()
    page = page[0]


})();

This usage only works on windows. puppeteer-real-browser works on 2 operating systems. Please check this github discussion. You will definitely find a solution.
https://github.com/zfcsoftware/puppeteer-real-browser
#817

@dannyokec
Copy link

I dont think is a permanent thing. It comes and goes. how ever I think CDP could be the cause. that sh*t leaks a whole lot to detection systems

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: bug report A bug has been reported needs triage
Projects
None yet
Development

No branches or pull requests

6 participants