You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have developed a script in which I want to reach destination url after login in Google. Google Login was working fine in headless mode using selenium-wire, undetected-chromedriver when it was not in docker container. So driver was not getting detected. But, after I put that code in docker container it started giving in error in login page.
This browser or app may not be secure.
Also, I created python virtual environment added same code. In that also it is working fine.
I tried all different ways to resolve the issue but didn't get success.
Tried different headers
Tried different user agents
Tried to upgrade/downgrade chrome to latest versions and older versions
I need help to resolve issue in docker container. Is there any way to detect the difference how undetected-chromedriver is working in with and without container ? so that I can know what is missing in container that is required by undetected-chromedriver.
The text was updated successfully, but these errors were encountered:
Hi
I have developed a script in which I want to reach destination url after login in Google. Google Login was working fine in headless mode using selenium-wire, undetected-chromedriver when it was not in docker container. So driver was not getting detected. But, after I put that code in docker container it started giving in error in login page.
This browser or app may not be secure.
Also, I created python virtual environment added same code. In that also it is working fine.
I tried all different ways to resolve the issue but didn't get success.
I need help to resolve issue in docker container. Is there any way to detect the difference how undetected-chromedriver is working in with and without container ? so that I can know what is missing in container that is required by undetected-chromedriver.
The text was updated successfully, but these errors were encountered: