can't execute rsDriver (connection refused)

Asked 30/7, 2017 at 2:38 Answered 8/5, 2023 at 3:5

I can't get anywhere with R selenium. Here's the first step and my output:

library(RSelenium)
rD <- rsDriver()
# checking Selenium Server versions:
#   BEGIN: PREDOWNLOAD
# BEGIN: DOWNLOAD
# BEGIN: POSTDOWNLOAD
# checking chromedriver versions:
#   BEGIN: PREDOWNLOAD
# BEGIN: DOWNLOAD
# BEGIN: POSTDOWNLOAD
# checking geckodriver versions:
#   BEGIN: PREDOWNLOAD
# BEGIN: DOWNLOAD
# BEGIN: POSTDOWNLOAD
# checking phantomjs versions:
#   BEGIN: PREDOWNLOAD
# BEGIN: DOWNLOAD
# BEGIN: POSTDOWNLOAD
# [1] "Connecting to remote server"
# Error in checkError(res) : 
#   Undefined error in httr call. httr output: Failed to connect to localhost port 4567: Connection refused
# In addition: Warning message:
#   In rsDriver() : Could not determine server status.

What did I miss ?

Deformity answered 30/7, 2017 at 2:38 Comment(0)

Note1: checkForServer() was removed in 1.7.9. I think it doesn't matter and the answer still holds up. If not please comment, I don't use it and don't have a windows machine anymore.

Note2: this answer is meant for Windows

Note3: I'm also happy to choose another answer since I was also the one who asked, but my answer has more points so make a case in comments

When trying to run the defunct checkForServer() Selenium offers two options:

use rsDriver
use Docker

see:

RSelenium::checkForServer()
# Error: checkForServer is now defunct. Users in future can find the function in 
# file.path(find.package("RSelenium"), "examples/serverUtils"). The
# recommended way to run a selenium server is via Docker. Alternatively
# see the RSelenium::rsDriver function.

Everybody seems to have issues with rsDriver and Docker is the recommended option so we'll go this route:

install docker
run it, restart computer as requested
pull image by running in command line: docker pull selenium/standalone-firefox(or chrome instead of firefox) or in R shell('docker pull selenium/standalone-firefox')
start server by running in command line: docker run -d -p 4445:4444 selenium/standalone-firefox or in R shell('docker run -d -p 4445:4444 selenium/standalone-firefox')
Then run remDr <- remoteDriver(remoteServerAddr = "localhost", port = 4445L, browserName = "firefox'") . The doc suggests something different with a virtual machine but i couldn't get it to work.

With this I was set, here is my code:

shell('docker run -d -p 4445:4444 selenium/standalone-firefox')
remDr <- remoteDriver(remoteServerAddr = "localhost", port = 4445L, browserName = "firefox")
remDr$open()
remDr$navigate("http://www.google.com/ncr")
remDr$getTitle()
# [[1]]
# [1] "Google"

The doc for more info:

Deformity answered 30/7, 2017 at 15:13 Comment(13)

Any similiar tutorial how to start using RSelenium on Mac? – Anastasius 31/7, 2017 at 18:8

I can't help you much unfortunately, see maybe this : #35619990 or this https://mcmap.net/q/451117/-rselenium-in-mac – Deformity 31/7, 2017 at 20:6

You've used the same command for pulling the image and starting the server: docker run -d -p 4445:4444 selenium/standalone-firefox Shouldn't the first be some invocation of docker pull instead? (using the same command for both tasks works, though, because docker run pulls the image if it is not available locally). – Lampas 2/8, 2017 at 10:45

You're right Frank, I had made a copy and paste mistake, it's fixed, thanks. I also harmonized the use of firefox and chrome as they was some ambiguity – Deformity 2/8, 2017 at 11:36

also it seems you have one ' too much in browserName = "firefox'" – Maus 18/10, 2017 at 21:6

