Selenium Error - The HTTP request to the remote WebDriver timed out after 60 seconds

Question

I ve been using Selenium for a number of months  which we re using to automate some of our internal testing processes  The scripts have been passing fine  I ve recently upgraded to C  2 40 0 webdriver using FF 27 01 and our scripts are now failing in random places with the following error     Portal SmokeTest SmokeRunTest Booking  TearDown method failed  OpenQA Selenium WebDriverException   The HTTP request to the remote WebDriver server for URL htt p    localhost 7055 hub session 56e99e88-ba17-4d12-bef1-c6a6367ccc2f element timed out after 60 seconds    ---- gt  System Net WebException   The operation has timed out TearDown   OpenQA Selenium WebDriverException   The HTTP request to the remote WebDriver server for URL htt p    localhost 7055 hub session 56e99e88-ba17-4d12-bef1-c6a6367ccc2f window timed out after 60 seconds    ---- gt  System Net WebException   The operation has timed out  09 01 20   Portal SmokeTest SmokeRunTest Booking  TearDown method failed  OpenQA Selenium WebDriverException   The HTTP request to the remote WebDriver server for URL htt p    localhost 7055 hub session 56e99e88-ba17-4d12-bef1-c6a6367ccc2f element timed out after 60 seconds    ---- gt  System Net WebException   The operation has timed out TearDown   OpenQA Selenium WebDriverException   The HTTP request to the remote WebDriver server for URL htt p    localhost 7055 hub session 56e99e88-ba17-4d12-bef1-c6a6367ccc2f window timed out after 60 seconds    ---- gt  System Net WebException   The operation has timed out    at OpenQA Selenium Support UI DefaultWait 1 PropagateExceptionIfNotIgnored Exception e     at OpenQA Selenium Support UI DefaultWait 1 Until TResult  Func 2 condition     at Portal Test Helpers Process Bookings OpenBookings SelectBooking String bookingnumber     at Portal SmokeTest SmokeRunTest Booking   in d  TeamCityAgent work dac1dcea7f2e80df SmokeTests SmokeRunTest cs line 68 --WebException    at System Net HttpWebRequest GetResponse      at OpenQA Selenium Remote HttpCommandExecutor CreateResponse WebRequest request  --TearDown    at OpenQA Selenium Remote HttpCommandExecutor CreateResponse WebRequest request     at OpenQA Selenium Remote HttpCommandExecutor Execute Command commandToExecute     at OpenQA Selenium Firefox Internal ExtensionConnection Execute Command commandToExecute     at OpenQA Selenium Remote RemoteWebDriver Execute String driverCommandToExecute  Dictionary 2 parameters     at OpenQA Selenium Remote RemoteWebDriver Close      at Portal Test Helpers Setup CloseWebdriver      at Portal SmokeTest SmokeRunTest TearDown   in d  TeamCityAgent work dac1dcea7f2e80df SmokeTests SmokeRunTest cs line 162 --WebException    at System Net HttpWebRequest GetResponse      at OpenQA Selenium Remote HttpCommandExecutor CreateResponse WebRequest request    The latest error I ve managed to track down to one single line of code    setup driver FindElement By XPath    button  class  buttonSmall lockBookingButton      Click      The annoying thing is  trying to fix the problem is proving difficult  as if I run the test on my local machine  in debug it passes   Additionally  if I run it via the NUNIT runner on the build machine I m running the test off  it also passes  It only seems to fail as part of our automated build running process when using Teamcity  Like I said  this has been running fine for months previously  and the only thing that has changed is the selenium webdriver kit    I have experienced this problem before  whilst in debug  and when a Click   line of code was called  Firefox appeared to lock up  and only stopping the test would allow Firefox to continue  There are a number of suggestions on here including modifying the webdriver source  I d like to not go down that route if possible if anyone else can offer any suggestions

User · Answer

Had same issue with Firefox  I switched over to Chrome with options and all has been fine since   ChromeOptions options   new ChromeOptions     options AddArgument  no-sandbox      ChromeDriver driver   new ChromeDriver ChromeDriverService CreateDefaultService    options  TimeSpan FromMinutes 3     driver Manage   Timeouts   PageLoad Add System TimeSpan FromSeconds 30

User · Answer

I had the same exception when trying to run a headless ChromeDriver with a scheduled task on a windows server  unattended   What solved it for me is to run the task as the user  quot Administrators quot   notice the S at the end   What I also did  I don t know if its relevant  is selected the  quot Any Connection quot  from the task  quot Conditions quot  tab

User · Answer

In my case none of the answers above solved my problem completely  I ended up using the  no-sandbox  mode  the connection with extended timeout period  driver   new RemoteWebDriver new Uri  quot http   localhost 4444 wd hub quot    capability  TimeSpan FromMinutes 3     and the page load timeout  driver Manage   Timeouts   PageLoad Add System TimeSpan FromSeconds 30     so now my code looks like this      public IWebDriver GetRemoteChromeDriver string downloadPath                ChromeOptions chromeOptions   new ChromeOptions            chromeOptions AddArguments               quot start-maximized quot                quot enable-automation quot                quot --headless quot                quot --no-sandbox quot     this is the relevant other arguments came from solving other issues              quot --disable-infobars quot                quot --disable-dev-shm-usage quot                quot --disable-browser-side-navigation quot                quot --disable-gpu quot                quot --ignore-certificate-errors quot            capability   chromeOptions ToCapabilities             SetRemoteWebDriver            SetImplicitlyWait            Thread Sleep TimeSpan FromSeconds 2            return driver                 private void SetImplicitlyWait                 driver Manage   Timeouts   PageLoad Add TimeSpan FromSeconds 30                private void SetRemoteWebDriver                 driver   new RemoteWebDriver new Uri  quot http   localhost 4444 wd hub quot    capability  TimeSpan FromMinutes 3           But as I mentioned none of the above method solved my problem  I was continuously get the error  and multiple chromedriver exe and chrome exe processses were active   10 of the chromedriver and  50 of chrome   So somewhere I read that after disposing the driver I should wait a few seconds before starting the next test  so I added the following line to dispose method      driver  Quit        driver  Dispose        Thread Sleep 3000    With this sleep modification I have no longer get the timeout error and there is no unnecessarily opened chromedriver exe and chrome exe processses  I hope I helped someone who struggles with this issue for that long as I did

