webdriverio / selenium-standalone

A Node.js based package and CLI library for launching Selenium with WebDrivers support (Chrome, Firefox, IE, Edge)
https://webdriver.io
Other
909 stars 222 forks source link

Selenium not connecting #331

Closed toien44 closed 6 years ago

toien44 commented 6 years ago

Expected Behavior

Selenium Standalone to install/start and run test

Current Behavior

I'm getting the error

Invalid URI "http:///wd/hub/session"
  Error: Couldn't connect to selenium server

Steps to Reproduce

Selenium Standalone 6.9.0 Selenium 3.5.3

I am getting the selenium standalone install to work as I'm getting it to download and install selenium and the browser drivers and it's starting too, but will not start the test.

Logs

09:51:02.600 INFO - Selenium build info: version: '3.5.3', revision: 'a88d25fe6b' 09:51:02.600 INFO - Launching a standalone Selenium Server 2017-12-05 09:51:02.625:INFO::main: Logging initialized @237ms to org.seleniumhq.jetty9.util.log.StdErrLog 09:51:02.669 INFO - Driver class not found: com.opera.core.systems.OperaDriver 09:51:02.692 INFO - Driver provider class org.openqa.selenium.ie.InternetExplorerDriver registration is skipped: registration capabilities Capabilities [{ensureCleanSession=true, browserName=internet explorer, version=, platform=WINDOWS}] does not match the current platform MAC 09:51:02.693 INFO - Driver provider class org.openqa.selenium.edge.EdgeDriver registration is skipped: registration capabilities Capabilities [{browserName=MicrosoftEdge, version=, platform=WINDOWS}] does not match the current platform MAC 09:51:02.718 INFO - Using the passthrough mode handler 2017-12-05 09:51:02.738:INFO:osjs.Server:main: jetty-9.4.5.v20170502 2017-12-05 09:51:02.758:WARN:osjs.SecurityHandler:main: ServletContext@o.s.j.s.ServletContextHandler@6f1fba17{/,null,STARTING} has uncovered http methods for path: / 2017-12-05 09:51:02.762:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletContextHandler@6f1fba17{/,null,AVAILABLE} 2017-12-05 09:51:02.790:INFO:osjs.AbstractConnector:main: Started ServerConnector@68bbe345{HTTP/1.1,[http/1.1]}{0.0.0.0:4444} 2017-12-05 09:51:02.790:INFO:osjs.Server:main: Started @402ms 09:51:02.790 INFO - Selenium Server is up and running 2017-12-05 09:51:02.953:INFO:osjshC.ROOT:qtp1562557367-12: org.openqa.selenium.remote.server.WebDriverServlet-224edc67: Initialising WebDriverServlet 09:51:02.975 INFO - Found handler: org.openqa.selenium.remote.server.commandhandler.Status@1ce511e9 09:51:02.978 INFO - /status: Executing GET on /status (handler: Status)

Your Environment

toien44 commented 6 years ago

I have also tried selenium-standalone 6.11.0 with selenium 3.6.0 and had the same issues.