Jetty 403 Forbidden on fresh install about gridrouter HOT 6 CLOSED

I can however access http://localhost:4444/stats just fine. Which has me even more confused.

Is 403/404 returned if no nodes can be found? Surely it isn't that simple, given I'm not being authenticated as expected?

``
$ java -version
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)

from gridrouter.

I think pure /wd/hub is not expected to reply 200. If you're able to access /stats then it should be working. Try requesting a browser on this instance, as if you're running it on one of your hubs.

from gridrouter.

You can also try /ping, but there's zero chance it will fail. Because /stats is ok. Just FYI.

from gridrouter.

Hello,

try to create browser's session using curl and see if it fails

$ curl -u test:test http://localhost:4444/wd/hub/session -d'{"desiredCapabilities": "browserName":"firefox"}}'

from gridrouter.

Gridrouter doesn't have web front as selenium hub has. We have plans to implement it in the future

from gridrouter.

I see! Thank you guys for the quick responses, and for this very useful asset of a tool.

@aandryashin, your curl example was missing a { but as below, I see everything is working just fine.

curl -u test:test http://localhost:4444/wd/hub/session -d'{"desiredCapabilities": {"browserName":"firefox"}}'

Now, with a little luck, the magic can start happening, and my frustration of juggling hubs is over. Thanks again!

from gridrouter.