User · Answer

I think this problem occurs when you try to access your web driver object after  1  a window has closed and you haven t yet switched to the parent   2  you switched to a window that wasn t quite ready and has been updated since you switched  waiting for the windowhandles count to be what you re expecting doesn t take into account the page content nor does document ready  I m still searching for a solution to this problem

User · Answer

Arrrgh  Faced this on macOS today and the issue was as simple as - the pop-up window suggesting to install the new Appium version was showing on the remote CI build server   Just VNC ing to it and clicking  Install later  fixed it

User · Answer

In my case  my button s type is submit not button and I change the Click to Sumbit then every work good  Something like below   from     driver FindElement By Id  btnLogin    Click     to    driver FindElement By Id  btnLogin    Submit     BTW  I have been tried all the answer in this post but not work for me

User · Answer

new FirefoxDriver new FirefoxBinary   new FirefoxProfile   TimeSpan FromSeconds 180      Launch your browser using the above lines of code  It worked for me

User · Answer

We had the same problem  In our case  the browser was blocked by a login popup  Windows authentication   so not returning after 60 seconds  Adding correct access rights to the Windows account Chrome was running under solved the problem

User · Answer

For ChromeDriver the below worked for me  string chromeDriverDirectory    quot C   temp  2 37 quot    var options   new ChromeOptions     options AddArgument  quot -no-sandbox quot     driver   new ChromeDriver chromeDriverDirectory  options    TimeSpan FromMinutes 2     Selenium version 3 11  ChromeDriver 2 37

User · Answer

I had a similar issue using the Chrome driver  v2 23    running the tests thru TeamCity  I was able to fix the issue by adding the  no-sandbox  flag to the Chrome options   var options   new ChromeOptions    options AddArgument  no-sandbox      I m not sure if there is a similar option for the FF driver  From what I understand the issue has something to do with TeamCity running Selenium under the SYSTEM account

User · Answer

I first encountered this issue months ago  also on the click   command   and it has been an issue for me ever since  It seems to be some sort of problem with the  NET Selenium bindings  This blog post by the guy that works on the IE driver is helpful in explaining what s happening   http   jimevansmusic blogspot com 2012 11 net-bindings-whaddaymean-no-response html  Unfortunately  there doesn t seem to be a real solution to this problem  Whenever this issue has been raised to the Selenium developers  see here   this is a typical response      We need a reproducible scenario  that must include a sample page or a link to a public site s page where the issue can be reproduced    If you are able to submit a consistently reproducible test case  that could be very helpful in putting this bug to rest for good   That said  perhaps you can try this workaround in the meantime  If the HTML button that you are trying to click   has an onclick attribute which contains Javascript  consider using a JavascriptExecutor to execute that code directly  rather than calling the click   command  I found that executing the onclick Javascript directly allows some of my tests to pass

User · Answer

Got similar issue  Try to set more time in driver s constructor - add eg    var timespan   TimeSpan FromMinutes 3    var driver   new FirefoxDriver binary  profile  timeSpan

User · Answer

The new FirefoxDriver binary  profile  timeSpan  has been obsolete   You can now use new FirefoxDriver FirefoxDriverService CreateDefaultService    FirefoxOptions options  TimeSpan commandTimeout  instead   There is also a new FirefoxDriver string geckoDriverDirectory  FirefoxOptions options  TimeSpan commandTimeout  and it does works  But it s undocumented  and you need to manually specify geckoDriverDirectory even though it s already in Path

User · Answer

In my case I found this error happening in our teams build server  The tests worked on our local dev machines   The problem was that the target website was not configured correctly on the build server  so it couldn t open the browser correctly   We were using the chrome driver but I m not sure that makes a difference

User · Answer

In my case the issue was with SendKeys   and Remote Desktop  Posting the workaround I have so far   I had a Selenium test which would fail when run as part of a Jenkins job on a node hosted in vSphere and administered through RDP  After some troubleshooting it turned out it succeeds if Remote Desktop is connected and focused but fails with the exception if Remote Desktop is disconnected or even minimized  As a workaround  I logged through vSphere Console instead of RDP and then even after closing vSphere the test didn t fail anymore  This is a workaround but I would have to be careful never to login through RDP and always to administer only through vSphere Console

User · Answer

changing the Selenium WebDriver ChromeDriver from 2 40 0 to 2 27 0 is ok for me

User · Answer

The problem is that the evaluation of Click   times out on your build env   you might want to dig into what happens on Click     Also  try adding Retrys for the Click   because occssionally the evaluations take longer time depending on network speeds  etc

User · Answer

In my case  it s because I deleted the chrome update folder  After chrome reinstall  it s working fine

[c#] Selenium Error - The HTTP request to the remote WebDriver timed out after 60 seconds

Examples related to c#

Examples related to selenium

Examples related to selenium-webdriver

Examples related to nunit

Examples related to teamcity