When running WebDriver with Chrome browser getting message Only local connections are allowed even though browser launches properly

Question

When I run Chrome browser using WebDriver  I am getting following message on console  Please let me know how to resolve it        Starting ChromeDriver  v2 10 267521  on port 22582    Only local   connections are allowed     Here is my sample code   public class Browserlaunch       public static void main String   args            System setProperty  webdriver chrome driver    C   chromedriver win32     chromedriver exe            WebDriver driver   new ChromeDriver             driver get  http   webdunia com            driver close            driver quit

User · Answer

This was happening to me when I had to fix an old project that had not been looked at in a while  The chromedriver associated to the project was not compatible with my version of chrome  so when I updated the chromedriver it worked fine

User · Answer

I had to run my commands in the one and same terminal  not seperately   nohup sudo Xvfb  10 -ac export DISPLAY  10 java -jar vendor se selenium-server-standalone bin selenium-server-standalone jar -Dwebdriver chrome bin   usr bin google-chrome  -Dwebdriver chrome driver  vendor bin chromedriver

User · Answer

After hours of analysis reading tons of logs and sourcecode  finally found problem  And it is quite easy to solve it  in sinle line  you need to pass --whitelisted-ips  into chrome driver  not chrome   executables You can do it in few ways  If you use ChromeDriver locally directly from code  just insert lines below before ChromeDriver init     System setProperty  quot webdriver chrome whitelistedIps quot    quot  quot     If you use it remotely  eg  selenium hub grid  you need to set system property when node starts  like in command  java -Dwebdriver chrome whitelistedIps  testClass etc     or docker by passing JAVA OPTS env   chrome      image  selenium node-chrome 3 141 59     container name  chrome     depends on        - selenium-hub     environment        - HUB HOST selenium-hub       - HUB PORT 4444       - JAVA OPTS -Dwebdriver chrome whitelistedIps

User · Answer

I was getting the exact same errors  I battled this issue for a few hours today  It seemed to be caused by a mismatch between the versions of chromedriver and selenium-server-standalone  The config js file was referencing a directory that had chromedriver 2 9 and selenium-server-standalone 2 35 0  Once I made sure we were referencing 2 10 and 2 42 2  it worked

User · Answer

Very often this error appears if you use incompatible versions of Selenium and ChromeDriver   Selenium 3 0 1 for Maven project        lt dependency gt           lt groupId gt org seleniumhq selenium lt  groupId gt           lt artifactId gt selenium-java lt  artifactId gt           lt version gt 3 0 1 lt  version gt       lt  dependency gt    ChromeDriver 2 27  https   sites google com a chromium org chromedriver downloads

User · Answer

This is an informational message only  It means nothing if your test scripts and chromedriver are on the same machine then it is possible to add the  whitelisted-ips  option  your test will run fine However if you use chromedriver in a grid setup  this message will not appear

User · Answer

I solved this error by installing the browser driver    Navigate your browser to seleniumhq org website Select the Downloads tab Scroll down the page to the Browser section and download the driver you want by clicking the link  for example  Google Chrome Driver Double-click the downloaded file  for example  chromedriver mac64 1  zip Double-click the extracted file  for example  chromedriver   Reference   search YouTube com for the error  Platform   macOS High Sierra 10 13 3

User · Answer

Chromedriver is a WebDriver  WebDriver is an open-source tool for automated testing of web apps across many browsers  It provides capabilities for navigating to web pages  user input  JavaScript execution  and more  When you run this driver  it will enable your scripts to access this and run commands on Google Chrome    This can be done via scripts running in the local network  Only local connections are allowed   or via scripts running on outside networks  All remote connections are allowed    It is always safer to use the Local Connection option  By default your Chromedriver is accessible via port 9515   To answer the question  it is just an informational message  You don t have to worry about it   Given below are both options     chromedriver  Starting ChromeDriver 83 0 4103 39  ccbf011cb2d2b19b506d844400483861342c20cd-refs branch-heads 4103   416   on port 9515 Only local connections are allowed  Please see https   chromedriver chromium org security-considerations for suggestions on keeping ChromeDriver safe  ChromeDriver was started successfully    This is by whitelisting all IPs     chromedriver --whitelisted-ips     Starting ChromeDriver 83 0 4103 39  ccbf011cb2d2b19b506d844400483861342c20cd-refs branch-heads 4103   416   on port 9515 All remote connections are allowed  Use a whitelist instead  Please see https   chromedriver chromium org security-considerations for suggestions on keeping ChromeDriver safe  ChromeDriver was started successfully

User · Answer

Not necessarily the best practice  but my environment was a local network with several machines which needed access to the selenium     When running the chromedriver  you can pass through a param like so    chromedriver --whitelisted-ips     This will basically whitelist all IP s  not always an ideal solution of course and be careful with it for production enviornments  but you should be presented with a verbose warning        Starting ChromeDriver 2 16 333244    15fb740a49ab3660b8f8d496cfab2e4d37c7e6ca  on port 9515 All remote   connections are allowed  Use a whitelist instead    A work-around at best  but it works    Relative check-in

User · Answer

This is an informational message only  What the message is telling you is that the chromedriver executable will only accept connections from the local machine   Most driver implementations  the Chrome driver and the IE driver for sure  create a HTTP server  The language bindings  Java  Python  Ruby   NET  etc   all use a JSON-over-HTTP protocol to communicate with the driver and automate the browser  Since the HTTP server is simply listening on an open port for HTTP requests generated by the language bindings  connections to the HTTP server started by the language bindings are only allowed to come from other processes on the same host  Note carefully that this limitation does not apply to connections the  browser can make to outside websites  rather it simply prevents incoming connections from other websites

User · Answer

Had the same problem  solved it by getting the appropriate webdriver from  https   chromedriver chromium org downloads You can know the exact version of your chrome browser by entering the link  chrome   settings help

[google-chrome] When running WebDriver with Chrome browser, getting message, "Only local connections are allowed" even though browser launches properly

Examples related to google-chrome

Examples related to webdriver

Examples related to selenium-chromedriver