[🐛 Bug]: Unable to Access Chrome's Remote Debugging Port

[h-nakao]

What happened?

I am a beginner. I'm sorry if I was saying something strange.

I got a timeout error after I raised the version.

Error: The HTTP request to the remote WebDriver server for URL http://localhost:56649/session timed out after 60 seconds.

• Chrome version 115.XXX → 116.XXX
• Chrome driver version 115.XXX → 116.XXX
• Selenium version 4.10.0 → 4.11.1

How can we reproduce the issue?

1.Start Chrome with the following arguments
--profile-directory = "default" -remote-debugging-port = 9222

2.I used to operate it with the code below, but I get an error. 

    ChromeDriverService = ChromeDriverService.CreateDefaultService( );
    service.HideCommandPromptWindow = false;

    ChromeOptions options = new ChromeOptions
    {
        DebuggerAddress = "127.0.0.1:9222"
    };

    webDriver = new ChromeDriver(service, options);

Relevant log output

https://www.selenium.dev/documentation/webdriver/troubleshooting/logging/ says ".NET does not currently have a Logging implementation".

Operating System

Windows10

Selenium version

DotNet 4.11.0

What are the browser(s) and version(s) where you see this issue?

116.0.5845.97

What are the browser driver(s) and version(s) where you see this issue?

116.0.5845.96

Are you using Selenium Grid?

No response

[github-actions]

@h-nakao, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[titusfortner]

I think this is going to fix that: #12534
It'll get merged for 4.12 and hopefully released soon.

[h-nakao]

Thank you very much.
I will wait for the release of 4.12.

[h-nakao]

I was able to confirm that it moved normally.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.