don't you mean: system('docker run -d -p 4445:4444 selenium/standalone-firefox') ; instead of shell – Heathheathberry 4/3, 2018 at 11:53

it will have the same effect, shell is a more user-friendly wrapper for system from ?shell – Deformity 4/3, 2018 at 12:0

does this mean you are running RSelenium from inside Docker? – Crux 28/7, 2019 at 2:2

when I run this I get the following error Undefined error in httr call. httr output: Failed to connect to localhost port 4445: Connection refused – Sibbie 16/9, 2019 at 16:47

in R: system() is for mac, shell() is for Linux – Hartford 1/9, 2021 at 20:8

RSelenium::checkForServer does not exist – Teacart 28/3 at 10:27

So may you indicate that the answer is outdated? – Teacart 2/4 at 10:10

I don't know if it's outdated, as I said above checkForServer is not used in the solution, it's just the lead I followed at the time. For all I know the answer still works, but anyway see edit with notes 1 and 3 – Deformity 2/4 at 10:25

After using RSelenium/rsDriver for a while without issue, I recently got a very similar error message as OP, but couldn't use Docker to solve it (mostly for organizational reasons). Here's how I solved it:

Taking a look at the function documentation, it turns out that rsDriver() is default configured to launch the Selenium server with the latest versions of both Chrome and Firefox (Gecko) drivers, even if you have specified the other browser to run. In my case, I was specifying browser = "firefox", but a new Chrome driver had auto-downloaded on the most recent run and, for whatever reason, wasn't playing nice with Selenium. That was the root cause of the issue.

It's not particularly intuitive, and the "Connection refused" message doesn't really help, but following the error advice and checking the server log made me realize that Selenium was still trying to load Chrome drivers, even though I was using Firefox:

rd <- rsDriver(browser = "firefox")
# Yields an error message after doing pre/post downloads:

#> Could not open firefox browser.
#> Client error message:
#> Undefined error in httr call. httr output: Failed to connect to localhost port 4567: Connection refused
#> Check server log for further details.
#> Warning message:
#> In rsDriver(browser = "firefox" :
#>  Could not determine server status.

rd$server$log()

> $stderr
> [1] "Error: Could not find or load main class c(-Dwebdriver.chrome.driver=\"C:\filepath\to\chromedrivers\109.0.5414.25.chromedriver.exe\","

> $stdout
> character(0)

Anyway, if you specify rsDriver() to run with either an older driver version, or just pass in NULL so it doesn't look for a driver at all, it might fix the issue (it worked for me).

# Default parameters of the rsDriver() function:

rsDriver(port = 4567L,
         browser = c("chrome", "firefox", "phantomjs", "internet explorer"),
         version = "latest",
         chromever = "latest",
         geckover = "latest",
         iedrver = NULL,
         phantomver = "2.1.1",
         verbose = TRUE,
         check = TRUE,
         ...)

# Specify an older driver version you know works (or just use NULL), 
# even if it doesn't correspond to the browser you're using:

rd <- rsDriver(browser = "firefox",
               chromever = "109.0.5414.25") # alt: chromever = NULL

In case you're looking for the filepath that these drivers get saved to when auto-downloaded by RSelenium (e.g. maybe you want to find the name of an older driver version), on Windows, it should be ~/AppData/Local/binman.

Shoutout to the responses on this question, which also helped point me in the right direction!

Scalise answered 8/12, 2022 at 19:48 Comment(7)

Fantastic answer! I was worried I was going to have to put in a request to get docker installed (my company is fairly locked down permission wise). Your solution was a lifesaver! Can't believe it is checking for chrome when I am using firefox XD. – Gibbsite 9/12, 2022 at 18:27

Thank you so much for this answer! I was going crazy with the issue and could not find a solution. – Sainfoin 13/12, 2022 at 15:3

On second thought, it worked for me once, but I can't reproduce the fix. I'm now continuing to get the same error message. Frustrating. – Via 15/12, 2022 at 18:19

