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

UC getting detected on a website(protected by DataDome) whereas original browser is not #1082

Open
ignis-tech-solutions opened this issue Feb 21, 2023 · 14 comments

Comments

@ignis-tech-solutions
Copy link

Hi, I'm trying to open a website but after accepting the T&C, it shows a captcha, solving which it says blocked on using UC. But normal google chrome works fine. I've also tried using NordVPN but no luck.

From what I know they are using datadome for security. Does anyone have a workaround to bypass this?

@ignis-tech-solutions ignis-tech-solutions changed the title UC getting detected on a website whereas original browser is not UC getting detected on a website(protected by DataDome) whereas original browser is not Feb 21, 2023
@ignis-tech-solutions
Copy link
Author

I can add more information if needed, please let me know.

@donggoing
Copy link

+1

@donggoing
Copy link

The same thing happened to me. You can experiment with specifying different browser versions (browser_executable_path) and user_data_dir, which worked for a while but quickly broke.

@ignis-tech-solutions
Copy link
Author

I'll try that out. One way I found(that will work for sometime) is to manually solve the captcha and retrieve the cookies from the request, then use the same cookies to run the automation with either UC or requests. Not sure for how long this will work though.

@donggoing
Copy link

I tried the cookie way before, and it has worked, but it doesn't work for me recently.
For my case, datadome used geetest captcha before but it changed now.

@dogi-sol
Copy link

I tried the cookie way before, and it has worked, but it doesn't work for me recently. For my case, datadome used geetest captcha before but it changed now.

Unfortunately, I'm experiencing the same issue as well. After a clean start, it doesn't get detected on the first run, but it does on subsequent runs no matter what I do. I'm also using this fork: #1010.

@dogi-sol
Copy link

I see that there was also an issue about this elsewhere, and I'm experiencing exactly what's shown in the video (seleniumbase/SeleniumBase#1760).

@dogi-sol
Copy link

Fun fact: If I open the page in regular Chrome browser from a fresh IP address in incognito mode, it works fine. If I refresh the page, it still works. But when I open the inspector and refresh the page, it immediately blocks the IP address. (https://antoinevastel.com/bots/datadome)

@donggoing
Copy link

A temporary workaround for me is to constantly switch proxies. Still working on it...

@ignis-tech-solutions
Copy link
Author

How are you maintaining a session when changing proxies?

@donggoing
Copy link

I do not. just simply switching.

@ignis-tech-solutions
Copy link
Author

Can you show the code where you're rotating proxies and bypassing them? Also, which proxies are you using, I'm using bright data.

@donggoing
Copy link

Just some tunnel proxy services.
BTW, is there any solution now?

@FranciscoPalomares
Copy link

Solutions ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants