undetected-chromedriver
undetected-chromedriver copied to clipboard
Message: unknown error: cannot connect to chrome at 127.0.0.1:52125
I am facing this error. Tried setting different options in chrome but nothing works. Versions I am currently using are:
Chromedriver: 96.0.4664.18 Chrome: 96.0.4664.110-1 undetected-chromedriver: 3.1.0
Unexpected error: Message: unknown error: cannot connect to chrome at 127.0.0.1:52125
from chrome not reachable
Stacktrace:
#0 0x555dcc35c173
same error with
Google Chrome 94.0.4606.54
ChromeDriver 94.0.4606.113
undetected-chromedriver==3.1.3
this happened due to race condition, we need to provide different profile path in options.
options = undetected_chromedriver.ChromeOptions() options.path =
<new temp folder path>
Same error here too, but I have to say that I'm working with Docker (not sure if this is relevant).
I've tested with different versions of Chrome, from version 90 to 100. The same error occurs with all of them. The driver log is continually filled with this error until it fails:
[1648861215.668][DEBUG]: DevTools HTTP Request: http://127.0.0.1:38429/json/version
[1648861215.671][DEBUG]: DevTools HTTP Request failed
[1648861215.722][DEBUG]: DevTools HTTP Request: http://127.0.0.1:38429/json/version
[1648861215.724][DEBUG]: DevTools HTTP Request failed
[1648861215.775][DEBUG]: DevTools HTTP Request: http://127.0.0.1:38429/json/version
[1648861215.777][DEBUG]: DevTools HTTP Request failed
@snehalwagh : there's no ChromeOptions.path
attribute, maybe you're talking about ChromeOptions.user_data_dir
? In this case you're right, Chrome can't have shared running profile.
It's very likely a duplicate of #572 which has been resolved (this was not a bug btw). Please check that your undetected-chromedriver package and your Chrome are both correctly updated.
In the Ubuntu 20.04, I have the same problem with you. However, in my macOS Monterey, I don't have such problem. A little bit confusing for me.
The same issue here with CentOS 8
The same issue here with CentOS 8
Ok, I figured out my problem when I tried to launch google chrome binary alone, and it gave an error saying that it should run with --no-sandbox option, so I add it to my code and it worked
The same issue here with CentOS 8
Ok, I figured out my problem when I tried to launch google chrome binary alone, and it gave an error saying that it should run with --no-sandbox option, so I add it to my code and it worked
It doesn't work for me.I always have --no-sandox option