Jetty 403 forbidden about gridrouter

[vania-pooh]

@tizzythegrey which webapp are you speaking about? There's no web-interface in GridRouter like Selenium Hub Console.

[tizzythegrey]

Thank you for the response. Ok (1) how do I test that GridRouter can talk to both of my selenium hubs? (2) do I need to actually create the user in user.properties on the OS level?

Setup:
2 hubs with nodes attached to each hub.
Grid router node in the same network with hubs. hubs address is in the quota.xml and user.properties has a test user.

[tizzythegrey]

To answer your question @ivan, I was under the impression that I can browse to the jetty server with http://user:pass@gridrouter-server:4444 but doing that gives the error message above. I basically want to know how to test the connection from gridrouter to hubs

[smecsia]

@tizzythegrey The best way to debug the connection is to watch the log files. There you can find the full information regarding each session request.
As stated by @vania-pooh, unlike Selenium Hub Gridrouter does not have any web UI, but you may consider to use Selenograph if you need it.

[innokenty]

@tizzythegrey to test the GridRouter try to launch an instance of Selenium's RemoteWebDriver against the address you provided. Instead of giving the address of a hub just give it this address. And then watch the logs or see what Selenium error message will be.

[innokenty]

As already stated, there's no web-interface whatsoever, so the only way to tests it either the one described above, or requesting a browser manually from console with curl command.

[vania-pooh]

@tizzythegrey no need to create system users, just use login and password from users.properties file. To test simply launch your test like you do with standard Selenium Hub against the URL:

 http://user:pass@gridrouter-server:4444/wd/hub

Log file is usually located at:/var/log/grid-router/grid-router.log

[tizzythegrey]

Perfect. Thanks to all of you guys and forgive me if the question was stupid. I appreciate the quick response.