The HTTP request to the remote WebDriver server for URL http://localhost:51647/session timed out - Robotiq

Answered

Hello, I’ve been having an issue with Selenium for a while. The robot interacts with a web application, opens Chrome, and navigates to the appropriate URL. The page loads, but as soon as the first Selenium command needs to be executed, I get the following error: The HTTP request to the remote WebDriver server for URL http://localhost:51647/session timed out.

Chrome and Chromedriver versions are compatible. The error only occurs when the robot runs unattended; there are no issues when running from development. On this VM, no process involving Selenium can execute – this error always appears.

I’m using a Script step to execute the Selenium code.

Has anyone experienced a similar issue, and how did you resolve it?

Thanks in advance!

General Discussion script step Selenium unattendedrobot chromedriver

Nevena asked 4 weeks ago

You must login to post comments

Answers (4)

Best Answer

Dear Nevena, it’s unfortunate that you’re facing this issue.

Since I haven’t encountered the same problem, I’m not sure how to help.
However, you might consider uninstalling the current version of your browser and downgrading to an older version. Be sure to download the appropriate older driver for that version as well. Once you’ve done that, you can disable automatic updates to prevent any future issues. This might serve as a temporary solution until newer versions are released to address this problem. Numerous users have been expressing their complaints about this issue with Selenium, so let’s hope for the best! :).

Additionally, keep an eye on whether Robotiq releases a fix in their updates, so you can later modify your code to align with the new Robotiq steps when the issue is resolved.

NewUser answered 3 weeks ago

You must login to post comments

Hello, can you provide more information about how you created the process and what is included in the script step? I found that many users on the internet are having issues with Selenium after the recent upgrade 🙁 Take a look at this; it might be helpful.

NewUser answered 4 weeks ago

You must login to post comments

Thank you! This Youtube video helped me.

My code in the Script step was as follows:

var options = new ChromeOptions();
options.DebuggerAddress = “127.0.0.1:9222”;
IWebDriver driver = new ChromeDriver(driverPath, options);

and it was throwing the previous error.

I had already tried adding some arguments, but nothing solved the problem. However, after adding the argument from the video:
options.AddArguments(“–remote-allow-origins=*”);

the Selenium process is now running unattended again.

Thanks again!

Nevena answered 4 weeks ago

You must login to post comments

This solved my problem only temporarily, meaning that the first few times the unattended process ran with this command, it was executed successfully. However, after that, the same error started appearing again. I tried using some additional arguments, but without success.

When I attempted to open Chrome through a Script step, navigate to the appropriate URL, and execute Selenium commands, everything worked fine. However, the main issue occurs when trying to connect to an already open Chrome instance, which is actually what I need.

Nevena answered 4 weeks ago

You must login to post comments

Your Answer

Please login first to submit.