Gmail login blocked - Githubissues

filipopo / undetected-chromedriver-lambda

A minimal working example of using undetected-chromedriver on AWS Lambda

MIT License

6 stars 2 forks source link

Gmail login blocked #3

Open ejooroo opened 8 months ago

ejooroo commented 8 months ago

First of all, I want to congratulate and thank you for the great work you've done.

I am using the Docker base image filipmania/undetected-chromedriver-lambda:latest to create an AWS Lambda function. However, I am experiencing an issue when trying to access Gmail using this Lambda function; it seems like access is being blocked, similar to what happens with traditional Selenium.

202403302250

Interestingly, I can successfully log in to Gmail from my local machine using undetected-chromedriver. I was wondering if you have any idea why this might be happening. Is there any specific configuration I should be aware of when using this image in a Lambda environment?

I appreciate any help or suggestions you can provide.

filipopo commented 8 months ago

Hey, thanks for using the image!

Can you share more info about how you're using undetected-chromedriver from your local machine? Did you run a container from this image locally or just some script?

I see two possibilities here:

Google doesn't like some of the ChromeOptions here: https://github.com/filipopo/undetected-chromedriver-lambda/blob/main/main.py In case you're using different options you may want to align them or test various combinations with them, afaik undetected-chromedriver doesn't recommend adding any options but in my tests I needed at least some of those to get past bot detection on some website
Google doesn't like AWS ip's If the container works locally then you could try to use a proxy either with the ChromeOptions in undetected chromedriver or set something up on AWS

ejooroo commented 8 months ago

Thank you for your quick response!

I got'it. The issue was due to these options arguments:

options.add_argument('--headless=new')
options.add_argument('--single-process')

With those options enabled, Google blocks access, and if I remove them, I can't get the Lambda function to work.

At the moment, I can't think of what I can do about it.

filipopo commented 6 months ago

Hey @ejooroo Sorry for taking a long time, well unfortunately those options are necessary for it to work on Lambda but have you tried experimenting with the other options and seeing if Google allows you login?

Alternatively have you considered doing what you need to do with some other method such as the gmail API? https://developers.google.com/gmail/api/guides