top of page
  • Writer's picturekhyati sehgal

Selenium Grid: Forbidden for Proxy, HTTP ERROR: 403

Command to start Selenium Grid at your local

java -jar selenium-server-standalone-2.41.0.jar

Aug 20, 2014 7:44:34 PM org.openqa.grid.selenium.GridLauncher main
INFO: Launching a selenium grid server
2014-08-20 19:44:35.907:INFO:osjs.Server:jetty-7.x.y-SNAPSHOT

2014-08-20 19:44:35.952:INFO:osjsh.ContextHandler:started o.s.j.s.ServletContextHandler{/,null}
2014-08-20 19:44:35.960:INFO:osjs.AbstractConnector:Started SocketConnector@0.0.0.0:4444
 

Browser Console

Error Message from browser

Forbidden for Proxy RequestURI=/grid/console

Powered by Jetty

Root cause analysis

To start the selenium grid, you need selenium standalone jar. That has to be executed at the local machine, or at the machine where you want to host your hub on.

For this, you need to make sure the command you are executing should be correct and complete. Recheck the above command I have added.

The command is not specifying any role, whether the Selenium grid should treat this instance as a Node or Hub.

Solution

java -jar selenium-server-standalone-2.41.0.jar -role hub
Aug 20, 2014 7:44:34 PM org.openqa.grid.selenium.GridLauncher main
INFO: Launching a selenium grid server
2014-08-20 19:44:35.907:INFO:osjs.Server:jetty-7.x.y-SNAPSHOT
2014-08-20 19:44:35.952:INFO:osjsh.ContextHandler:started o.s.j.s.ServletContextHandler{/,null}
2014-08-20 19:44:35.960:INFO:osjs.AbstractConnector:Started SocketConnector@0.0.0.0:4444

 

Specifying the role as the hub will solve this issue, you can make this instance as Node also for this you have to make sure that the -role parameter should get a Node as a role.

27 views0 comments
bottom of page