Message: session not created: cannot connect to chrome at 127.0.0.1:9222

[misterpeople]

Hey, Im getting this error

selenium.common.exceptions.SessionNotCreatedException: Message: session not created: cannot connect to chrome at 127.0.0.1:9222

Although im running on ChromeDriver 136.0.7103.92, I do not get this error on windows only on my linux server, talked with few people that are seeing the same error. Ive tried running on a new linux server and freshly installed everything and im getting the same error.

`with SB(uc=True, test=True, locale="en", proxy=DEDICATED_PROXY, ad_block=True, headed=True) as sb:
sb.activate_cdp_mode(url)
sb.sleep(3)

    # Wait for product title element (up to 20s), checking for not found error
    for _ in range(20):
        if check_and_handle_not_found(sb):
            return product_name, rating, reviews, orders, description, image_urls
        if sb.cdp.is_element_visible("h1[data-pl='product-title']"):
            break
        sb.sleep(1)
    # Get product name
    for _ in range(2):
        if check_and_handle_not_found(sb):
            return product_name, rating, reviews, orders, description, image_urls
        try:
            if sb.cdp.is_element_visible("h1[data-pl='product-title']"):`

[mdmintz]

cannot connect to chrome means that either Chrome isn't installed on your machine, or it's not located in the default location.
Use binary_location to set the location, which expects a full path to the Chrome executable.

[misterpeople]

Hey, thanks for the answer
Chrome is installed
(venv) home@/home/AliAffiliate# google-chrome --version
Google Chrome 136.0.7103.113

Still getting:
12|mainaliforward | Error in my_handler: Message: session not created: cannot connect to chrome at 127.0.0.1:9222

What else should i check?

[mstanowski]

I've got the same issue. Seleniumbase is closed in docker container, and fresh build works on my machine, also on production EC2 server, but do not work for my colleque (who has the same dev setup as me, Docker Desktop on Mac).

He got the same error message as you.

seleniumbase --version
seleniumbase 4.41.8

chromedriver --version
ChromeDriver 140.0.7339.207

google-chrome --version
Google Chrome 140.0.7339.207

[mdmintz]

I'd avoid Docker for UC Mode / CDP Mode. It leaves a hardcoded fingerprint, which prevents stealth.

[mstanowski]

Thanks @mdmintz for the info, good to know. But do you know if seleniumbase running directly on EC2 instance (instead of docker) will have no fingerprint and is better solution for stealth?

Meanwhile @misterpeople I found a fix for our problem.
My compose.yml has "platform: linux/amd64" set for service with chrome.
It's working great on our EC2 m6i instance.
It was working also on my Mac with Docker Desktop.
But was not working for my collegue on the same setup.

We found that our Docker Desktop setup is different.
I am using "Apple Virtualization framework" with "Use Rosetta for x86_64/amd64 emulation on Apple Silicon" checked

He had "Use Rosetta for x86_64/amd64 emulation on Apple Silicon" disabled. As soon as changed all works good for him as well.

No more error like this
"selenium.common.exceptions.SessionNotCreatedException: Message: session not created: cannot connect to chrome at 127.0.0.1:9222"

[mdmintz]

The main issue with EC2 would be the non-residential IP address, which could get flagged by anti-bot services that check for it. This can be avoided by setting a proxy server to use. (Set the proxy arg to connect to a proxy server address.)

[ramazan-umutlu]

In windows we have that problem, mac works fine.

Path is executeable everything was working but for a while that started saying cannot connect to chrome.

Also I am using chrome for testing thats why this happening.