Things that worked for others: 1) deleting the LICENSE.chromedriver file and 2) rolling back wdman from version 0.2.6 to 0.2.5. What finally worked for me, though, was updating all of the packages that wdman is dependent upon. It appears that I had some pretty old versions of packages like yaml and jsonlite that hadn't been updated in a long time. Once I updated all of these, rsDriver started working again. – Via 16/12, 2022 at 16:23

thanks for figuring this out. all i had to change was adding chromever = NULL – Abana 31/12, 2022 at 17:6

I tried everything I could to get chrome to work, spent hours, and nothing did. Then switching to Firefox and using chromever = NULL worked. Like. A. Charm. Thank you! – Erythro 16/5, 2023 at 19:11

Same, setting up NULL chromever and firefox browser worked for me – Silber 17/7, 2023 at 12:50

In case that is still useful, I was running into the same problem today and was able to fix it by installing a Java Development Kit (Java SE Development Kit 11.0.1).

I was getting an error message from my computer to that effect, as well as the same R error as mentioned in this question, and it fixed it.

For a reproducible example, I was able to replicate this tutorial.

sessionInfo() R version 3.4.4 (2018-03-15) Platform: x86_64-apple-darwin15.6.0 (64-bit) Running under: macOS High Sierra 10.13.5

Matrix products: default
BLAS: /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/3.4/Resources/lib/libRlapack.dylib

locale:
[1] fr_CA.UTF-8/fr_CA.UTF-8/fr_CA.UTF-8/C/fr_CA.UTF-8/fr_CA.UTF-8

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base     

other attached packages:
[1] RSelenium_1.7.5

loaded via a namespace (and not attached):
[1] Rcpp_0.12.17     XML_3.98-1.11    binman_0.1.1     assertthat_0.2.0 rappdirs_0.3.1   bitops_1.0-6    
[7] R6_2.2.2         jsonlite_1.5     semver_0.2.0     httr_1.3.1       curl_3.2         xml2_1.2.0      
[13] subprocess_0.8.3 tools_3.4.4      wdman_0.2.4      yaml_2.1.18      compiler_3.4.4   caTools_1.17.1  
[19] openssl_1.0.1

Rudnick answered 5/1, 2019 at 18:50 Comment(3)

The site linked to is not working - could you add details of the fix in your answer? – Reverential 29/4, 2023 at 9:17

I'm afraid the website is down, and there doesn't seem to be a copy of it on the wayback machine :/ – Rudnick 30/4, 2023 at 22:14

Ah shame! An alternative tutorial is at joshuamccrain.com/tutorials/web_scraping_R_selenium.html (not that it will help until the issue is fixed). For me I could resolve the issue by deleting the license files from the chromedriver downloads. – Reverential 1/5, 2023 at 9:58

In 2023 I'm using chrome and getting this error and the solution that worked for me was to delete LICENSE.chromedriver in the following directory (on Windows 10):

C:\Users\YOURUSERNAME\AppData\Local\binman\binman_chromedriver\win32\114.0.5735.16

C:\Users\YOURUSERNAME\AppData\Local\binman\binman_chromedriver\win32\YOURCHROMEVERSION

I don't know why it works, it was suggested by a YouTuber who's name I can't remember and it worked for on three separate installs.

UPDATE (MARCH 2024): I finally gave up on Chrome and switched to FireFox when working on RSelenium and it has been working much better.

Mollymollycoddle answered 8/5, 2023 at 3:5 Comment(0)

Per the Cran vignette I had to run:

shell("docker-machine ip")

Then set the remoteServerAddr to the IP which was returned.

Misalliance answered 18/2, 2020 at 18:54 Comment(0)

Hot tags

Godot Unity Godot Help Programming Godot 4.X GUI GDScript 3D 2D Physics CSharp Godot 3.X VR XR Projects C++

Recommended topics

Hot tags